uv-suite

Design system architecture and decompose work into Acts with tasks, dependencies, and cycle budgets. Use after a spec is approved, before coding begins.

Review, test, slop-check, then commit and optionally open a PR. The ship pipeline: one command from "code complete" to "committed and reviewed."

Show all UV Suite skills, agents, hooks, guardrails, and personas. Use when you want to know what's available or how to use a specific feature.

Systematic root-cause debugging. Traces data flow, tests hypotheses, narrows scope. Stops after 3 failed attempts and escalates. Use when something is broken and you don't know why.

Toggle lite mode — instructs the assistant to be terse (no preamble, no summaries, no decorative formatting). Use when tokens are limited or you just want shorter answers. Persists across turns until disabled.

Build an interactive prototype as a static React site. For concept exploration, stakeholder demos, presentations, and documentation websites.

Browser-based QA: exercises the running app via Playwright MCP, captures console errors and visual evidence, optionally fixes source bugs with atomic commits and generates regression tests. Three tiers (quick / standard / exhaustive). Writes uv-out/qa-state.md so /uvs-commit and /ship can detect completion and read the health score.

Multi-specialist code review. Dispatches concern-specific subagents in parallel (security, performance, testing, maintainability, api-contract, data-migration), scores each finding 1-10 for confidence, gates output by tier, and persists state to uv-out/review-state.md so /uvs-commit and /ship can detect completion. Pass --security for a focused tool-backed (Semgrep/Gitleaks/Trivy) OWASP review, --slop for a full anti-slop audit (all six slop categories), or --architecture to audit a design against its recorded Design Constraints (traceability). Note: ambient slop detection also runs as a PostToolUse hook on every write; --slop is the deep on-demand audit.

Manage the UV Suite session lifecycle: label it (init), save a checkpoint, restore a prior checkpoint, end it cleanly, or toggle auto-checkpoints. One skill, subcommand-routed. The automatic counterparts (PostToolUse auto-checkpoint, SessionStart auto-restore) remain hooks. Checkpoints are stored per-session under uv-out/sessions/<session-id>/checkpoints/, so concurrent terminals don't clobber each other.

Convert requirements into a structured technical specification. Use when starting a new feature or receiving vague requirements.

Write tests or LLM evals. Routes to a specialist: the test-writer agent for code tests (unit/integration), the eval-writer agent for AI/LLM evals (--eval). Use after implementing a feature, when coverage is low, or when building/ changing an LLM-powered feature.

Understand code: map a single codebase or a whole multi-service stack. Repo mode produces an architecture overview, domain map, sequence diagrams, and entry points; stack mode maps how services connect (REST, queues, shared DBs, shared libs). Use when entering an unfamiliar codebase or system.