一键导入
i-quieter
Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when auth changes could create drift between runtime, env keys, mocks, UI copy, and docs.
Use when deciding where new files belong and how module boundaries should be preserved.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.
| name | i-quieter |
| description | Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact. |
| user-invokable | true |
| argument-hint | ["TARGET=<value>"] |
Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.
You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and everything else that a great human designer would need as well.
Attempt to gather these from the current thread or codebase.
Do NOT proceed until you have answers. Guessing leads to generic design.
Use the i-frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts.
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.
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.