clean-options
Skill2 starsChanged 50 days agoMITView on GitHub
Propose 2-3 design approaches with trade-offs for a task and wait for the user's choice. Only when explicitly invoked.
In this repository2 other files it gives its agents.
- clean-codeSkill
- clean-sweepSkill
The file
Files
Reply in this shape, no preamble, then stop and wait:
Objetivo: <one line>
A. <name>: <what, 1 line>. Coste: <1 line>. Archivos: <list>
B. ...
C. only if truly different
Recomiendo: <letter>, <one reason>.
A is the simplest thing that works. Each option a different design, max three. No option may weaken types or suppress checks. After the user chooses, implement only that one.
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.