Instructions for faizkhairi/claude-code-blueprint, covering agents.md: repository orientation for ai assistants, what this repo is, what this repo is not, repository layout and how to help the user.
Instructions for faizkhairi/claude-code-blueprint, covering global claude behavior rules, verify-after-complete (mandatory), what to verify depends on what was built, verification mindset and after verification.
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.
Expert backend engineer for building server routes, API endpoints, database operations, services, and middleware. Adapts to any backend framework based on project context.
Creates and maintains project documentation, README files, API docs, changelogs, and architecture documents. Use after features are completed or when docs need updating.
Expert frontend engineer for building UI components, pages, forms, state management, and client-side logic. Adapts to any frontend framework based on project context.
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.
Designs system architecture, plans features, breaks work into tasks, and makes technology decisions. Use when starting new projects or designing new features.
Mechanical verification of implementation plans. Run on EVERY plan before ExitPlanMode. Checks counts, paths, wiring, policies, examples, and completeness.
MUST use before any git push to main/master/production, or when user mentions 'deploy', 'going live', 'push to prod', 'ready to ship', 'merge to main', 'release'. Also trigger before any npm publish for CLI tools, or on 'audit', 'check vulnerabilities', 'are our deps safe?', 'npm audit', 'yarn audit'. Performs: test…
Structured pre-feature requirements gathering. Run before writing any new feature or API endpoint to clarify scope, acceptance criteria, and technical constraints. Produces: a Requirements Summary (Problem | Scope | Stories | Acceptance Criteria | Out of Scope | Open Questions), presented to the user for confirmation…
Restore session context at the start of every new conversation. Auto-triggers on session start, or when user says 'continue', 'what were we doing', 'where did we leave off'.
Review and post feedback on a GitHub or Gitea pull request end-to-end: fetch the PR diff, run a multi-agent code review, and auto-post the verdict as a real PR review (approve/request-changes/comment) via the platform's API. Triggers on: 'review this PR', 'review PR #N', 'check this pull request', 'post a PR review'…
Register an existing project in memory. Use when starting work on a new repo or when a project needs its own context file. Triggers on: 'register project', 'add project to memory', 'track this project', 'create project file'.
Run a comprehensive multi-perspective code review on recent changes. Also triggers on 'is this secure?', 'security review', 'check for vulnerabilities', 'could this be exploited?' for security-focused review. Produces: GO/NO-GO verdict + findings table (Severity | Category | File:Line | Issue | Recommendation)…