원클릭으로
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 the user wants to open a pull request or finish a branch handoff. Read the PR template, inspect changes vs main, run the release skill first if the branch name looks like a version, validate the branch with the shared repo checks, open a draft PR targeting main, and return the preview deployment URL when one applies.
Use when the user asks to take a feature or bug fix from prompt to implementation, especially prompts like "/create a new feature", "build this feature end-to-end", "take this from plan to PR", or "own this change through validation and handoff". This skill is for repo-local delivery workflows that must create and maintain implementation plans, choose appropriate tests, run deterministic validation, open a draft PR against main, and return the preview deployment URL when one is available.
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.
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy to create intentional compositions.
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.
| name | quieter |
| description | Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact. |
| user-invokable | true |
| args | [{"name":"target","description":"The feature or component to make quieter (optional)","required":false}] |
Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.
Use the frontend-design skill — 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.
Analyze what makes the design feel too intense:
Identify intensity sources:
Understand the context:
If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify.
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.