Loading...
Loading...
Found 67 Skills
Shared vocabulary for designing deep modules. Suitable for users who want to design or improve module interfaces, identify deepening opportunities, decide where to place seams, make code easier to test or more navigable for AI, or when other skills require vocabulary for deep modules.
Identify codebase deepening opportunities based on the domain language in CONTEXT.md and decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Use when a Jetpack Compose screen-level composable takes a ViewModel/component/controller, collects state or effects, handles navigation/snackbars, or wires callbacks while also rendering layout.
Clean-room rethink of existing functionality — trace what the code really does, restate it as a problem and a goal, design a solution behind a context wall where the code is unseen (web research for libraries and best practices), then judge the current implementation against that design and propose replace, graft, or keep-as-is. Use when asked whether some code is the best way to solve its problem, to rethink or redesign a module, for a second opinion on an approach, or to find a simpler, more robust, or more testable way to build something that already exists.
Design shared vocabulary for deep modules. Use this when you want to design or improve a module's interface, identify opportunities for deepening, decide where to place seams, make code more testable or navigable by AI, or when other skills require vocabulary for deep modules.
Use when writing or refactoring code, before creating files - enforces separation of pure business logic (Functional Core) from side effects (Imperative Shell) using FCIS pattern with mandatory file classification
This skill should be used when a user wants to identify which parts of a codebase are safe to modify with AI ("vibe code") and which require careful human engineering. It classifies files and modules into Leaf (safe to vibe), Branch (caution), or Trunk (hands off) based on dependency isolation, stability, and external verifiability. Use when users say "find safe places to vibe code", "where can I let AI loose in this repo", "leaf nodes", "vibe-code audit", "can a PM edit this codebase", or when someone points at a directory and asks whether it's safe to let Claude rewrite it. Grounded in Erik Schluntz's (Anthropic) "leaf nodes vs trunks" framework from the "Vibe coding in prod" talk.