ワンクリックで
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 職業分類に基づく
Improve the current branch's changes by getting code reviews in a loop until all feedback is addressed
Improve the current branch's changes by getting code reviews in a loop until all feedback is addressed
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.
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.
| 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.