Archive228

Before fixing any bug, write a test that reproduces it and watch it fail. Use for every bug fix.

The English summary is being prepared. Showing the original description.

Use when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including clarifying questions.

The English summary is being prepared. Showing the original description.

One sentence that describes WHEN to invoke this skill. Write it as a trigger phrase, not a summary — include the words a user would say ("fix bug", "add feature", "review diff"). The agent routes on this field.

The English summary is being prepared. Showing the original description.

Use before claiming work is complete, fixed, or passing — before committing, opening a PR, or handing off. Requires running the verification command in THIS turn and reading its output before any success claim.

The English summary is being prepared. Showing the original description.

Systematically remove one harness component at a time and measure impact, killing scaffolding that no longer earns its complexity.

The English summary is being prepared. Showing the original description.

Validate and constrain untrusted input at the boundary. Use on any handler that accepts external data.

The English summary is being prepared. Showing the original description.

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

The English summary is being prepared. Showing the original description.

Write a PR description a reviewer can approve fast. Use when opening any pull request.

The English summary is being prepared. Showing the original description.

Test the boundary between two systems by the contract, not the implementation. Use for APIs, integrations, and shared interfaces.

The English summary is being prepared. Showing the original description.

Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception.

The English summary is being prepared. Showing the original description.

Flatten deeply nested conditionals into readable, early-return code. Use on any function with 3+ levels of indentation.

The English summary is being prepared. Showing the original description.

Undo a bad change without nuking unrelated work. Use when a specific commit or change broke something.

The English summary is being prepared. Showing the original description.

Write and read the between-session handoff file so a fresh agent with no memory can pick up where the last one stopped without re-deriving context. Structured prose, not JSON — the model writes prose better.

The English summary is being prepared. Showing the original description.

Negotiate a pre-code contract between generator and evaluator personas that defines what "done" means before any code is written. Turns fuzzy specs into a testable target the evaluator can hold the generator to.

The English summary is being prepared. Showing the original description.

Write safe, reversible database migrations for this repo's conventions. Use for any schema change.

The English summary is being prepared. Showing the original description.

Use for ANY bug, test failure, crash, or unexpected behavior. Forces reproduce-then-isolate before proposing a fix. Stops the agent from guessing.

The English summary is being prepared. Showing the original description.

Read git log since initial scaffold + last 3 progress notes, draft feature additions to a SEPARATE suggestions file so feature_list.json stays immutable

The English summary is being prepared. Showing the original description.

Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.

The English summary is being prepared. Showing the original description.

Rebase, squash, or rewrite history without losing work or breaking shared branches. Use before any history rewrite.

The English summary is being prepared. Showing the original description.

Get JSON out of the model reliably. Prefer tool_use with a schema over prompted-JSON, validate on receive, retry on parse fail. Use when downstream code will parse the response.

The English summary is being prepared. Showing the original description.

Design the three states every data UI forgets. Use for any component that fetches or lists data.

The English summary is being prepared. Showing the original description.

Find the untested code paths that actually matter, not just the coverage percentage. Use after adding tests.

The English summary is being prepared. Showing the original description.

Capture an architectural decision so the next session (or engineer) knows WHY. Use after any non-obvious technical choice.

The English summary is being prepared. Showing the original description.

Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.

The English summary is being prepared. Showing the original description.