quieter
Skill571 starsChanged 3 months agoApache-2.0View on GitHub
Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.
We split this skill into the rules it gives an agent
11 rules. 10 are common, 1 is distinctive, and 0 are very specific to this project.
10
Common
Most of the 28 edited versions we read keep these.
1
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 34
If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.
- Common: line 40
Create a strategy to reduce intensity while maintaining impact:
- Common: line 56
Reduce color variety: Use fewer colors more thoughtfully
- Common: line 59
Tinted grays: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness
- Common: line 60
Never gray on color: If you have gray text on a colored background, use a darker shade of that color or transparency instead
- Common: line 64
Hierarchy through subtlety: Use weight, size, and space instead of color and boldness
- Common: line 76
Remove decorative animations: Keep functional motion, remove flourishes
- Common: line 78
Refined easing: Use ease-out-quart for smooth, understated motion—never bounce or elastic
- Common: line 79
Remove animations entirely: if they're not serving a clear purpose
- Common: line 88
Remove all color (quiet ≠ grayscale)
- Common: line 95
Ensure refinement maintains quality:
“Common” is measured: kept by at least 6 in 10 of the 28 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
Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.
MANDATORY PREPARATION
Invoke /frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.
Assess Current State
Analyze what makes the design feel too intense:
- Identify intensity sources:
- Color saturation: Overly bright or saturated colors
- Contrast extremes: Too much high-contrast juxtaposition
- Visual weight: Too many bold, heavy elements competing
- Animation excess: Too much motion or overly dramatic effects
- Complexity: Too many visual elements, patterns, or decorations
- Scale: Everything is large and loud with no hierarchy
- Understand the context:
- What's the purpose? (Marketing vs tool vs reading experience)
- Who's the audience? (Some contexts need energy)
- What's working? (Don't throw away good ideas)
- What's the core message? (Preserve what matters)
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.
Plan Refinement
Create a strategy to reduce intensity while maintaining impact:
- Color approach: Desaturate or shift to more sophisticated tones?
- Hierarchy approach: Which elements should stay bold (very few), which should recede?
- Simplification approach: What can be removed entirely?
- Sophistication approach: How can we signal quality through restraint?
IMPORTANT: Great quiet design is harder than great bold design. Subtlety requires precision.
Refine the Design
Systematically reduce intensity across these dimensions:
Color Refinement
- Reduce saturation: Shift from fully saturated to 70-85% saturation
- Soften palette: Replace bright colors with muted, sophisticated tones
- Reduce color variety: Use fewer colors more thoughtfully
- Neutral dominance: Let neutrals do more work, use color as accent (10% rule)
- Gentler contrasts: High contrast only where it matters most
- Tinted grays: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness
- Never gray on color: If you have gray text on a colored background, use a darker shade of that color or transparency instead
Visual Weight Reduction
- Typography: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate
- Hierarchy through subtlety: Use weight, size, and space instead of color and boldness
- White space: Increase breathing room, reduce density
- Borders & lines: Reduce thickness, decrease opacity, or remove entirely
Simplification
- Remove decorative elements: Gradients, shadows, patterns, textures that don't serve purpose
- Simplify shapes: Reduce border radius extremes, simplify custom shapes
- Reduce layering: Flatten visual hierarchy where possible
- Clean up effects: Reduce or remove blur effects, glows, multiple shadows
Motion Reduction
- Reduce animation intensity: Shorter distances (10-20px instead of 40px), gentler easing
- Remove decorative animations: Keep functional motion, remove flourishes
- Subtle micro-interactions: Replace dramatic effects with gentle feedback
- Refined easing: Use ease-out-quart for smooth, understated motion—never bounce or elastic
- Remove animations entirely if they're not serving a clear purpose
Composition Refinement
- Reduce scale jumps: Smaller contrast between sizes creates calmer feeling
- Align to grid: Bring rogue elements back into systematic alignment
- Even out spacing: Replace extreme spacing variations with consistent rhythm
NEVER:
- Make everything the same size/weight (hierarchy still matters)
- Remove all color (quiet ≠ grayscale)
- Eliminate all personality (maintain character through refinement)
- Sacrifice usability for aesthetics (functional elements still need clear affordances)
- Make everything small and light (some anchors needed)
Verify Quality
Ensure refinement maintains quality:
- Still functional: Can users still accomplish tasks easily?
- Still distinctive: Does it have character, or is it generic now?
- Better reading: Is text easier to read for extended periods?
- Sophistication: Does it feel more refined and premium?
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.
Other versions34 projects use a version of this.
Word for word · 5
- HK-hub/AgentSkills★ 6100% same
- arnabdeypolimi/claude_code_setup★ 4100% same
- huangzida/skills★ 2100% same
- freshpomelo/agent_skills★ 0100% same
- lucaszb-orla/claude-skills★ 0100% same
Edited · 27
- nexmoe/DayBee★ 42495% same
- nexmoe/eve★ 42195% same
- Southclaws/storyden★ 33995% same
- 10xChengTu/Mux0★ 33797% same
- theexperiencecompany/gaia★ 32097% same
- AkaraChen/aghub★ 271100% same
- zacharyfmarion/openscad-studio★ 23891% same
- jagrat7/linux-wallpaper-engine★ 20898% same
- owshq-mec/semana-ai-data-engineer★ 12295% same
- rwliebs/Dossier★ 8895% same
17 more not listed
Wrote their own version · 2
- educlopez/ui-craft★ 398same name
- Zack-Grogan/agentos-foundation★ 0same name
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.
Used alongsideProjects with it also use layout, shape and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
HAR5HA-7663Skillshape
Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.
Also in 11 projects that use this
VercelSkillvercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Also in 3 projects that use this
In this repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adaptSkill
- animateSkill
- arrangeSkill
- auditSkill
- bolderSkill
- clarifySkill
- colorizeSkill
- critiqueSkill
- delightSkill
- distillSkill
- extractSkill
- frontend-designSkill
- hardenSkill
- normalizeSkill
- onboardSkill
- optimizeSkill
- overdriveSkill
- pixijs-accessibilitySkill
- pixijs-applicationSkill
- pixijs-assetsSkill
- pixijs-blend-modesSkill
- pixijs-colorSkill
- pixijs-core-conceptsSkill
- pixijs-createSkill
- pixijs-custom-renderingSkill
- pixijs-environmentsSkill
- pixijs-eventsSkill
- pixijs-filtersSkill
- pixijs-html-sourceSkill
- pixijs-mathSkill
- pixijs-migration-v8Skill
- pixijs-performanceSkill
- pixijs-scene-containerSkill
- pixijs-scene-core-conceptsSkill
- pixijs-scene-dom-containerSkill
- pixijs-scene-gifSkill
- pixijs-scene-graphicsSkill
- pixijs-scene-meshSkill
- pixijs-scene-particle-containerSkill
- pixijs-scene-spriteSkill
- pixijs-scene-textSkill
- pixijsSkill
- pixijs-tickerSkill
- polishSkill
- teach-impeccableSkill
- typesetSkill
- cohub-appsSkill
- cohub-boardSkill
- cohub-generateSkill
- cohubSkill
- public-filesSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

