armor

Deep-dive interview to flesh out a spec

Walkthrough branch changes with teaching-focused feedback

Write a concise recap to LOG.md

Review recent changes using specialized agents

Type design analyst — use when introducing new types, reviewing type changes in PRs, or refactoring existing types. Provides qualitative feedback and quantitative ratings on encapsulation, invariant expression, usefulness, and enforcement.

Error handling auditor — use when reviewing code changes for silent failures, inadequate error handling, inappropriate fallback behavior, or any code that could suppress errors. Invoke after completing work involving catch blocks, fallback logic, or error paths.

Test reviewer — use when reviewing tests in a diff, PR, or recently modified spec files. Drives a discussion by asking the questions that separate valuable tests from theater. Flags tautologies, over-mocking, framework-testing, vague names, and tests that would still pass if the prod code were gutted.

Expert second opinion — use when stuck on complex coding problems, architectural decisions, or technical challenges. Consults an external model for validation and synthesizes the response.

Jira ticket manager — use when creating, updating, or querying Jira tickets. Handles epics, stories, tasks, and bugs with proper formatting and project conventions.

Audit an API, CLI, or config surface for what it makes easy (affordances) and what it makes easy to get wrong (anti-affordances, footguns). Finds the pit-of-success versus the footgun, and the smell where the primary use is smooth but the secondary use is awkward. The principle: good design you act through without noticing; bad design makes you fight it. Use when designing or reviewing a public interface, library, SDK, or command surface. Triggers on "API ergonomics", "is this easy to misuse", "footgun", "pit of success", "review this interface", "review this CLI", "ergonomics".

Become a REST client and QA a live API against its spec. Spawns subagents to hit the server with real requests, finds gaps where the spec lies, and compiles feedback. Use when auditing or hammering an existing API implementation against its OpenAPI/Swagger contract.

Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.

Guidelines for authoring reusable UI components. Use when asked to create new frontend features, components, or design-adjacent tasks.

Diátaxis documentation framework — the four kinds of documentation (tutorials, how-to guides, reference, explanation) and how to apply the framework iteratively. This skill should be used whenever classifying documentation types, reviewing docs for boundary violations (a doc trying to be both a tutorial and reference), deciding how to structure new documentation, or applying the Diátaxis compass to improve existing docs. Also trigger when the user mentions "Diátaxis", "four kinds of documentation", "tutorial vs how-to", "documentation types", or asks whether a doc should be a tutorial, how-to, reference, or explanation.