design-interface-polish
Skill376 starsChanged 10 days agoLicence not identifiedView on GitHub
Micro-detail polish for emisar's rendered UI — the small craft that makes an interface feel finished: optical alignment, interruptible motion, icon cross-fades, image outlines, transition specificity, and the LiveView-specific traps around enter animations. Use when building or reviewing a HEEx/Tailwind component or marketing page, polishing details, or when something \"feels off\", \"feels generic\", or you're asked to \"make it feel better\". The macro art-direction layer is `design-creative-director`/`design-review`; this is the detail layer under both.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- infra/AGENTS.mdAGENTS.md
- mcp/AGENTS.mdAGENTS.md
- packs/AGENTS.mdAGENTS.md
- portal/AGENTS.mdAGENTS.md
- runner/AGENTS.mdAGENTS.md
- content-directorSkill
- content-seoSkill
- debug-investigateSkill
- design-creative-directorSkill
- design-frontendSkill
- design-reviewSkill
- design-uxSkill
- elixir-boundariesSkill
- elixir-context-fnSkill
- elixir-iron-reviewSkill
- elixir-new-contextSkill
- elixir-performanceSkill
- elixir-recurrent-jobsSkill
- elixir-testingSkill
- go-engineerSkill
- ops-deploySkill
- ops-releaseSkill
- product-managerSkill
- review-boardSkill
- security-deps-auditSkill
- security-engineerSkill
- tooling-verify-apiSkill
- workflow-specSkill
- workflow-workSkill
- author-packSkill
- connect-llmSkill
- install-emisarSkill
- respond-to-production-incidentsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — 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 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.
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.

