skills/quieter/SKILL.md
Reduce visual intensity, saturation, and noise while preserving hierarchy and character. Use when the structure is basically sound but the design feels too loud, bold, garish, aggressive, or overstimulating—not when the real problem is structural clutter, too many features, or not enough personality.
npx skillsauth add aladicf/better-web-ui quieterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.
Users start this workflow with /quieter. Once this skill is active, load $frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow that protocol before proceeding — if no design context exists yet, you MUST load $setup first.
Consult the hierarchy checklist when quieting the design depends on de-emphasis, grayscale hierarchy, or clearer action priority. Consult the spacing system when calmness should come from better grouping and rhythm rather than just less saturation. Consult the personality levers when the design needs to stay distinctive while becoming more restrained. Consult the ai slop detection when "quieter" risks drifting into generic, trend-safe blandness. Consult the surface separation when removing intensity means using fewer borders, fewer unnecessary cards, quieter shadows, or calmer background shifts.
Analyze what makes the design feel too intense:
Identify intensity sources:
Understand the context:
If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.
CRITICAL: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness.
Quiet design usually comes from fewer competing decisions, not from draining all the life out of the interface.
Create a strategy to reduce intensity while maintaining impact:
IMPORTANT: Great quiet design is harder than great bold design. Subtlety requires precision.
Systematically reduce intensity across these dimensions:
NEVER:
Ensure refinement maintains quality:
Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality.
development
Build or improve a UI testing strategy covering visual regression, interaction testing, and accessibility assertions. Use when the user asks to add tests, set up testing, fix flaky tests, improve test coverage, validate UI behavior, catch visual bugs, or establish confidence in shipping frontend changes.
development
Design security-conscious interfaces that protect users without frustrating them. Use when the user asks about MFA, password UX, breach notifications, trust indicators, secure forms, account recovery, or making security feel safe rather than scary.
development
Design or improve search experiences, result presentation, and filtering interfaces. Use when the user asks to add search, redesign search results, improve findability, build autocomplete, add filters, or fix zero-results dead ends.
development
Plan, implement, or improve an internationalization and localization strategy for UI content, formatting, and regional adaptation. Use when the user asks to add i18n, localize, translate, support multiple languages, handle regional formats, manage locale switching, or build a multilingual product.