fancy-pants-brief
Skill1 starsChanged 10 days agoNo licenceView on GitHub
The house look for every HTML page an agent makes for a person to read: glass over a random Omarchy wallpaper in that wallpaper's theme, always dark, with gel buttons, a rail of sections and plenty of pictures, and never read-only: every section and figure takes a note, with a copy map and Terminal Delight's one-click send-back to the agent. Built with one tool and passed through one gate. Use whenever you are about to write ANY .html a person will open: a report, a review page, a storyboard, a results or status page, an index, a gallery, a comparison, a preview, a handoff page, a dashboard, a demo page; when a tool you are writing generates HTML for people; when a page came out white, plain or flat; when a page has no notes, no copy map, or \"no commentable sections\"; when the user says \"fancy pants\", \"/fancy-pants-brief\", \"make it look nice\", \"the glass look\", \"Omarchy theme\". A decision brief is one of these pages and keeps its own skill, decision-brief, which wears the same look. NOT for HTML that belongs to another design: a product's or client's own site, an email body, a résumé or invoice that leaves as a PDF, or a scene page a film renders frames from.
In this repository13 other files it gives its agents.
- ai-slopSkill
- articleSkill
- ascii-artSkill
- briefingSkill
- code-tasteSkill
- decision-briefSkill
- hardenSkill
- localizationSkill
- scientific-methodSkill
- storytellingSkill
- td-skinSkill
- udev-rule-deploySkill
- viral-circular-lymricSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
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.