NodeJSmith/i-quieter

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

MANDATORY PREPARATION

Read ~/.claude/skills/i-frontend-design/SKILL.md for design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /i-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 not answered by design context (design/context.md, .impeccable.md, or design/direction.md), STOP and call the AskUserQuestion tool to clarify. Use the answer to inform your refinement strategy. If the answer is unclear or deferred, proceed by reducing color count, not content.

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.

---

Propose Changes

After analyzing the current state, present your proposed changes to the user:

1. Assessment: What's wrong and why (your domain analysis above)
2. Proposed changes: Specific changes ranked by impact, with rationale
3. Verification plan: What to check after implementation (LLM self-check items + Playwright verification if available)

Then STOP and confirm before implementing:

AskUserQuestion:
  question: "Here's what I propose. How would you like to proceed?"
  header: "Confirm"
  options:
    - label: "Implement"
      description: "Looks good — go ahead and make these changes."
    - label: "Refine scope"
      description: "I want to adjust what's included before you start."
    - label: "Challenge this first"
      description: "I'll run /mine.challenge against your proposal before we proceed."
    - label: "Stop here"
      description: "Don't implement anything. The proposal is in this conversation only."

If "Implement" → proceed to implementation below. If "Refine scope" → ask what to change, update proposal, re-confirm.

<!-- CHALLENGE-CALLER -->

If "Challenge this first" → invoke /mine.challenge inline against the proposal, read findings, revise proposal, re-present this gate. If "Stop here" → end the skill.

---

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)

Also review the anti-patterns reference — many anti-patterns describe over-designed AI defaults that quieter work should move away from.

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.

Completion

After implementation, summarize in conversation:

1. Changes made: List each file changed and what was done
2. Verification: LLM self-check results (anti-pattern scan, consistency check). Note if Playwright was available for visual verification.
3. Suggested next step: Any follow-up skills that would complement this work (e.g., after /i-typeset, suggest /i-polish for a final pass)