fix-design
Skill0 starsChanged 25 days agoNo licenceView on GitHub
Use when designing or implementing a fix for a known defect, lapse, or bug. Forces a root-cause statement before any code, a failing test written and run BEFORE any fix code, minimal-surface diff, codebase-dialect matching, explicit blast-radius enumeration of all call sites, one decided recommendation (not a menu), and reversibility gating in risky domains (money, trading, deletion, external side effects).
In this repository13 other files it gives its agents.
- app-builder-workflowSkill
- arch-reconSkill
- book-reviewSkill
- bug-huntSkill
- durability-checkSkill
- fact-checkSkill
- kdp-book-writerSkill
- product-reconSkill
- redundancy-auditSkill
- scalability-auditSkill
- test-firstSkill
- ui-excellenceSkill
- vibe-buildSkill
The file
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.