Menu
SkillsMP has collected 10 skills from bharat3645/The-Ideal-Harness. Open a skill to review its source and details.
Showing 10 of 10 collected skills.
Pre-emit self-critique for UI/visual/design output (components, CSS, copy, layouts) — anti-slop gates, taste dials, and a design-token contract check, run BEFORE the work is shown, not after. Use whenever producing or editing anything with a visual/UX surface.
Judge or write UI motion (CSS/JS animation, Framer Motion / Motion, transitions, micro-interactions) against context-weighted designer philosophies instead of one universal taste. Use whenever adding, reviewing, or auditing any animation — a hover effect, a…
Answer-first, structured output mode — lead with the action, number multi-step work, restate state across turns, suppress tangents. Use when the user wants to act on your answer immediately, not read around it. A different axis from caveman…
Before brainstorming or coding, interrogate a vague request for scope/constraints AND ground it against real, current docs (not training-data memory) for any library or API it touches. Produces a CONTEXT.md the brainstorming/planning phase consumes. Use at…
Watch this session for corrections, repeated patterns, and judgment calls, and record them as episodic observations for later human-reviewed skill/policy improvement. Use continuously during any non-trivial session, not as a one-shot invocation — the value is…
Execute a multi-task plan as a controller that dispatches one fresh-context subagent per task, reviews each result against the spec, loops fixes, and tracks progress in a durable ledger. Use for any non-trivial build so the controller's context stays lean and…
Write the failing test before the implementation, for a single piece of code — red, green, refactor. A finer grain than the ledger's task-level verify.command (subagent-driven-development); use this INSIDE an implementer's work on one task, not as a…
Bootstrap skill for the Ideal Harness. Explains the installed modules and when to route to them. Injected at session start so the agent knows the harness is active.
Turn a vague request into an agreed design before any code is written. HARD GATE — produce a design and get explicit approval first; do not implement, scaffold, or edit until the user approves. Use whenever a request is non-trivial or under-specified.
Output-side token compression. Write terse, high-signal prose — drop articles, filler, and pleasantries — while keeping all technical substance, code, and errors verbatim. Use when output token volume matters and prose polish does not.