ux-feedback-and-performance
Skill4 starsChanged 5 days agoMITView on GitHub
Fix slow-feeling UI, missing loading acknowledgement, stale or optimistic success messages, unclear progress, duplicate submissions, and async state feedback.
In this repository55 other files it gives its agents.
- design-balance-and-proportionSkill
- design-brand-and-art-directionSkill
- design-buildSkill
- design-color-theorySkill
- design-diagnoseSkill
- design-hierarchy-and-emphasisSkill
- design-imagery-and-textureSkill
- design-layout-and-gridSkill
- design-movement-and-flowSkill
- design-reviewSkill
- design-rhythm-and-patternSkill
- design-typographySkill
- design-unity-and-systemsSkill
- design-validateSkill
- security-api-files-and-realtimeSkill
- security-authentication-and-sessionsSkill
- security-authorizationSkill
- security-browser-and-originSkill
- security-buildSkill
- security-configuration-and-secretsSkill
- security-crypto-and-dataSkill
- security-dependencies-and-buildSkill
- security-diagnoseSkill
- security-injection-and-validationSkill
- security-logging-and-failureSkill
- security-reviewSkill
- security-threat-model-and-designSkill
- security-validateSkill
- ux-accessibilitySkill
- ux-buildSkill
- ux-controls-and-inputsSkill
- ux-decisions-and-loadSkill
- ux-diagnoseSkill
- ux-forms-and-errorsSkill
- ux-journeys-and-motivationSkill
- ux-navigation-and-structureSkill
- ux-onboarding-and-learningSkill
- ux-reviewSkill
- ux-trust-and-ethicsSkill
- ux-validateSkill
- ux-visual-hierarchySkill
- wcag-alternatives-and-mediaSkill
- wcag-assistive-tech-and-statusSkill
- wcag-buildSkill
- wcag-diagnoseSkill
- wcag-forms-and-error-preventionSkill
- wcag-keyboard-and-focusSkill
- wcag-language-and-predictabilitySkill
- wcag-navigation-and-discoverySkill
- wcag-pointer-and-touchSkill
- wcag-reviewSkill
- wcag-semantics-and-reading-orderSkill
- wcag-time-and-motionSkill
- wcag-validateSkill
- wcag-visual-and-responsiveSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 14
Read references/playbook.md for symptoms, differential diagnosis, proven repair patterns, tradeoffs and test cases.
- Distinctive: line 18
Verify the repaired journey including one edge case.
≈ “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
Responsiveness, visibility of state and waiting
Scope
Apply this specialist skill only when the user's task implicates responsiveness, visibility of state and waiting. If the problem is merely adjacent, do not broaden the user's scope.
Procedure
- Read
references/playbook.mdfor symptoms, differential diagnosis, proven repair patterns, tradeoffs and test cases. - Establish the actual user goal and evidence. Do not assume causal failure from a visual screenshot alone.
- Identify the primary failure mechanism; consider alternative root causes before choosing a fix. Relevant Laws of UX: doherty-threshold, selective-attention, goal-gradient-effect, zeigarnik-effect, peak-end-rule.
- Recommend or implement a specific change, preserving functional, accessibility, security and consent constraints. Use existing design patterns/components in the user's project.
- Verify the repaired journey including one edge case. State what was observed versus what remains hypothetical.
Related workflows
For broad reviews, issue IDs, and severity classification use ux-review and ux-diagnose. For coding tasks use ux-build; for acceptance checks use ux-validate. Specialist guidance is advisory, not authority to change code or expand scope.
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.