nix-config

Ensures markdown files conform to rumdl linting rules and personal formatting preferences. Use when creating or editing .md files, or when user mentions formatting, linting, or rumdl.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Reference for writing and editing skills well - the vocabulary and principles that make a skill predictable.

Implement a piece of work based on a PRD or set of issues.

Ensures issue titles conform with a specific style. Use when creating or editing an issue.

Ensures PR (Pull Request) titles conform with a specific style. Use when creating or editing a PR.

Patterns for invoking the GitHub CLI (gh) from agents. Covers structured output, pagination, repo targeting, search vs list, gh api fallback. Use when calling GitHub CLI, namely the `gh` command.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Turn the current conversation into a PRD and publish it to the project issue tracker - no interview, just synthesis of what you've already discussed.

Compact the current conversation into a handoff document for another agent to pick up.

Configure this repo for the engineering skills - set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other skills depending on the output of this skill.

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

A relentless interview to sharpen a plan or design.

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

Formats section separator comments in source files. Use when writing or editing comments that function as section separators.

Writes commit messages following the Conventional Commits specification. Use when writing a commit message or when user mentions commit message, commit, or conventional commits.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Auto-formats edited files using the project's formatter. Use after editing any source code file when a formatter is available.

Validates edited files have no LSP errors or warnings, auto-fixes them if possible. Use after editing any source code file when an LSP is available.

Ensures markdown frontmatter conforms with personal preferences. Use when creating or editing .md files in which frontmatter exists.