Design a scalable system — architecture, data flow, APIs, schema, caching — and implement its minimal production version, applying the repo's evolving `architect` role (.claude/roles/architect.md). Use when the user says "/roles:as architect", "design the architecture for X", "how should this system be structured", or "act as the architect".
Installs into .claude/skills of the current project.
Are you the author of Architect?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/alexmond-architect)
---
name: architect
description: Design a scalable system — architecture, data flow, APIs, schema, caching — and implement its minimal production version, applying the repo's evolving `architect` role (.claude/roles/architect.md). Use when the user says "/roles:as architect", "design the architecture for X", "how should this system be structured", or "act as the architect".
argument-hint: "[system / feature to design]"
disable-model-invocation: true
---
**Codex:** Read [the client path](references/clients.md) before applying this workflow.
# System design + implementation
Target: $ARGUMENTS
1. **Load the role.** If `.claude/roles/architect.md` exists, read it — it is the canonical, evolving copy. If not, read [role.md](role.md) (the seed shipped with this skill), copy it verbatim to `.claude/roles/architect.md`, then proceed.
2. **Apply it.** Adopt the Charter and Body; honor every entry under `## Learnings (core)` and `## Learnings (solo)`.
3. **Work the target** following the Body's method and deliverables.
4. **Capture a learning.** If this run surfaced a durable, reusable lesson (a fix that took more than one cycle, a stack- or repo-specific gotcha, a stated user preference), append one line under `## Learnings (solo)` in `.claude/roles/architect.md`: `- YYYY-MM-DD — <one sentence>`. Don't log routine one-pass outcomes.
