Meta-documentation framework for effective development with Claude Code and AI agents
β οΈ Important Note: This framework is designed for beginners practicing vibe-coding, not professional developers. It covers a tiny fraction of AI coding agents' capabilities and will evolve and be modified as practical experience accumulates.π Created to support students of the AI Agents course for beginners:
- Full course: AI Agents Full Course (Russian)
- For complete beginners: Free AI Intro Course (Russian)
π·πΊ Π ΡΡΡΠΊΠ°Ρ Π²Π΅ΡΡΠΈΡ: README_RU.md
π Π¨Π°Π±Π»ΠΎΠ½Ρ Π΄ΠΎΡΡΡΠΏΠ½Ρ Π½Π° Π΄Π²ΡΡ ΡΠ·ΡΠΊΠ°Ρ :
Init/β ΡΡΡΡΠΊΠΈΠ΅ ΡΠ°Π±Π»ΠΎΠ½Ρ (Russian templates)init_eng/β Π°Π½Π³Π»ΠΈΠΉΡΠΊΠΈΠ΅ ΡΠ°Π±Π»ΠΎΠ½Ρ (English templates)
Claude Code Starter is a ready-to-use meta-documentation framework that transforms chaotic AI-assisted development into a structured and efficient process.
When working with Claude Code or other AI agents:
- π₯ AI doesn't understand project context β makes wrong architectural decisions
- πΈ Loads entire project into context β wastes tokens and money
- π You explain the same things repeatedly β waste time
- π² Unpredictable results β no single source of truth
- π« Security issues β AI doesn't know the rules
The framework provides 11 ready-made documentation templates that:
- β
Auto-load into Claude Code context (via
CLAUDE.md) - β Save tokens through modular architecture
- β Single source of truth for AI and team
- β Built-in security (SECURITY.md)
- β Slash commands for automation (/commit, /pr, /migrate, etc.)
- β Standardized processes via Makefile
git clone https://github.com/alexeykrol/claude-code-starter.git
cd claude-code-starter# Create new project or navigate to existing one
mkdir my-new-project
cd my-new-project
# Copy all files from Init/
cp -r ../claude-code-starter/Init/* .
cp -r ../claude-code-starter/Init/.claude .This is the most important file - start here:
# Open in editor
code PROJECT_INTAKE.md
# Or use Claude Code
claude PROJECT_INTAKE.mdFill in key sections:
- Problem β Solution β Value - why does your project exist?
- User Personas - who are your users?
- User Flows - how will they interact?
- Unique vs Standard Features - what to build vs what to integrate?
- Modular Structure - how to break into modules?
# In your project root
claude
# Claude will automatically load CLAUDE.md into context
# And read all necessary files"Read PROJECT_INTAKE.md and ask all clarifying questions"
| File | Purpose | When to Fill |
|---|---|---|
| CLAUDE.md | π€ Auto-loads in Claude Code | Immediately, minimal edits |
| PROJECT_INTAKE.md | β START HERE - project requirements | Day 1, foundation of everything |
| SECURITY.md | π Security rules | Immediately, critical! |
| ARCHITECTURE.md | ποΈ Architectural decisions | As decisions are made |
| BACKLOG.md | π Single source of truth for status | Update each sprint |
| AGENTS.md | π― Detailed AI instructions | As patterns emerge |
| WORKFLOW.md | π Development processes | Rarely, when processes change |
| PLAN_TEMPLATE.md | π Planning template | Use as template |
| README-TEMPLATE.md | π README template for project | Fill and rename to README.md |
| File/Folder | Purpose |
|---|---|
| Makefile | Standardized commands (make dev, make build, etc) |
| .claude/commands/ | Slash commands: /commit, /pr, /migrate, /security, etc |
| .claude/settings.json | Access permissions for Claude Code |
| .env.example | Environment variables template |
Monolithic approach problem:
Claude loads entire project (5000 lines) β
Wastes tokens reading everything β
Expensive and slow β
May get confused in large context
Solution through modules:
Claude loads only needed module (200 lines) β
Fewer tokens β
Faster and cheaper β
Better understanding of task
Application = Set of small LEGO blocks
Each module:
- Solves one narrow task
- Has clear input and output
- Can be tested separately
- Doesn't depend on other modules
Read more in Init/ARCHITECTURE.md (section "Module Architecture")
- Copy templates from
Init/to your project - Fill PROJECT_INTAKE.md - this is the foundation
- Read SECURITY.md - internalize security rules
- Configure Makefile for your stack (React/Vue/Node/etc)
- Launch
claudein project root - CLAUDE.md auto-loads into context
- Ask AI to read PROJECT_INTAKE.md and ask questions
- Work modularly: one module β testing β next module
- Update BACKLOG.md after each sprint
- Enhance ARCHITECTURE.md with architectural decisions
- Expand AGENTS.md with new patterns
- Use slash commands to automate routine tasks
β DO:
- Start with "WHY?" - problem β solution β value
- Create 2-3 User Personas with names and pain points
- Describe User Flows step-by-step (not abstractions!)
- Separate features into unique (build) vs standard (integrate ready-made)
- Plan modular structure
β DON'T:
- Leave [FILL IN] without filling
- Write abstractly without specifics
- Plan to build standard features from scratch (Auth, Payments, etc)
β DO:
- Use
/commitinstead of manual commits - Load context via TodoWrite for task tracking
- Work by modules: Auth β API β Screens β Business Logic
- Ask AI to update documentation with changes
β DON'T:
- Don't load entire project into context at once
- Don't skip SECURITY.md
- Don't ignore architectural decisions from ARCHITECTURE.md
β ALWAYS:
- Read SECURITY.md before coding
- Use
.env.exampleβ.env.local - Validate all input data
- Use
/securityslash command for audits
β NEVER:
- Commit
.envfiles - Hardcode secrets in code
- Ignore security warnings
After copying templates, your project will look like this:
your-project/
βββ .claude/
β βββ commands/ # Slash commands (/commit, /pr, etc)
β βββ settings.json # Claude Code access permissions
β
βββ src/ # Your code
β βββ features/ # Feature modules
β βββ lib/ # Utilities and services
β βββ ...
β
βββ CLAUDE.md # π€ Auto-loads in Claude Code
βββ PROJECT_INTAKE.md # β Project requirements
βββ SECURITY.md # π Security rules
βββ ARCHITECTURE.md # ποΈ Architectural decisions
βββ BACKLOG.md # π Implementation status
βββ AGENTS.md # π― AI instructions
βββ WORKFLOW.md # π Development processes
βββ Makefile # π οΈ Standard commands
βββ .env.example # π Variables template
βββ README.md # π Project documentation (from README-TEMPLATE.md)
The framework is alive and evolving. To get updates:
# In claude-code-starter folder
git pull origin main
# Compare changes and update your projects manually
diff Init/CLAUDE.md your-project/CLAUDE.mdRecommendation: Don't overwrite your filled files - copy only new sections.
The framework is created for the community and open to improvements!
- Fork the repository
- Create feature branch (
git checkout -b feature/AmazingFeature) - Commit changes (
git commit -m 'Add some AmazingFeature') - Push to branch (
git push origin feature/AmazingFeature) - Open Pull Request
- π New sections in templates
- π§ New slash commands
- π¨ Examples for popular stacks (Next.js, Vue, etc)
- π Translations (already have Russian version!)
- π Tutorials and use cases
- Claude Code Documentation - official documentation
- GitHub Repository - framework source code
- Issues - report problem or suggest improvement
MIT License - use freely in your projects!
Framework inspired by:
- Official Claude Code best practices
- Experience developing with AI agents
- Modular architecture principles
- Developer community
- β Basic documentation templates
- β Slash commands for git and security
- β Makefile for standardization
- β Modular architecture
- Examples for Next.js
- Examples for Vue 3
- English version
- Video tutorials
- CLI for automatic initialization
- Integration with popular templates
- VS Code plugins
- AI-powered code review templates
If something is unclear:
- Read
Init/PROJECT_INTAKE.md- detailed comments there - Study
Init/CLAUDE.md- Quick Start there - Open Issue
Happy coding with Claude! π€β¨
This framework turns AI-assisted development from chaos into a structured process.