ux-audit
Skill0 starsChanged 28 days agoMITView on GitHub
Systematic UX audit for Spark and Energy platform. Checks component consistency, accessibility, duplicate elements, responsive layout, and interaction patterns. Run before any demo or commit.
28 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- carlsz/ux-agent-skillstheir own version, first seen Nov 15, 2026
- undark-ai/Meta-Ads-OStheir own version, first seen Nov 15, 2026
- lobehub/lobehubtheir own version, first seen Nov 15, 2026
- thensls/nsls-builder-toolkittheir own version, first seen Nov 13, 2026
- AhmedAbdelfattah0/AI-Skillstheir own version, first seen Nov 12, 2026
- dundas/thinkruntheir own version, first seen Nov 9, 2026
Other versions28 projects use a version of this.
Word for word · 2
- naman10parikh/penny★ 0100% same
- naman10parikh/turbo★ 0100% same
Edited · 2
- naman10parikh/agentgrid★ 999% same
- naman10parikh/wikimem★ 899% same
Wrote their own version · 24
- lobehub/lobe-chat★ 86ksame name
- lobehub/lobehub★ 86ksame name
- thedesignproject/agent-skills★ 101same name
- drvoss/everything-copilot-cli★ 49same name
- carlsz/ux-agent-skills★ 18same name
- EliaAlberti/ux-audit-skill★ 17same name
- kevin-burns/claude-skills★ 11same name
- AhmedAbdelfattah0/AI-Skills★ 4same name
- paulunemoon/ux-audit-skill★ 4same name
- AhmedMerza/agent-skills★ 2same name
14 more not listed
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 repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-runtimeSkill
- frontend-designSkill
- architectSkill
- deep-thinkSkill
- design-systemsSkill
- ecosystem-referenceSkill
- fractal-delegationSkill
- harness-reviewSkill
- heartbeatSkill
- integrate-resourcesSkill
- llm-council-critiqueSkill
- loop-createSkill
- mcp-setupSkill
- memory-compressionSkill
- memorySkill
- model-routingSkill
- oss-project-scaffoldSkill
- playwright-cliSkill
- repo-scoutSkill
- self-improveSkill
- skill-creatorSkill
- skill-routingSkill
- sprintSkill
- test-visualSkill
- troubleshootSkill
- Accessibility AuditorSkill
- artifacts-builderSkill
- brand-guidelinesSkill
- canvas-designSkill
- frontend-patternsSkill
- design-mirrorSkill
- design-system-starterSkill
- design-to-codeSkill
- feature-design-assistantSkill
- figma-implement-designSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- mobile-designSkill
- motion-canvasSkill
- pixel-agent-uiSkill
- pixel-animateSkill
- pixel-anti-slopSkill
- pixel-brain-pageSkill
- pixel-migrate-next16Skill
- pixel-rsc-boundarySkill
- pixel-ship-gateSkill
- premium-web-designSkill
- senior-frontendSkill
- shadcnSkill
- tailwind-design-systemSkill
- tailwind-patternsSkill
- theme-factorySkill
- ui-design-systemSkill
- ui-ux-pro-maxSkill
- ux-researcher-designerSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
After building or modifying any UI component
- Distinctive: line 9
Before presenting work to Naman
- Distinctive: line 11
When onboarding a new page to the platform
“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When to Use
- After building or modifying any UI component
- Before presenting work to Naman
- As part of /wrap-up session protocol
- When onboarding a new page to the platform
UX Audit Checklist
1. Component Consistency
- No duplicate elements (avatars, indicators, icons showing twice)
- Consistent spacing (px-4/px-6 pattern, not mixed)
- Same border radius pattern (rounded-xl for cards, rounded-2xl for containers)
- Color tokens used everywhere (no hardcoded hex outside globals.css)
- All interactive elements have hover states with
hover-liftor color change
2. Layout & Responsiveness
- Mobile-first: every page works on 375px width
- No horizontal scroll on any breakpoint
- Navigation accessible on mobile (hamburger or stack)
- Text readable without zoom (min 14px body, 11px smallest)
- Cards stack on mobile, grid on desktop
3. Loading & Streaming States
- Every async action shows loading state
- Streaming text has cursor indicator
- No flash of unstyled content (FOUC)
- Skeleton or shimmer for data-dependent areas
- Error states are user-friendly (not raw error messages)
4. Accessibility Basics
- All buttons have accessible names (text or aria-label)
- Links with icons have title attributes
- Color contrast meets WCAG AA (4.5:1 for text)
- Focus indicators visible on keyboard navigation
- Form inputs have labels or placeholders
5. Brand Consistency
- Warm black background (#141312), not pure black
- Instrument Serif for display text (font-display class)
- Poppins for body (font-sans)
- Rose-500/600 for Spark accent, purple for Energy platform
- Bento-style asymmetric grids (not uniform)
6. Interaction Patterns
- Enter key submits forms
- Escape key closes modals/menus
- Back navigation works (no dead ends)
- Empty states guide user to action
- Success feedback on mutations (save, delete, send)
How to Execute
Method A: Code Review (No Browser)
1. Grep for common UX antipatterns:
- Duplicate components in same view
- Missing loading states (isLoading without UI)
- Hardcoded colors outside theme
- Missing error boundaries
- Non-responsive layouts (fixed widths)
2. Check component tree:
- Each page has proper hierarchy
- Shared components extracted (not copy-pasted)
- State doesn't leak between routes
3. Review all pages systematically:
/spark → landing
/spark/chat → chat interface
/spark/pricing → pricing
/spark/history → date history
/spark/settings → preferencesMethod B: Browser Testing (Preferred)
1. Start dev server: pnpm --filter @energy/web dev
2. Use Chrome extension or --chrome flag
3. Navigate each page in sequence
4. Check mobile view (375px) and desktop (1440px)
5. Test all interactive flows:
- Onboarding → Chat → Save Plan → View History
- Settings → Save → Return to Chat
- Pricing → Checkout flow
6. Screenshot and report issuesMethod C: Automated Checks
# TypeScript compilation (catches missing props, wrong types)
pnpm --filter @energy/web exec tsc --noEmit
# Build check (catches import errors, SSR issues)
pnpm --filter @energy/web build
# Lint (catches code quality issues)
pnpm --filter @energy/web exec next lintCommon UX Bugs to Watch For
| Bug | Cause | Fix |
| Duplicate avatar/icon | Two components both rendering same element | Remove redundant one |
| Flash of wrong content | Client-side check without hasChecked guard | Add loading gate |
| Scroll jump on new message | Missing smooth scroll or wrong ref | useEffect with scrollIntoView |
| Input loses focus | Component re-render replacing input | Use controlled component with ref |
| Mobile nav overflow | Too many items in row | Collapse to hamburger or hide |
| Stale data after action | Missing state refresh after mutation | Re-fetch or update local state |
Output Format
## UX Audit — [Page Name] — [Date]
### Issues Found
1. **[SEVERITY]** Description — File:line — Fix
### Passed Checks
- [x] Component consistency
- [x] Loading states
...
### Recommendations
- Consider adding...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.

