Chess has 6 piece types: King, Queen, Rook, Bishop, Knight, Pawn. Each moves differently but shares common properties (color, position, alive/captured). You need a clean hierarchy that lets the board call move validation on any piece polymorphically.

Code

enum Color { WHITE, BLACK }

abstract class Piece {
  protected color: Color
  protected position: Position
  protected alive: boolean = true

  abstract getValidMoves(board: Board): Position[]
  abstract getSymbol(): string

  canMoveTo(board: Board, target: Position): boolean {
    return this.getValidMoves(board).some(p => p.equals(target))
  }
}

class King extends Piece {
  getValidMoves(board: Board): Position[] {
    // One square in any direction + castling
  }
}

class Knight extends Piece {
  getValidMoves(board: Board): Position[] {
    // L-shape moves
  }
}

Question

How should you design the piece class hierarchy?

0% completed

🔍Search

📚LLD Introduction

🎯OOP Fundamentals

🔗Class Relationships

💡Design Principles

⭐SOLID Principles

Single Responsibility Principle

Open/Closed Principle

Liskov Substitution Principle

Interface Segregation Principle

Dependency Inversion Principle

📊UML Diagrams

🎨Additional Patterns

Template Method Pattern

Proxy Pattern

💼LLD Interview Tips

LLD Interview Approach

Common LLD Mistakes

Evaluation Criteria

Back to LLD

6/20

LLD|❓ LLD Interview Questions| 35 min

Design Chess Game

Intermediate35 min read+10 XP

TL;DR — Design Chess Game

Learn Design Chess Game — a key concept for LLD interviews.

Interactive — Try it yourself!

♚Design a Chess Gamehard

Step 1/5

0 pts

Piece Class Hierarchy

Abstract Class Design

Code

enum Color { WHITE, BLACK }

abstract class Piece {
  protected color: Color
  protected position: Position
  protected alive: boolean = true

  abstract getValidMoves(board: Board): Position[]
  abstract getSymbol(): string

  canMoveTo(board: Board, target: Position): boolean {
    return this.getValidMoves(board).some(p => p.equals(target))
  }
}

class King extends Piece {
  getValidMoves(board: Board): Position[] {
    // One square in any direction + castling
  }
}

class Knight extends Piece {
  getValidMoves(board: Board): Position[] {
    // L-shape moves
  }
}

Question

How should you design the piece class hierarchy?