cal/mantimon-tcg
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Mantimon TCG - Monster collecting trading card game
132 Commits 2 Branches 0 Tags 20 MiB
TypeScript 46.9%
Python 43.4%
Vue 9.5%
Shell 0.1%
7885b272a4
Go to file
Claude 7885b272a4
Honor RulesConfig for prize cards vs points in frontend game board 
The game board now conditionally renders prize card zones based on
the RulesConfig sent from the backend:

- Add rules_config field to VisibleGameState in backend (visibility.py)
- Add rules_config to frontend game types and game store
- Update layout.ts to accept LayoutOptions with usePrizeCards and prizeCount
- Update StateRenderer to conditionally create PrizeZone objects
- Update Board to handle empty prize position arrays gracefully
- Add game store computed properties: rulesConfig, usePrizeCards, prizeCount
- Add tests for conditional prize zone rendering

When use_prize_cards is false (Mantimon TCG points system), the prize
zones are not rendered, saving screen space. When true (classic Pokemon
TCG mode), the correct number of prize slots is rendered based on
the rules config's prize count.

https://claude.ai/code/session_01AAxKmpq2AGde327eX1nzUC
2026-02-02 09:22:44 +00:00
.claude Add lessons learned README for frontend POC 2026-01-31 22:06:10 -06:00
backend Honor RulesConfig for prize cards vs points in frontend game board 2026-02-02 09:22:44 +00:00
docs Implement Phase 2: Authentication system 2026-01-27 21:49:59 -06:00
frontend Honor RulesConfig for prize cards vs points in frontend game board 2026-02-02 09:22:44 +00:00
.gitignore Archive frontend POC to .claude/frontend-poc/ 2026-01-31 22:00:51 -06:00
CLAUDE.md Add project-specific skills reference to CLAUDE.md 2026-01-31 15:40:37 -06:00
PROJECT_PLAN.md Add RPG campaign structure inspired by GBC Pokemon TCG 2026-01-24 18:22:36 -06:00

docs/README.md

Mantimon TCG Documentation

Active Documentation

File Description
ARCHITECTURE.md Technical architecture overview covering frontend (Vue+Phaser), backend (FastAPI), database schema, real-time communication, game engine design, and offline fork considerations.
GAME_RULES.md Game rules document defining campaign structure, base ruleset, energy system, deck building, win conditions, turn structure, card types, and status conditions.

Legacy Documentation

Historical documents from completed development phases, preserved for reference.

File Description
legacy/SYSTEM_REVIEW.md Comprehensive code review of the core game engine (Jan 2026). Identified 15 issues across models, effects, and engine - all resolved. 826 tests passing.
legacy/PROJECT_PLAN_ENERGY_EVOLUTION.md Implementation plan for energy/tool attachment refactor and evolution stack system. Changed attached_energy/attached_tools from list[str] to list[CardInstance]. Completed Jan 2026.