harness-engineering

Find and fix design smells in breadboards. Use after /breadboarding to validate affordance boundaries, naming, and wiring correctness.

Map a system into Places, UI affordances, Code affordances, and wiring. Use to map existing systems or design new ones from shaped parts.

Add optional ESLint-based mechanical enforcement to steer agents (JS/TS repos).

Bootstrap an agent-first knowledge base in this repository

Onboard an existing repository into the harness-engineering knowledge base and fill in gaps using an automated audit.

Shape the knowledge base with real project context. Replaces placeholders with actual standards, domains, and guardrails.

Fill Phase 0 standards after harness bootstrapping. Alias for /harness-shape.

Start or continue a shaping session — iterate on requirements (R) and solution shapes (S) with fit checks.

This skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with automatic .env file copying and shared-context configuration. Use when spinning up parallel feature branches, code review in isolation, or multi-agent development.

Bootstrap an agent-first knowledge base in any repository. This skill should be used when initializing a new project or adding structured knowledge scaffolding to an existing repo. Supports configurable base directory, new/existing repos, Claude settings with plan directory, and bundled agent capabilities. Invoke via /harness-init.

This skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with automatic .env file copying and shared-context configuration. Use when spinning up parallel feature branches, code review in isolation, or multi-agent development.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Shape Up methodology adapted for LLMs. Three phases: /shaping (iterate on requirements and solution shapes with fit checks), /breadboarding (map systems into Places, UI affordances, Code affordances, and wiring), /breadboard-reflection (find and fix design smells in breadboards). Use when defining problems, exploring solutions, mapping systems, slicing into vertical scopes, or validating breadboard designs.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

4 hooks across 2 events