All 94 skillsPlan and decide9 of 15
stryx:architect
When the hard part is structure: how the parts of a system fit, and the trade-offs between designs.
/stryx:architectInside its piece: 15 specks, one for each file on its shelf. Its fourteen group-mates glow on the open book behind it. The light splits toward red, the band of Plan and decide.
In numbers
counted 2026-10-12 in the installed set- 12reference files
- 1helper scripts
- 15files in the skill
- 206KB on disk
- 12chapters
- 2agents work by this book
Use it when
in the skill’s own wordsWhen designing or changing how a system is structured
- The user says
- architect
- architecture
- system design
- "how should I build this"
- RPI or research-plan-implement
- wants a non-trivial change researched and planned before code (a feature crossing several files or processes, a large refactor, unfamiliar code)
- Choosing between architectural approaches (trade-offs, pros and cons, score this decision, hexagonal / ports and adapters, actor model)
- Writing or enforcing INVARIANTS.md contracts
- Splitting big work into file-bounded parallel sprints
- Reviewing a whole system's architecture
- Deciding Electron process/IPC boundaries, Zustand state placement, sql.js schema or sync design
- For multi-client code ("fork discipline", "check the boundary", "is this core or client", "platform audit", "client separation", "fork test", "clean up the fork")
Not for
another skill does it- What to build→ stryx:brainstorm
- The step-by-step plan→ stryx:taskmaster
- Reviewing a spec or plan→ stryx:plan-review
- A bake-off→ stryx:bakeoff
On its shelf
15 files, 206 KB- references/12
- SKILL.md1
- evals/1
- scripts/1
Inside the book
12 chapters, by title only- Modes
- Research-Plan-Implement (RPI)
- Complexity: how much of each phase
- Sprint decomposition (file-bounded parallel work)
- INVARIANTS.md: architecture contracts a machine checks
- Security
- Architecture
- Architecture verification gate (before implementation starts)
- Done means done (anti-premature-completion)
- The architectural 3-strike rule
- Scope boundaries
- Failure modes: the sign, and what to do
Its helpers
2 agents work by this book- stryx:architect-agentWhen a design question needs its own room: options with trade-offs, or a review of a whole system.
- stryx:database-expertWhen SQLite or sql.js work is needed: schema, migrations, indexes, slow queries, backups.
Works with
the skills it names most- stryx:workflow→When starting or resuming a big piece of work and deciding how much process it needs.
- stryx:plan-review→When a spec, plan or roadmap should be tested for holes before work starts.
- stryx:bakeoff→When two or more very different approaches must each be drafted before you can choose.
- stryx:verify→When Claude is about to say done, fixed or ready to commit: fresh proof comes first.
- stryx:brainstorm→You want something new built: it agrees what to build before any code is written.
- stryx:debug→Something is broken: a bug, an error, a crash, a failing test or wrong data.
Claude loads it by itself when the moment comes; by hand, type the line at the top. It comes with the whole set: Installs all 94 skills, 32 agents and the brain program as one set. The skill’s own text is private source and is not shown here.