Architect.
Architecture decisions, scaling patterns, technology selection. The thinking layer above implementation.
System Design Superbrain.
When the question is HOW SHOULD THIS SYSTEM BE BUILT (not how do I write the code) -- this is the skill. It walks through architecture trade-offs (monolith vs microservices, CQRS vs CRUD, event-driven vs request-response), scales decisions from MVP to production, and forces explicit reasoning over reflex.
Four recipes.
Architecture decision records
ADR template + decision-rationale capture. Every major choice gets a one-page record: context, decision, consequences, alternatives considered. Compounds into institutional memory.
Scale-aware patterns
When to introduce caching, queues, sharding, read replicas, CQRS. Each pattern has thresholds (e.g. introduce Redis when read p99 exceeds 200ms). No premature optimization.
Technology selection matrix
Cost vs maturity vs ops-burden grids for databases, message queues, frameworks. Anti-recommendations (when NOT to use Kubernetes, when NOT to use GraphQL).
Cross-cutting concerns
Auth, observability, secrets, rate-limiting, idempotency keys, retry semantics. Each has a default recipe + the override conditions.
It composes.
Skills compose into workflows. Architect is rarely the only skill you will use — it pairs naturally with these others in the library.
One command.
Installs only stryx-architect (skip the other 19) into ~/.claude/skills/stryx-architect/.
Free for all use.
Stryx Labs License v1.0. Use Architect in personal, commercial, internal, and production work. No attribution required.