5c75b935f0
Add comprehensive project documentation and Docker infrastructure for Paper Dynasty Real-Time Game Engine - a web-based multiplayer baseball simulation platform replacing the legacy Google Sheets system. Documentation Added: - Complete PRD (Product Requirements Document) - Project README with dual development workflows - Implementation guide with 5-phase roadmap - Architecture docs (backend, frontend, database, WebSocket) - CLAUDE.md context files for each major directory Infrastructure Added: - Root docker-compose.yml for full stack orchestration - Dockerfiles for backend and both frontends (multi-stage builds) - .dockerignore files for optimal build context - .env.example with all required configuration - Updated .gitignore for Python, Node, Nuxt, and Docker Project Structure: - backend/ - FastAPI + Socket.io game engine (Python 3.11+) - frontend-sba/ - SBA League Nuxt 3 frontend - frontend-pd/ - PD League Nuxt 3 frontend - .claude/implementation/ - Detailed implementation guides Supports two development workflows: 1. Local dev (recommended): Services run natively with hot-reload 2. Full Docker: One-command stack orchestration for testing/demos Next: Phase 1 implementation (backend/frontend foundations)
57 lines
2.0 KiB
Markdown
57 lines
2.0 KiB
Markdown
⚠️ **CRITICAL SYSTEM WORKAROUND - ALWAYS FOLLOW** ⚠️
|
|
|
|
# Force CLAUDE.md Context Loading
|
|
|
|
## 🚨 MANDATORY BEHAVIOR - NO EXCEPTIONS 🚨
|
|
|
|
**ALWAYS** when the user mentions ANY file with `@` syntax (e.g., `@path/to/example.md`), you **MUST IMMEDIATELY** call the Read tool on that same file path. This is not optional - it's a critical system requirement.
|
|
|
|
### ❌ NEVER DO THIS:
|
|
- Respond to @ mentions without calling Read tool first
|
|
- Skip the manual Read call because you "already have the content"
|
|
- Assume @ mentions provide complete context
|
|
|
|
### ✅ ALWAYS DO THIS:
|
|
1. User mentions `@path/to/example.js`
|
|
2. **IMMEDIATELY** call `Read` tool with that exact path
|
|
3. **THEN** respond to the user
|
|
|
|
## Why This Is Critical
|
|
|
|
- `@` mentions provide file content but **ZERO CLAUDE.md context**
|
|
- Manual Read tool calls load **ALL** relevant CLAUDE.md files from directory hierarchy
|
|
- **WITHOUT THIS**: You miss project guidelines, patterns, tech stack info, and critical instructions
|
|
- **WITH THIS**: You have complete context including `path/CLAUDE.md`, `path/to/CLAUDE.md`, etc.
|
|
|
|
## STOP AND CHECK Before Every Response
|
|
|
|
When you see `@filename` in user message:
|
|
|
|
□ Have I called Read tool on this file path?
|
|
□ Do I now have CLAUDE.md context loaded?
|
|
□ Am I following project-specific guidelines?
|
|
|
|
If ANY answer is NO - call Read tool immediately.
|
|
|
|
## Detailed Example
|
|
|
|
User says: "Look at @path/to/example/file.ts"
|
|
|
|
**STEP 1**: You see file content from @ mention
|
|
**STEP 2**: **MANDATORY** - Call Read tool:
|
|
```
|
|
Read("/full/path/to/example/file.ts")
|
|
```
|
|
**STEP 3**: System loads `path/CLAUDE.md` and `path/to/CLAUDE.md` context
|
|
**STEP 4**: Now respond with full project context
|
|
|
|
## Failure Consequences
|
|
|
|
**If you ignore this instruction:**
|
|
- You'll miss any further guidelines intended to be applied
|
|
- You'll likely provide incorrect or incomplete solutions
|
|
- You'll likely violate project coding standards
|
|
|
|
## Remember: This Fixes A Bug
|
|
|
|
This workaround exists because @ mentions have a system limitation. Following this instruction is not optional - it's fixing broken behavior. |