This index is the canonical entry point for durable project documentation in docs/. When adding, moving, or replacing documentation, update this file in the same change.

• Product Docs: product-facing documents, including scope, goals, acceptance criteria, and the current high-fidelity gameplay-recreation direction.

• Research Docs: research and technical evaluation notes that support delivery decisions.
• Tiantian Fuweng Map References: public screenshots of Tiantian Fuweng maps collected for internal reference only.

• Superpowers Docs: validated design specs and execution plans for implementation work.
• Fortune Board High-Fidelity Tiantian Fuweng Roadmap Implementation Plan: current mainline implementation roadmap for shifting the project toward a phased high-fidelity Tiantian-Fuweng-style gameplay target.
• Fortune Board Reference Image Full-Screen Battle Design: canonical visual-design spec for rebuilding Battle toward the user-provided full-screen reference image with denser HUD, board, and edge-action structure.
• Fortune Board Reference Image Full-Screen Battle Implementation Plan: current implementation plan for rebuilding Battle toward the user-provided reference image with a denser full-screen shell, richer corner HUDs, and stronger edge-action structure.
• Fortune Board World Map High-Fidelity Battle Design: superseded predecessor spec that established the broader world-map direction before the tighter reference-image target.
• Fortune Board World Map High-Fidelity Battle Implementation Plan: older implementation plan for the superseded world-map target; retained as project history after the newer reference-image full-screen direction.
• Fortune Board First Playable MVP Design: approved design for the first playable Cocos board-game slice.
• Fortune Board First Playable MVP Implementation Plan: implemented execution record for initializing the real Cocos project and shipping the first playable board loop.
• Fortune Board Cocos CI Verification Design: approved design for automated Cocos import/build verification in CI using a GUI-capable macOS runner.
• Fortune Board Cocos CI Verification Implementation Plan: task-by-task plan for wiring generic preflight checks, an authoritative build wrapper, and CI workflow coverage.
• Fortune Board Cards And Skills Alpha Implementation Plan: next-iteration plan for adding deterministic cards, role skills, and AI usage on top of the first playable Battle scene.
• Fortune Board City Park Map Rework Design: approved design for reworking the Battle scene into a city-park-style competition board.
• Fortune Board City Park Map Rework Implementation Plan: execution plan for rebuilding the Battle scene into a city-park competition board with richer tile variety and presentation.
• Fortune Board Bright Amusement Map Polish Implementation Plan: superseded execution plan from the earlier bright-amusement visual direction.
• Fortune Board Battle Scene Visual Recovery Implementation Plan: superseded recovery plan from the abandoned bright-amusement direction.
• Fortune Board Bright Amusement Map Polish Design: superseded visual-direction spec from the earlier bright-amusement branch.
• Infrastructure Checklist: phased recommendation for the minimum client, tooling, observability, and backend infrastructure needed before and after MVP validation.

• Create or refresh the Cocos project baseline with bash tools/create-cocos-project.sh
• Install JS dependencies with npm install
• Run repo-local lint with npm run lint
• Check formatting for supported code/config files with npm run format:check
• Auto-fix supported code/config files with npm run format and npm run lint:fix
• Run deterministic rules tests with npm test
• Run repository preflight verification with npm run verify:cocos-preflight (lint, format check, tests, and project verification)
• Run the authoritative Cocos build smoke with npm run verify:cocos-build on a GUI-capable macOS machine with Cocos Creator 3.8.8
• GitHub Actions wires both checks through .github/workflows/cocos-verify.yml; the authoritative build job expects a self-hosted macOS runner labeled gui-capable and cocos-3_8_8, and runs Cocos with an isolated HOME under the runner temp directory
• Open the project through Cocos Dashboard with: '/Applications/CocosDashboard.app/Contents/MacOS/CocosDashboard' /Users/lzn/Documents/trae_projects/demo
• If assets/scenes/Battle.scene.meta UUID or the playable build target changes, update the committed CI build config in the same change

• Add every durable document in docs/ to this index with a one-line description.
• Group entries by document type or topic so readers can scan the tree quickly.
• If a topic expands into multiple files, create a topic folder with its own README.md and link that folder here.
• Mark temporary, draft, or superseded documents clearly instead of leaving their status implicit.