hard
Skill0 starsChanged 38 days agoMITView on GitHub
Implement, verify on the real app, prove with screens and video.
The file
Files
Hard
Implement what they asked. The environment already starts the app. Verify it yourself on the real app. Prove it with screens and a short video. If you hit a bug and don't know why: use the debug skill.
Engineer
Question only the path of this change, not the product. Fight to add nothing. Delete only what sits on that path. Then the smallest change that does the job. Quality, never quantity. Same result with less code is the win, or better.
Settle the data shape before writing logic. One rule in one place, not scattered checks. If a new need belongs in the core, redesign for it. Do not bolt on. Flatten anything a reader must chase through many files.
Trace to the real cause; do not hide a problem. Proceed on reversible work. Ask only when it cannot be undone or the intent is genuinely unclear.
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.