Common ClaudeForge usage scenarios.
Scenario: Starting fresh project, need CLAUDE.md
Setup:
mkdir my-react-app
cd my-react-app
npm init -y
npm install react react-dom typescriptRun ClaudeForge:
/enhance-claude-md
Claude's Response:
Discovered:
- Project Type: Web App
- Tech Stack: TypeScript, React, Node.js
- Team Size: Solo
- Phase: Prototype
Creating CLAUDE.md (85 lines) with:
- Project structure diagram
- Setup instructions (npm install, npm start)
- Component guidelines
- TypeScript best practices
Output: Single CLAUDE.md file, ~85 lines
Scenario: API service, team of 6
Setup:
mkdir api-service
cd api-service
echo "fastapi[all]" > requirements.txt
echo "pytest" >> requirements.txt
mkdir app testsRun ClaudeForge:
/enhance-claude-md
"This is a Python FastAPI API service. Team of 6 developers, MVP phase."
Output: CLAUDE.md with:
- FastAPI patterns
- Async/await guidelines
- Testing with pytest
- API documentation standards
Scenario: Large project with backend + frontend
Setup:
mkdir fullstack-app
cd fullstack-app
mkdir backend frontend
cd backend && echo "express" > package.json
cd ../frontend && echo "react" > package.jsonRun ClaudeForge:
/enhance-claude-md
Output: Modular structure
CLAUDE.md(root navigation)backend/CLAUDE.md(API guidelines)frontend/CLAUDE.md(React patterns)
Before:
# CLAUDE.md
## Tech Stack
- TypeScript
- ReactRun:
/enhance-claude-md
Claude Analyzes:
Quality Score: 25/100
Missing:
- Project Structure
- Setup & Installation
- Core Principles
- Common Commands
After: Complete 120-line file with all sections
Scenario: Made edits, verify quality
Run:
/enhance-claude-md
"Just validate, don't make changes"
Output:
Quality Score: 88/100
✅ Length: 245 lines (good)
✅ Structure: All required sections
✅ Formatting: Valid markdown
⚠️ Consider adding: Performance Guidelines
See also:
- modular-setup.md - Complex projects
- integration-examples.md - CI/CD integration