Level Skills
Auto-adaptive skills that understand your quality level and generate code accordingly.
How Level Skills Work
Level Skills automatically detect your project's quality level (Rapid, Balanced, or Crafted) by reading your CLAUDE.md file. They then generate code that matches the architectural patterns and quality requirements of that level.
Zero Configuration Required
You never have to tell Claude which level you're using. It reads your project configuration and adapts automatically.
The 3 Level Skills
rapid (MVP Mode)
Ship in 2 days. Flat architecture. Perfect for validating your market before investing in complex architecture.
Example Usage:
/rapid "Add user profile page with bio and avatar upload"Generated Code:
- • tRPC router with all logic in-router (flat, up to 100 lines OK)
- • Zod validation schemas
- • React component with Tailwind CSS
- • No tests (unless explicitly requested)
- • Pragmatic, working code over perfect architecture
Architecture Pattern:
Everything in routers. Direct Prisma calls. No separation of concerns.
Code Quality Rules:
Functions up to 100 lines. DRY only if repeated 3+ times. Focus on shipping.
Best For:
0-100 users. Testing market fit. Solo founders. 2-day MVPs.
balanced (Growth Mode)
MOST POPULAR3-layer architecture. 70% test coverage. Pragmatic quality for growing teams and products.
Example Usage:
/balanced "Add payment integration with Stripe checkout"Generated Code:
- • Router: Thin orchestration layer (max 20 lines)
- • Service: Business logic (pure functions, max 50 lines)
- • Repository: Data access layer with Prisma
- • Tests: Unit + integration (70%+ coverage enforced)
- • Validation: SOLID principles checked automatically
Architecture Pattern:
3-layer (Router → Service → Repository). Clean separation of concerns.
Code Quality Rules:
Functions max 50 lines. Max 3 parameters. No duplication (2+ = extract). Cyclomatic complexity < 10.
Best For:
100-10K users. Growing teams (3-10 devs). Products with 1-3 year horizon.
crafted (Enterprise Mode)
Hexagonal DDD. 100% test coverage. Software craftsmanship for products built to last 10+ years.
Example Usage:
/crafted "Add order management with approval workflow"Generated Code:
- • Domain Layer: Pure entities, value objects, aggregates (ZERO deps)
- • Application Layer: Use-cases (ultra-thin, max 10 lines)
- • Infrastructure: Repositories, external services
- • Tests: Domain 100%, Use-cases 100%, Infra 80%
- • Validation: Architecture tests, SOLID audits, ADR documentation
Architecture Pattern:
Hexagonal (Domain/Application/Infrastructure). Ports & Adapters. Pure business logic.
Code Quality Rules:
Functions max 20 lines. Max 2 parameters. Zero duplication. Cyclomatic complexity < 5.
Best For:
10K+ users. Large teams (10-200 devs). Enterprise products with 5-10+ year lifespan.
Choosing Your Level
Each level is designed for different stages of product maturity:
Choose your level when creating the project based on your team size, user base, and long-term goals. Each level generates code with different architectural patterns and quality standards.
💡 Pro Tip
Most startups should start with Rapid for market validation, then upgrade to Balanced once they hit product-market fit (100+ paying users). Only upgrade to Crafted when you have significant revenue and a large team.