Published skills
deep-modules
Use when refactoring into deep modules, choosing seams, classifying dependencies, deciding adapter strategy, or planning tests around a refactor.
code-design
Use when discussing modules, interfaces, implementation, depth, seams, adapters, leverage, locality, or code design terminology.
gh-notifications
Use when working with GitHub notifications.
design
Use when planning, building or designing solutions. Applies to interfaces, data models, algorithms, control flow, architectures, processes, etc.
ai-writing-signs
Patterns in vocabulary, structure, formatting, tone, and citations that are characteristic of LLM-generated text. Avoid these when writing any text.
levels-of-abstraction
Use when discussing levels of abstraction, composed method, SLAP, stepdown rule, or mixed abstraction levels within a function.
open-pr
Use when opening a pull request, pushing changes for review, or when the user says "open PR", "create PR", "send for review", or "get this merged".
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
testing
Use when writing, reviewing, or improving tests, deciding what to mock, or designing interfaces for testability.
review-architecture
Find deep-module opportunities in a codebase. Use when the user wants to improve architecture, refactor, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
refactoring
Use when refactoring code, identifying refactor candidates, or improving design after tests are green.
Category alert