Apexyard

ApexYard

  Take agent-built code the last mile — safely to production.

AI can build quickly. Shipping safely needs a system.

AI can produce a working prototype in a weekend. Teams still need a way to
track decisions, review changes, run checks, and approve a release.

ApexYard provides that system. Every change starts with a ticket. An
independent reviewer checks the change. A merge gate stays closed until a
named human approves the exact commit.

ApexYard is a multi-project ops repo. You fork it, register your projects,
and manage the portfolio from one place. Shared rules, project records, and
shell hooks keep the workflow consistent.

Claude Code is the default driver. The rules, hooks, and templates are plain
Markdown and shell, so you can use another coding tool through an adapter.
There is no service to run and no hosted lock-in.

The workflow has been used with TypeScript and AWS Lambda backends, Next.js
apps, Chrome extensions, and native Swift macOS apps.

What makes it different

What's inside

ApexYard is a set of plain-text files. Claude Code reads them from the repo
root. No runtime or service is required.

- 20 roles across 6 departments (engineering, product, design, security, data, architecture) that activate on triggers
- 60 shell hooks that mechanically enforce the SDLC — ticket-first edits, a two-marker merge gate, migration gates, secrets scanning, and more
- 69 slash-command skills — from /setup, /handover, and /scaffold to /decide, /code-review, /migration, and /launch-check
- 23 sub-agents — Rex (code review), Hakim (security), Tariq (design review), plus the department personas
- 22 rule files, workflow docs, and document templates (PRD, tech design, ADR, AgDR, C4 diagrams)

See docs/whats-inside.md for the full directory and component…