Skip to content
Agent Orchestration
Skill

/quieter

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.

BOOST
From plugin
ccg
5.9k47 skills19 commands
Install
$ npx -y skills add fengshao1227/ccg-workflow --skill quieter --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/quieter

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

quieter.SKILL.md
name: quieter
description: "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."
argument-hint: "[target]"
user-invocable: false

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:

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

2. **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 using AskUserQuestion.

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

Read more
Ships withccg

多模型协作工作流引擎 — /ccg:go 一个命令,AI 自动分析意图、选择策略、编排 Codex + Gemini + Claude 协作执行

Get the whole plugin

Other skills on ccg.

verify-change
Skill

verify-change

变更校验关卡。分析代码变更,检测文档同步状态,评估变更影响范围。当用户提到变更检查、文档同步、代码审查、提交前检查、diff分析时使用。在设计级变更、重构完成时自动触发。

verify-module
Skill

verify-module

模块完整性校验关卡。扫描目录结构、检测缺失文档、验证代码与文档同步。当用户提到模块校验、文档检查、结构完整性、README检查、DESIGN检查时使用。在新建模块完成时自动触发。

verify-quality
Skill

verify-quality

代码质量校验关卡。检测复杂度、重复代码、命名规范、函数长度等质量指标。当用户提到代码质量、复杂度检查、代码异味、重构建议、lint检查、代码规范时使用。在复杂模块、重构完成时自动触发。

verify-security
Skill

verify-security

安全校验关卡。自动扫描代码安全漏洞,检测危险模式,确保安全决策有文档记录。当用户提到安全扫描、漏洞检测、安全审计、代码安全、OWASP、注入检测、敏感信息泄露时使用。在新建模块、安全相关变…