一键导入
colorize
Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.
Normalize design to match your design system and ensure consistency
Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great.
Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact.
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.
Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.
| name | colorize |
| description | Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive. |
| user-invokable | true |
| args | [{"name":"target","description":"The feature or component to colorize (optional)","required":false}] |
Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality.
You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and especially existing brand colors.
Attempt to gather these from the current thread or codebase.
Do NOT proceed until you have answers. Guessing leads to generic AI slop colors.
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 the current state and identify opportunities:
Understand current state:
Identify where color adds value:
If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
CRITICAL: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose.
Create a purposeful color introduction plan:
IMPORTANT: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more.
Add color systematically across these dimensions:
State indicators:
Status badges: Colored backgrounds or borders for states (active, pending, completed, etc.)
Progress indicators: Colored bars, rings, or charts showing completion or health
#f5f5f5) with warm neutrals
(oklch(97% 0.01 60)) or cool tints (oklch(97% 0.01 250))Use OKLCH for color: It's perceptually uniform, meaning equal steps in lightness look equal. Great for generating harmonious scales.
Ensure color addition improves rather than overwhelms:
NEVER:
#000) or pure white (#fff) for large areasTest that colorization improves the experience:
Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional.