Loading...
Loading...
Found 31 Skills
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
System Architect Specialist. Use this to design system architecture, creating C4 models and ADRs (Decision Records).
Diagnoses what makes code complex and why, using the three-symptom two-root-cause framework. Use when code feels harder to work with than it should but the specific problem is unclear. This skill identifies WHETHER complexity exists and WHERE it comes from. Not for scanning a checklist of known design smells (use red-flags) or evaluating a specific module's depth (use deep-modules).
Refactors specified code to improve clarity, reduce duplication, or align with the project's architectural patterns — without changing external behavior. Invoked when the user asks to refactor, clean up, simplify, or restructure code.
Use when designing modules, APIs, and system architecture requiring independent, non-overlapping components where changes in one don't affect others.
Reviews error handling strategy and exception design. Use when the user asks to review error handling, when a module throws too many exceptions, or when callers must handle errors they shouldn't need to know about. Applies the "define errors out of existence" principle with a decision tree for exception strategies.
Explore requirements and approaches through collaborative dialogue before planning implementation