Migrated from design-system-swarm with fresh git history.
Old project history preserved in /home/overbits/apps/design-system-swarm
Core components:
- MCP Server (Python FastAPI with mcp 1.23.1)
- Claude Plugin (agents, commands, skills, strategies, hooks, core)
- DSS Backend (dss-mvp1 - token translation, Figma sync)
- Admin UI (Node.js/React)
- Server (Node.js/Express)
- Storybook integration (dss-mvp1/.storybook)
Self-contained configuration:
- All paths relative or use DSS_BASE_PATH=/home/overbits/dss
- PYTHONPATH configured for dss-mvp1 and dss-claude-plugin
- .env file with all configuration
- Claude plugin uses ${CLAUDE_PLUGIN_ROOT} for portability
Migration completed: $(date)
🤖 Clean migration with full functionality preserved
74 lines
2.5 KiB
Plaintext
74 lines
2.5 KiB
Plaintext
# DSS Claude Code Context Rules
|
|
# Automatically loads optimal documentation hierarchy for each task
|
|
|
|
## Session Initialization (ALWAYS LOAD FIRST)
|
|
Always load these files at the start of each session to understand the project:
|
|
1. QUICK_REFERENCE.md - Navigation map for all documentation
|
|
2. docs/02_status/PROJECT_STATUS.md - Current deployment status
|
|
3. docs/01_core/PRINCIPLES.md - Design philosophy
|
|
|
|
## Context by Task Type
|
|
|
|
### Architecture & Design Questions
|
|
Load: docs/01_core/ARCHITECTURE.md
|
|
Search: "system design", "component boundaries", "technology stack"
|
|
|
|
### API Development & Changes
|
|
Load: docs/01_core/API_CONTRACTS.md
|
|
Search: "endpoints", "status codes", "authentication", "error handling"
|
|
|
|
### Integration Work
|
|
Load: docs/03_reference/INTEGRATION_GUIDE.md
|
|
Search: "external projects", "consuming DSS", "setup"
|
|
|
|
### Migration from Legacy Systems
|
|
Load: docs/03_reference/MIGRATION_GUIDE.md
|
|
Search: "upgrading", "converting", "legacy"
|
|
|
|
### MCP Tool Execution
|
|
Load: docs/03_reference/MCP_TOOLS_SPEC.md
|
|
Search: "Model Context Protocol", "tool parameters", "execution"
|
|
|
|
### Production Deployment
|
|
Load: docs/03_reference/PRODUCTION_READINESS.md
|
|
Search: "deployment", "monitoring", "health checks", "production"
|
|
|
|
### Feature Planning & Roadmap
|
|
Load: docs/02_status/PROJECT_STATUS.md
|
|
Search: "roadmap", "open bugs", "current phase"
|
|
|
|
## Files to IGNORE (Never Load)
|
|
|
|
**NEVER load these files** - they are historical/obsolete:
|
|
- docs/archive/* (unless specifically researching history)
|
|
- Any file matching: DEPLOYMENT_*, MVP_*, PHASE_*_COMPLETE, *_REPORT.md
|
|
- WEEK*_SUMMARY.md files
|
|
- Old phase planning documents
|
|
|
|
These files can confuse the model about current state. Always use docs/02_status/ instead.
|
|
|
|
## Documentation Versioning
|
|
|
|
Tier 1 files include version numbers (e.g., "Version 1.2.3"):
|
|
- docs/01_core/API_CONTRACTS.md
|
|
- docs/01_core/ARCHITECTURE.md
|
|
- docs/01_core/PRINCIPLES.md
|
|
|
|
If working on features that require API/architecture changes, check these versions first.
|
|
|
|
## When in Doubt
|
|
|
|
1. Check QUICK_REFERENCE.md for navigation
|
|
2. Load relevant Tier docs: 1 → 2 → 3
|
|
3. If still unclear, search for keywords in loaded docs
|
|
4. Never load from docs/archive/ unless specifically researching history
|
|
|
|
## Breaking the Rules
|
|
|
|
If you need to:
|
|
- Load a file not listed here: Check that it's in docs/ and not in docs/archive/
|
|
- Create a new documentation file: Follow DOCUMENTATION_GUIDE.md governance
|
|
- Reference historical information: Use docs/archive/ cautiously
|
|
|
|
Last Updated: 2025-12-08
|