Structured workflows, specialized agents, mandatory rules, and best practices
Inspired by addyosmani/agent-skills
This repository provides a production-grade configuration for Claude Code AI agents. It includes:
- Structured development workflow (Spec → Plan → Build → Test → Review → Ship)
- 10 specialized agents for different development roles
- 13 mandatory rules covering code quality, architecture, and operations
- 8 slash commands for common workflows
- 4 reference checklists for security, testing, performance, and accessibility
┌──────────────────────────────────────────────────────────────────┐
│ │
│ /spec → /plan → /build → /test → /review → /deploy │
│ │
│ Define Plan Build Verify Review Ship │
│ │
└──────────────────────────────────────────────────────────────────┘
| Phase | Command | Description |
|---|---|---|
| Define | /spec |
Create PRD with objectives, scope, and boundaries |
| Plan | /plan |
Decompose into vertical slices with acceptance criteria |
| Build | /build |
Implement incrementally using TDD |
| Verify | /test |
Write tests with RED-GREEN-REFACTOR |
| Review | /review |
Five-axis code review |
| Ship | /deploy |
Build, test, and deploy |
| Command | Description |
|---|---|
/debug |
Systematic error diagnosis |
/simplify |
Reduce code complexity |
/fix-issue |
Analyze and fix issues |
.claude/
├── CLAUDE.md # Main AI configuration
│
├── commands/ # Slash commands (8 total)
│ ├── spec.md # /spec — PRD creation
│ ├── plan.md # /plan — Task breakdown
│ ├── build.md # /build — Incremental implementation
│ ├── test.md # /test — TDD workflow
│ ├── review.md # /review — Code review
│ ├── deploy.md # /deploy — Deployment
│ ├── debug.md # /debug — Error diagnosis
│ ├── simplify.md # /simplify — Code simplification
│ └── fix-issue.md # /fix-issue — Issue resolution
│
├── agents/ # Specialized agents (10 total)
│ ├── frontend.md # Frontend Developer
│ ├── backend.md # Backend Developer
│ ├── systems-architect.md # Systems Architect
│ ├── code-reviewer.md # Code Reviewer
│ ├── test-engineer.md # Test Engineer
│ ├── security-auditor.md # Security Auditor
│ ├── qa.md # QA Engineer
│ ├── project-manager.md # Project Manager
│ ├── ui-ux-designer.md # UI/UX Designer
│ └── copywriter-seo.md # Copywriter/SEO
│
├── rules/ # Mandatory rules (13 total)
│ ├── clean-code.md # Clean Code principles
│ ├── code-style.md # Formatting & naming
│ ├── error-handling.md # Error patterns
│ ├── tech-stack.md # Approved technologies
│ ├── system-design.md # System design patterns
│ ├── project-structure.md # Folder organization
│ ├── api-conventions.md # REST API standards
│ ├── naming-conventions.md # Naming patterns
│ ├── database.md # Database patterns
│ ├── security.md # Security requirements
│ ├── monitoring.md # Observability
│ ├── testing.md # Test standards
│ └── git-workflow.md # Git conventions
│
├── skills/ # Advanced skills
│ ├── tdd/SKILL.md # Test-Driven Development
│ ├── code-review/SKILL.md # Five-axis review
│ ├── incremental-implementation/SKILL.md
│ ├── deploy/SKILL.md
│ └── security-review/SKILL.md
│
├── references/ # Quick checklists
│ ├── security-checklist.md
│ ├── testing-patterns.md
│ ├── performance-checklist.md
│ └── accessibility-checklist.md
│
└── settings.json # Project settings
| Agent | Role | Invoke When |
|---|---|---|
| Frontend Developer | Next.js, React, TypeScript, UI | Components, pages, state |
| Backend Developer | Express, Prisma, Redis, BullMQ | APIs, services, jobs |
| Systems Architect | Architecture, ADRs, scaling | System design decisions |
| Agent | Role | Invoke When |
|---|---|---|
| Code Reviewer | Five-axis code review | PR reviews, quality checks |
| Test Engineer | TDD, coverage, test strategy | Writing and reviewing tests |
| Security Auditor | Vulnerability, threat modeling | Security reviews |
| QA Engineer | Test plans, E2E, bug reports | Quality assurance |
| Agent | Role | Invoke When |
|---|---|---|
| Project Manager | Stories, sprints, planning | Project planning |
| UI/UX Designer | Design system, accessibility | UX decisions |
| Copywriter/SEO | Copy, meta tags, SEO | Content creation |
| Layer | Technology |
|---|---|
| Frontend (SEO) | Next.js 14 (App Router) |
| Frontend (Admin) | React + Vite |
| Styling | Tailwind CSS + shadcn/ui |
| State | Zustand + TanStack Query |
| Backend | Express.js + TypeScript |
| ORM | Prisma |
| Database | PostgreSQL |
| Cache | Redis (ioredis) |
| Queue | BullMQ (simple) / RabbitMQ (enterprise) |
| Auth | NextAuth.js / JWT + bcrypt |
| Testing | Vitest + Playwright |
| Monitoring | Prometheus + Grafana + Pino |
| CI/CD | GitHub Actions |
| Deploy | Vercel + Railway/Fly.io |
All 13 rules in .claude/rules/ must be followed:
- clean-code.md — Variables, functions, SOLID, async/await
- code-style.md — 2-space indent, single quotes, semicolons
- error-handling.md — AppError class, centralized handler
- tech-stack.md — Approved technologies only
- system-design.md — CAP, caching, scaling patterns
- project-structure.md — Layered architecture
- api-conventions.md — REST standards, response envelopes
- naming-conventions.md — Cache keys, DB, queues, env vars
- database.md — Prisma patterns, N+1 prevention
- security.md — CRITICAL — Never violate
- monitoring.md — Prometheus, Grafana, alerting
- testing.md — 80% coverage minimum
- git-workflow.md — Conventional commits
# Clone repository
git clone <repo-url>
cd ai-agent
# Copy to your project
cp -r .claude/ /path/to/your/project/
# Or use as template# In Claude Code, use slash commands:
/spec "User authentication feature"
/plan
/build
/test
/review
/deploy"Act as the Frontend Developer and build the login page"
"As Systems Architect, design the notification system"
"Code Reviewer: review this PR for security issues"
"Test Engineer: write tests for the payment flow"
Every code review evaluates:
- Correctness — Does it work? Edge cases?
- Readability — Can others understand it?
- Architecture — Follows patterns? Appropriate abstractions?
- Security — Input validation? Auth? No secrets?
- Performance — N+1? Pagination? Async?
RED → Write failing test
GREEN → Write minimal code to pass
REFACTOR → Improve while green
Build features end-to-end, not layer-by-layer:
✅ Task 1: User can create task (DB + API + UI)
✅ Task 2: User can view tasks (DB + API + UI)
❌ Task 1: Create all DB models
❌ Task 2: Create all API routes
Never commit:
.envfiles- API keys, secrets, passwords
.claude/settings.local.json
Always:
- Use environment variables
- Validate all inputs
- Hash passwords (bcrypt >= 12 rounds)
- Parameterize queries
- Follow the development workflow (
/spec→/plan→/build) - Ensure all tests pass
- Run
/reviewbefore submitting PR - Follow conventional commit format
- Workflow inspired by addyosmani/agent-skills
- Best practices from Software Engineering at Google
- Clean Code principles from Robert C. Martin
Code Web Khong Kho
| Platform | Link |
|---|---|
| facebook.com/codewebkhongkho | |
| TikTok | @code.web.khng.kh |
| Website | codewebkhongkho.com |
Made with care by Code Web Khong Kho