wilsoncespedes-dot/ajedrez-

Purpose and execution surfaces

This repository models chess-piece movement in Java and provides a standalone browser visualizer of the same rules. It is a movement model, not a full chess engine: check, checkmate, castling, en passant, and pawn promotion are outside its scope.

Java console entry point: ModeladorAjedrez/src/ajedrez/features/juego/Main.java.

Browser entry point: ModeladorAjedrez/interfaz/index.html; it runs directly in a browser and is independent of the Java runtime.

Core domain model

ModeladorAjedrez/src/ajedrez/core/Color.java defines the two sides.

ModeladorAjedrez/src/ajedrez/core/Posicion.java represents board coordinates and chess notation (a1 through h8).

ModeladorAjedrez/src/ajedrez/core/Pieza.java is the abstract base contract for all pieces, carrying shared identity/state and the movement interface.

The central boundary is that piece-specific logic depends on the core abstractions, while core does not depend on concrete piece types.

Board state and move boundary

ModeladorAjedrez/src/ajedrez/core/Tablero.java owns the 8×8 board state and provides placement, movement, and piece lookup. It is the authoritative Java state container used by movement calculations.

Primary Java flow: a caller constructs/configures a Tablero, places Pieza instances, asks a selected piece for legal movement destinations against that board, then requests the board to move the piece. Captures are represented by replacing/removing the occupant at a destination rather than through a separate game-service layer.

Piece-rule polymorphism

Each chess type is a concrete Pieza implementation:

• ModeladorAjedrez/src/ajedrez/features/piezas/Peon.java

• ModeladorAjedrez/src/ajedrez/features/piezas/Torre.java

• ModeladorAjedrez/src/ajedrez/features/piezas/Caballo.java

• ModeladorAjedrez/src/ajedrez/features/piezas/Alfil.java

• ModeladorAjedrez/src/ajedrez/features/piezas/Reina.java

• ModeladorAjedrez/src/ajedrez/features/piezas/Rey.java

Their defining responsibility is movimientosPosibles(Tablero): each evaluates destinations using position, color, board occupancy, and capture rules. Sliding pieces stop at blockers; movement validity is local to pieces and does not incorporate king-safety rules.

Console demonstration

ModeladorAjedrez/src/ajedrez/features/juego/Main.java composes the Java model into a deterministic demo: it initializes a board, displays it, queries the white queen’s moves, moves a pawn, and displays the resulting state. It is not an interactive game loop or service endpoint.

The Java runtime requires a JDK; compilation is performed directly over the source tree without a declared build system.

Independent HTML visualizer

ModeladorAjedrez/interfaz/index.html contains the interactive UI and a JavaScript translation of the Java movement rules. It initializes a standard board, tracks turns, highlights destinations, applies moves/captures, records moves, displays selected-piece metadata, and can reset state.

This is a behavioral duplication boundary: the HTML implementation does not call, compile, or embed the Java model. Rule changes must therefore be kept synchronized manually across src/ajedrez/features/piezas/ and interfaz/index.html.

External dependencies and infrastructure

There are no indicated databases, network APIs, backend services, package managers, or deployment infrastructure. Material runtimes are the JDK for the console model and any modern browser for the visualizer.