output
Skill3 starsChanged 5 months agoMITView on GitHub
Execution discipline for shipped UI. Use to make sure generated frontend work is actually complete, with no placeholders, no skipped sections, no half-finished states, every interactive state handled, and the brief honestly met.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- HurricaHjz/second-yourselftheir own version, first seen Nov 9, 2026
- HurricaHjz/SecondSelftheir own version, first seen Oct 20, 2026
- fuadnafiz98/skillstheir own version, first seen Oct 15, 2026
- jienigoto/ai-skill-upgradestheir own version, first seen Jun 24, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- HurricaHjz/second-yourself★ 150same name
- HurricaHjz/SecondSelf★ 150same name
- fuadnafiz98/skills★ 0same name
- jienigoto/ai-skill-upgrades★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- brandkitSkill
- design-systemSkill
- fluidSkill
- redesignSkill
- refineSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If the brief lists five sections, build five, fully.
- Distinctive: line 22
Every link goes somewhere.
- Very specific: line 26
Before saying it is done, re-read the brief and confirm each requirement is actually met, not approximated.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Output
The difference between a demo and a shippable build is finish. This is a short checklist the agent runs before calling UI work done.
No placeholders
- No "lorem ipsum", no "TODO", no "[image here]", no empty
href="#". Use real or plausible content. - No "rest of the component" comments, no skipped sections. Write the whole thing.
Every state
- Loading, empty, error, and success states for anything that fetches or submits.
- Hover, focus-visible, active, and disabled for every interactive element.
- Responsive: the layout holds at 375px, 768px, and 1280px. No horizontal scroll on mobile.
Honest completeness
- If the brief lists five sections, build five, fully. Do not stub the last two.
- Every link goes somewhere. Every button does something or is clearly disabled.
- Accessibility: alt text, labels, visible keyboard focus, body contrast 4.5:1.
Pre-flight
Before saying it is done, re-read the brief and confirm each requirement is actually met, not approximated. Run the fluid detector. If anything is stubbed, finish it first.
Pairs with: every other skill. This is the last gate before shipping.
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.

