harness
Harness Engineering
Transform any code project so AI agents can work in it reliably and autonomously.
The bottleneck is never the agent's coding ability — it's the environment the agent operates in. This skill builds that environment.
Core Principles
These govern every decision:
-
Declarative over procedural — Define what "correct" looks like (verification criteria), not step-by-step procedures. Agents determine how to verify on their own and generate temporary scripts if needed.
-
Recognition over recall — Extract knowledge by showing users detected patterns and asking them to react (choose, confirm, reject). Never ask open-ended "describe your principles" questions.
-
Minimal context footprint — Every generated document must be as concise as possible. Agents read actual code for details. Only externalize knowledge that CANNOT be inferred from code: architectural rules, canonical pattern choices, prohibited actions, business domain terms.
-
Persist invariants, not procedures — Commit architectural rules, lint configs, structural tests (permanent invariants). Never commit task-specific verification scripts — agents create those on-the-fly per task and discard them after.
-
Language-agnostic — Adapt to the project's tech stack. Never assume a specific language, framework, or toolchain.
More from jtsang4/efficient-coding
brainstorming
Use only when the user explicitly asks to do brainstorming (e.g., says 'brainstorm'/'头脑风暴' or invokes $brainstorming). Do not auto-trigger based on general creative work.
17writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
16dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
13subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
13executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
12shape
>
11