Target Audience: Claude AI working as a Reactium/Actinium developer Purpose: Minimal bootstrap → comprehensive CLAUDEDB documentation system
START HERE when answering any question about this framework:
- CLAUDEDB/INDEX.md - Keyword → direct section links (100+ terms)
- CLAUDEDB/TASKS.md - "How do I..." → implementation guides (60+ tasks)
- CLAUDEDB/CONCEPTS.md - Concept → learning paths (25+ topics)
- CLAUDEDB/API.md - Function signatures + docs (60+ APIs)
- User asks question
- Check CLAUDEDB for relevant keyword/task/concept/API
- Get direct link to answer in CLAUDE/ documentation
- Read ONLY that specific section (not entire files)
- Answer with reference
Example:
- User: "How do I create a route with data loading?"
- You: Check CLAUDEDB/TASKS.md → find task → read linked section → answer
Efficiency: Instead of reading 3-4 full files (1000s of lines), read ONE section (50-100 lines).
reactium-framework/
├── CLAUDEDB/ # ← YOUR NAVIGATION SYSTEM (start here)
├── CLAUDE/ # ← Comprehensive documentation (20+ guides)
├── Actinium-Plugins/ # Backend plugins
├── Reactium-Core-Plugins/ # Frontend core plugins
├── reactium-sdk-core/ # Shared SDK package
├── CLI/ # CLI tools (npx reactium)
└── example-reactium-project/ # Reference implementation
- INDEX.md - Alphabetical keyword lookup
- TASKS.md - Task-based organization ("I want to...")
- CONCEPTS.md - Learning paths (basic → advanced)
- API.md - Function signatures + parameter docs
- README.md - How to use CLAUDEDB
- VERIFICATION.md - Link integrity tests
| File | Use When | Example |
|---|---|---|
| INDEX.md | User asks "What is X?" | "What are Capabilities?" |
| TASKS.md | User asks "How do I X?" | "How do I create a route?" |
| CONCEPTS.md | User wants to learn/understand | "Explain the Hook System" |
| API.md | User needs function signature | "What params does Hook.register take?" |
You are now bootstrapped. Start with CLAUDEDB for every question.