Claude Code
1 / 7
Step 01 — LLM Target
Choose Your AI Tool
Controls prompt structure, context strategy, and the project rules file generated for your repo.
01aSelect AI coding tool
01bContext strategy
Claude Code reads your repo files directly. Reference files by path and Claude finds them. Lean prompt — no scaffold needed.
Rules file: CLAUDE.md
Context strategy
  • → Reference files by route/path — Claude reads them directly
  • → No context pasting required
  • → Lean prompt — skip output scaffolding
  • → CLAUDE.md in repo root read before every task
01c Project rules file — toggle rules
Consistency First
Reuse and extend existing code before creating new patterns.
Smallest Possible Change
Prefer the minimal change that satisfies requirements. No unsolicited refactors.
Infrastructure Guard
Do not create or modify infra resources unless explicitly requested.
Database Guard
Verify new tables/indexes are required. Prefer existing access patterns.
API Conventions
Follow existing validation, error handling, and response structures.
Frontend Patterns
Follow existing component structure, routing, and state management patterns.
Styling Rules
Use existing CSS/Tailwind conventions. No inline styles. No global CSS changes.
No New Dependencies
Do not add packages without explicit approval.
TypeScript Strict
No any types, no unnecessary assertions, no disabled lint rules.
File Scope
Modify only files required for the task. Keep PRs focused.
Inspect Before Implementing
Find similar implementations and existing patterns before writing code.
Required Output Scaffold
Provide: Analysis → Files Impacted → Plan → Code → Validation → Risks.
Validation Checklist
Verify TypeScript compiles, tests pass, no infra changes, no unrelated changes.
Step 02 — Project
Project Context
Name your project, set the stage, and reference files.
02 Identification
Stage
Step 03 — Cloud & Infra
Cloud Platform & IaC
Select provider(s), region, and IaC tooling. Mix freely.
03a Cloud Provider
03b Region
03c Infrastructure as Code
Step 04 — Stack
Languages & Frameworks
Select every technology in play.
04aFrontend
04bCSS / Styling
04cBackend / Runtime
04dDatabase & Storage
04eAuth, AI & Services
04fTesting & Tooling
Step 05 — Changes
What to Build
One atomic change per item. One concern per change.
05 Change list
1
Step 06 — Constraints
Guard Rails
What the AI must not touch. Constraints matter as much as changes.
06a Hard constraints
1
06bQuick presets
Step 07 — Generate
Your Outputs
Task prompt to paste into your AI tool + project rules file to commit to your repo.
Stagedev
LLMClaude Code
Words0
Chars0
Changes0
Constraints0
Stack0
📋 Project Rules File
CLAUDE.md
— commit to repo root
# AI Development Rules ## Purpose These rules apply to all AI-assisted development tasks in this repository. Optimised for: **Claude Code** Read this file before making any changes. --- # Project Context **Stage:** dev --- # Architecture Principles ## Definition of Success * Solves the requested problem * Follows existing architecture * Minimises code changes * Maintains consistency * Introduces no unnecessary complexity