skills

Use when choosing between competing technical approaches, recording why an architecture decision (ADR) was made, or revisiting a previous ADR

Translate ambiguous natural language specifications into a formal Intermediate Verification Language (IVL). Use when users provide English specs, requirements, or descriptions of desired behavior and need unambiguous, verifiable specifications. Triggers include phrases like "specify this", "formalize this", "make this unambiguous", "write a spec for", "write specs", "formal specs", "formal specification", "specify this project", "specify this codebase", or when reviewing English specs like SPEC.md files for ambiguities. Also use when asked to create formal specifications for an existing codebase by first exploring it to understand its behavior, then formalizing that behavior into IVL.

Review and improve prompts for Claude using Claude 4 best practices. Use when writing system prompts, optimizing agent instructions, or when the user asks to review/improve prompts with /prompting.

Analyze and fix code quality issues (KISS, YAGNI, DRY, SOLID, etc.). Use when reviewing code quality, refactoring, or checking for code smells.

ALWAYS use when creating git commits. Formats commit messages using Conventional Commits standard with gitmoji emojis.

Use when implementing any feature or bugfix, before writing implementation code

Creates, installs, validates, and formats Agent Skills. Use when developing skills from templates, installing skills from git repositories, linting against the specification, or managing skills across AI coding agents.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification