mirror-pairs
Skill78 starsChanged 5 months agoMITView on GitHub
The red-flag lists mirrored between figure-out''s and define''s task files, so a change to one side lands on the other. Use when editing a task file under figure-out/tasks/ or define/tasks/.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architecture-principlesSkill
- bump-surfaces-versionSkill
- design-principlesSkill
- harden-task-fileSkill
- learn-from-sessionSkill
- product-principlesSkill
- prompt-principlesSkill
- sync-claude-code-pluginsSkill
- sync-toolsSkill
The file
Files
Red-flag mirror pairs
figure-out's task files and define's task files are decoupled, so a red-flag list both need lives in both. Change one, change the other:
figure-out/tasks/CODING.md(Shape before build, Already provided, Earned depth, A second shape, What the next agent copies, Design discipline, Recorded intent, Drivable and debuggable, Failure visibility, Silent regression, Verification design's independent expected values and whether example tests can reach the case that breaks, and The verification harness's fit-to-trust question) ↔define/tasks/CODING.mdDefaults (Sketch the shape before implementing, Use what is already provided, Earn each module's depth, Screen for what the next agent copies, Hold the design discipline, Read the intent before removing or adding a guard, Make failure visible and the result drivable, Name what could regress silently, Agree test seams before authoring tests, Reshape, don't patch, Trust the check before relying on it).figure-out/tasks/FEATURE.md(Bundled concerns, Remembered steps, Rollback, Orphaned resources, Driven as the person) ↔define/tasks/FEATURE.mdDefaults (One concern per change, No step that depends on memory, Define rollback strategy) and its Bounded growth and Journeys driven as the person gates.figure-out/tasks/DOCUMENT.md(One mode, A fact restated, The same fact twice) ↔define/tasks/DOCUMENT.mdDefaults (One mode per document, Generate or link what code owns, One copy of each fact).figure-out/tasks/DOCUMENT.mdandWRITING.md(Sources in hand) ↔define/tasks/PROSE_FLOOR.mdAccuracy gate;figure-out/tasks/WRITING.md(The author's own point) ↔define/tasks/WRITING.mdgates.figure-out/tasks/UI.md(Every state, Who and where, Honest figures, First look) ↔define/tasks/UI.md's design gate, whosereview-designstandards cover functional states, access, medium, figure fidelity, and where the eye lands first and the path it follows.figure-out/tasks/PROMPTING.md(A protocol on shared state; A rule in two files, including a contradicted one; An instruction where a check belongs) ↔define/tasks/PROMPTING.mdDefaults (Model a shared protocol before shipping it, One rule, one place).figure-out/tasks/MEASURE.md↔define/tasks/MEASURE.md(the measure proven then frozen, noise floor, fair comparison, unlike scenarios, a floor on attempts).figure-out/tasks/PERF.md↔define/tasks/PERF.md(limiter, bounded gain, verdict).figure-out/tasks/HILLCLIMB.md↔define/tasks/HILLCLIMB.md(quick or thorough, the cheap check's conditions, what a round can afford, what the next round sees, a priority that moves, a judge that can be fooled, one primary with guards; define alone keeps real use against prediction, a measure that could rise without the goal and getting past the nearest peak, which the model raises unprompted in figure-out). define's file states outcomes and the user's rulings, never steps (docs/adr/20261107-climb-guidance-states-outcomes-and-rulings-not-steps.md).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

