exec-ui-ux
Skill1 starsChanged 28 days agoMITView on GitHub
Execution skill loaded when making decisions about user interface layout, states, or user experience flows.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 7
When building user-facing features, ensure the interface is resilient, responsive, and intuitive:
- Distinctive: line 9
Loading States: Never assume instantaneous network responses.
- Distinctive: line 11
Empty States: If a list or dashboard has no data, design a friendly empty state that guides the user on what to do next.
- Distinctive: line 12
Responsive Design: Ensure layouts do not break on mobile viewports.
- Very specific: line 13
Micro-interactions: Use subtle transitions (e.g., transition-all duration-200) for hover and active states to make the interface feel …
≈ “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.
Files
UI/UX Execution Strategy
When building user-facing features, ensure the interface is resilient, responsive, and intuitive:
- Loading States: Never assume instantaneous network responses. Always design and implement skeleton loaders or spinners for async actions.
- Error States: Handle failures gracefully. Do not show raw stack traces to the user. Provide clear error messages and recovery actions (e.g., a "Retry" button).
- Empty States: If a list or dashboard has no data, design a friendly empty state that guides the user on what to do next.
- Responsive Design: Ensure layouts do not break on mobile viewports. Check text wrapping, tap target sizes (min 44x44px), and overflowing flex/grid containers.
- Micro-interactions: Use subtle transitions (e.g.,
transition-all duration-200) for hover and active states to make the interface feel responsive and premium.
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.