Loading...
Loading...
Found 303 Skills
System architecture design for Rust/WebAssembly projects. Creates ADRs, designs APIs, plans module structures, and documents architectural decisions. Never writes implementation code - focuses purely on design and documentation.
Write, edit, or review chapters of an arc42 architecture documentation. Use when user says 'write arc42', 'update the architecture documentation', 'fill out chapter 5', 'arc42 chapter', 'architecture docs', or 'document our building blocks'. Do NOT use for ADRs (use document-decision — ADRs belong inside arc42 chapter 9) or user-facing feature docs (use document-feature).
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.
Create and manage Architecture Decision Records (ADRs) using MADR 4.0.0 format. Use this skill when evaluating technology choices, documenting design decisions, or reviewing past architectural choices.
Guide for creating effective internal technical documentation (READMEs, ADRs, Contribution Guides). Use this skill when the user asks to write, refactor, or improve internal project documentation.
Principal Solution Architect with 15+ years designing scalable distributed systems. Use when making technology choices, designing system architecture, selecting patterns (Saga, CQRS, Event Sourcing), creating ADRs, planning integrations, or addressing scalability concerns.
Research and discovery workflow for document deliverables — competitive analyses, architecture comparisons, ADR scaffolding, literature reviews, vendor evaluations. No TDD requirement. Phases: gathering → synthesizing → completed. Triggers: 'discover', 'research', 'explore topic', or /discover.
Consumer-side wiring for ADR-097 Phase 3 federation_spend events — per-peer rolling windows + suspension-threshold check
System Architect Specialist. Use this to design system architecture, creating C4 models and ADRs (Decision Records).
Deep expertise in E-commerce domain logic (Cart, Checkout, SKU). Trigger this when building shopping features on top of MVC or ADR.
Fetch upstream, rebase, stage all changes, run ADR compliance check on modified artifacts, generate a descriptive commit message from the diff, commit, and push to the current branch's upstream. Handles merge conflicts by preferring local changes for config/project files and upstream for scaffolding.