.agents/skills/quieter/SKILL.md
Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact.
npx skillsauth add TheCardGoat/lorcana-engine quieterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 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, STOP and call the AskUserQuestionTool 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.
documentation
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
tools
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
development
--- name: review-pr-comments description: Systematically process GitHub pull request review feedback end-to-end: pick a target PR, identify unanswered or unresolved comments, handle each thread sequentially, implement required code updates, run repository verification checks, and post clear responses. Use when asked to review PR comments, resolve review threads, or address reviewer suggestions/questions. --- # Review PR Comments Process pull request feedback one thread at a time and finish wit
development
Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great.