Architecture skills for Codex
Skills for decisions that outlive the sprint: architecture decision records, system design reviews, C4 and Mermaid diagrams, domain-driven design, hexagonal and modular-monolith structure, event-driven systems with sagas and outboxes, resilience patterns, capacity planning and incremental migrations.
curl -fsSL codexskills.dev/install.sh | sh -s -- --category architecture Installs all 25 into ~/.agents/skills/. Or download the zip.
All 25 Architecture skills
Each opens the full SKILL.md, example prompts and every way to install it.
-
API Design Review
Catch contract mistakes before the first client -
API Gateway Patterns
A thin edge that never turns into a monolith -
Architecture Decision Records
Record why you chose it, not just what -
C4 Architecture Diagrams
Context, container and component views as code -
Caching Architecture
Caches with owners, limits and no surprises -
Capacity Planning
Know which resource runs out first, and when -
Clean Architecture
The dependency rule, minus the ceremony -
Dependency Injection
Constructor wiring that makes tests trivial -
Design Docs and RFCs
Docs reviewers can approve after one read -
Design Patterns
Use a pattern only when change demands it -
Distributed Locks
Leases, fencing tokens, or no lock at all -
Domain-Driven Design
Model the business rules where they belong -
Event-Driven Architecture
Events that survive duplicates, reordering and failure -
Event Sourcing and CQRS
Append-only truth, rebuildable read models -
Hexagonal Architecture
Keep frameworks and vendors out of your core -
Mermaid Diagrams
Diagrams from real code that render first time -
Microservice Boundaries
Cut services where change and data actually split -
Modular Monolith
Service-grade boundaries in one deployable -
Multi-Region Architecture
Survive a region outage with numbers to prove it -
Outbox Pattern
Publish if and only if the transaction committed -
Resilience Patterns
Stop one slow dependency from taking you down -
Saga Pattern
Multi-service transactions that undo themselves -
Strangler Fig Migration
Replace legacy one slice at a time, reversibly -
System Design Review
Find what breaks first, with the math to prove it -
Twelve-Factor Apps
One build, any environment, kill it anytime
No Architecture skill matches that.
Where to start
Install the ones that match requests you make every week. Name one with $resilience-patterns when you want it for sure; otherwise Codex picks by description.
Start with
- Resilience PatternsStop one slow dependency from taking you down
- System Design ReviewFind what breaks first, with the math to prove it
- API Design ReviewCatch contract mistakes before the first client
Install a few by name
curl -fsSL codexskills.dev/install.sh | sh -s -- api-design-review api-gateway-patterns 104-line POSIX script. No sudo, no telemetry. Read install.sh
Architecture FAQ
How do I install every Architecture skill at once?
Run curl -fsSL https://codexskills.dev/install.sh | sh -s -- --category architecture to put all 25 in ~/.agents/skills/, or add --project to install them into the current repository's .agents/skills/. You can also download the category zip and unpack it yourself.
Does installing 25 skills slow Codex down?
Hardly. At startup Codex sees only each skill's name and description, a few dozen words apiece, and reads a full SKILL.md only when a task needs it. Install the whole category if the work fits; unused skills cost almost nothing.
Which Architecture skill should I start with?
Start with Resilience Patterns, System Design Review, API Design Review. They cover the requests that come up most in this category. Mention one with $resilience-patterns to try it.