aladicf/better-web-ui

quieter

Reduce visual intensity, saturation, and noise while preserving hierarchy and character.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/aladicf/better-web-ui --skill quieter

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.

MANDATORY PREPARATION

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.


Assess Current State

Analyze what makes the design feel too intense:

  1. 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
  1. 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.

Quiet design usually comes from fewer competing decisions, not from draining all the life out of the interface.

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?
  • De-emphasis plan: Which noisy elements should recede so the true focal point can stay strong?

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
  • Preserve the anchor: Keep enough contrast on the primary action or key message that the screen still has a focal point

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
  • Favor de-emphasis: Often you should quiet the competing elements rather than weakening the most important one

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
  • Use spacing before separators: Extra space or subtle background shifts often work better than another border

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
  • Keep grouping clear: Quiet layouts still need more space around groups than within them

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)
  • Quiet the focal point so much that the screen no longer has a clear center of gravity

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.

来自同一仓库

更多 Skills

全部 Skills
aladicf
社区

data-viz

Design or improve data visualizations, charts, and data presentation interfaces. Use when the user asks to add charts, build dashboards, visualize data, choose chart types, make data accessible, or present metrics and analytics.

1小时安装量
3
GitHub Stars
49
最近更新
5月21日
aladicf
社区

arrange

Improve layout composition, spacing systems, grouping, and visual rhythm. Use when the user mentions weak layout structure, arbitrary spacing, weak grouping, crowded composition, or layout monotony rather than priority/emphasis problems.

1小时安装量
2
GitHub Stars
46
最近更新
5月21日
aladicf
社区

audit

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants measurable accessibility, performance, responsive, theming, or anti-pattern findings—not when they mainly want an overall UX critique or final visual/detail polish.

1小时安装量
2
GitHub Stars
46
最近更新
5月21日
aladicf
社区

critique

Evaluate an interface from a UX perspective, assessing hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring and actionable feedback. Use when the user wants an overall design or UX review—not when the main need is measurable accessibility/performance diagnosis, or final micro-detail polish.

1小时安装量
2
GitHub Stars
46
最近更新
5月21日