thebar
Skill1 starsChanged 27 days agoNo licenceView on GitHub
A universal reset: a short checklist for judging work against the ideal end state, and the one operation that applies it. Invoke /thebar when the agent is deep in details and off track: overthinking, overengineering, or cutting corners. The reset works out the ideal from scratch (what are we building, for whom, what is their ideal end state, what is the cleanest implementation with the fewest moving parts that works), then applies it backward (compare it with the whole current approach, plan included), sideways (the validity rule over review findings: a finding is valid exactly when the ideal implementation would not contain the flaw it names), or forward (at the start of a slice, the ideal itself is the output). Use when the user says "boil the ocean", "raise the bar", "ideal end state", "from first principles", "no half-measures", or "hold the line". Run it on yourself, unasked, when you notice these warning signs in your own work: a third consecutive fix to the same spot, a guard for a state with no concrete example, sleep or retry loops appearing, a "for now" in a comment, special cases piling up around one boundary. Self-contained: it depends on no other skill and proposes no contract changes. It names the differences, and the session rebuilds from there.
In this repository26 other files it gives its agents.
- agent-browserSkill
- brainstormingSkill
- broSkill
- clean-roomSkill
- copywritingSkill
- cut-stateSkill
- designingSkill
- design-knowledgeSkill
- design-reviewSkill
- distillSkill
- factsSkill
- grillingSkill
- interface-craftSkill
- marketing-psychologySkill
- planningSkill
- positioningSkill
- principlesSkill
- product-designSkill
- product-marketing-contextSkill
- readableSkill
- readbackSkill
- sharpenSkill
- show-meSkill
- stop-slopSkill
- writing-clearly-and-conciselySkill
- zen-reviewSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

