For agents that write and change code from a brief: a command, a site, a page or a migration.
4 skills
Open encode-lessons# Encode lessons in structureThe second time a lesson comes up, the text failed. Hold it with structure inste- Pick the cheapest guard that holds it: a type, then a lint rule, then a hook o- If the fix is structural, ship only the structural fix. Delete the instruction- If the lesson needs judgement and no guard can hold it, make the line more pro- Record the lesson's origin (the user's words, with the time) on the ticket, noExample: "never auto-compact" was a habit to remember. It became DISABLE_AUTO_CO
I told my agent the same thing twice and it did it again.
Open first-principles# Redesign from first principlesDon't bolt a change onto the current design. Redesign as if the new requirement 1. Read every affected file, type and rule. Know the current design before you c2. Ask: "Writing this from scratch with this requirement, what would we build?" 3. Propagate the change everywhere it reaches: types, states, events, errors cat4. Design the whole redesign, then deliver it in small verifiable steps.Signs you bolted it on: a new optional field or flag beside an old one, a specia
Open lever# Build the leverWhen the work isn't trivial, build the tool that does it. A script does the work- Do the first unit by hand to learn the recipe. Then write the tool, rerun it o- Make it safe to rerun (idempotent).- Codemod for edits, generator for repeated files, a query (sqlite, jq, awk) for- One deterministic pass beats handing units out. If neighbours share the work, - Smallest tool that does the job, never a framework. Scratch levers live in the- If you cite this skill and there is no script, codemod or generator in the res
My agent redoes the same long edit by hand and I can't check it.
Open prove-it# Prove it worksUnverified work has unknown correctness. Check the real thing directly.- Run the real program from outside and read what it prints (a demonstration, de- Check liveness directly (the process, the listener), not state derived from it- When a check fails, suspect the way you looked before you suspect the system.- Script the check when you can, so a reviewer reruns it instead of trusting you- A script that proves a fix is a demonstration, not a new test. Add a test only- Visual results go to the user, shown inline. Their eyes are the check.
encode-lessons: When the same correction comes up a second time, it picks the cheapest guard that holds it (a type, a lint rule, a hook or a script) instead of adding another line of text. first-principles: When a rule changes, it redesigns the type model or module from the start instead of adding another special case. lever: When the work isn't trivial, it has your agent write the script that does it, rerun it on the first unit and diff the result against the hand version. prove-it: Before your agent says it is done, it runs the real program from outside and reads what it prints, instead of trusting a compile, a cached screenshot or its own word.