faizkhairi/claude-code-blueprint

A battle-tested, framework-agnostic reference architecture for Claude Code. Beginner-friendly with graduated adoption (minimal / standard / core / full presets). 12 agents, 19 skills, 15 hooks, 6 rules, with reasoning behind every decision.

This repository also configures its own agents. See what claude-code-blueprint tells them →

73Stars on the repository
33Mods indexed here, across every type
22d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

faizkhairi/claude-code-blueprint

Agent Claude Code

Analyzes codebase architecture for structural issues, dependency direction, modularity, and separation of concerns. Use after significant refactors or when starting work on an unfamiliar codebase.

not rated 73 +1 22d ago A 39 tokens original MIT

backend-specialist

02

faizkhairi/claude-code-blueprint

Agent Claude Code

Expert backend engineer for building server routes, API endpoints, database operations, services, and middleware. Adapts to any backend framework based on project context.

not rated 73 +1 22d ago A 35 tokens original MIT

code-reviewer

03

faizkhairi/claude-code-blueprint

Agent Claude Code

Performs comprehensive code review focusing on quality, patterns, and best practices. Use proactively after significant code changes.

not rated 73 +1 22d ago A 26 tokens original MIT

db-analyst

04

faizkhairi/claude-code-blueprint

Agent Claude Code

Analyzes database schemas, queries, migrations, and performance. Use for schema reviews, query optimization, and migration planning across any ORM.

not rated 73 +1 22d ago A 32 tokens original MIT

devops-engineer

05

faizkhairi/claude-code-blueprint

Agent Claude Code

Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.

not rated 73 +1 22d ago A 29 tokens original MIT

docs-writer

06

faizkhairi/claude-code-blueprint

Agent Claude Code

Creates and maintains project documentation, README files, API docs, changelogs, and architecture documents. Use after features are completed or when docs need updating.

not rated 73 +1 22d ago A 35 tokens original MIT

frontend-specialist

07

faizkhairi/claude-code-blueprint

Agent Claude Code

Expert frontend engineer for building UI components, pages, forms, state management, and client-side logic. Adapts to any frontend framework based on project context.

not rated 73 +1 22d ago A 36 tokens original MIT

memory-curator

08

faizkhairi/claude-code-blueprint

Agent Claude Code

Audits your memory directory for orphans, phantom references, index drift, broken wiki-links, stale entries, and near-duplicates. Writes a dated health report. Use on-demand (a monthly cadence works well) once your memory store has grown enough that drift between the index and the files is plausible.

not rated 73 +1 22d ago A 65 tokens original MIT

project-architect

09

faizkhairi/claude-code-blueprint

Agent Claude Code

Designs system architecture, plans features, breaks work into tasks, and makes technology decisions. Use when starting new projects or designing new features.

not rated 73 +1 22d ago A 32 tokens original MIT

qa-tester

10

faizkhairi/claude-code-blueprint

Agent Claude Code

Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.

not rated 73 +1 22d ago A 28 tokens original MIT

security-reviewer

11

faizkhairi/claude-code-blueprint

Agent Claude Code

Reviews code for OWASP Top 10 vulnerabilities, authentication flaws, and injection attacks. Use proactively after writing API endpoints or auth code.

not rated 73 +1 22d ago A 31 tokens original MIT

verify-plan

12

faizkhairi/claude-code-blueprint

Agent Claude Code

Mechanical verification of implementation plans. Run on EVERY plan before ExitPlanMode. Checks counts, paths, wiring, policies, examples, and completeness.

not rated 73 +1 22d ago A 32 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: