
from claudefiles8
Analyze designs and introduce a small, accessible color palette with semantic roles and verification steps — consults design context before proposing changes.
Helps agents introduce and apply color strategically to user interfaces and designs. The skill defines a context-gathering protocol, evaluates where color improves hierarchy or meaning, proposes a compact palette (2–4 accents plus neutrals), and provides step-by-step plans for implementation, accessibility checks, and verification. It emphasizes restraint and WCAG-compliant contrast.
Use when a user asks to "fix the colors", create a color system, improve palettes, or increase visual warmth/clarity. The skill requires running a context-gathering step first (design context or an upstream skill) and will stop to ask clarifying questions if necessary. Triggers: "fix the colors", "palette", "color system", "contrast", "theming".
Designed for agents capable of multi-step conversational gating and running verification tooling where available (LLM-based checks, Playwright for visual tests). Works well with agents that can ask user questions and confirm before implementing changes.
A design-focused skill that guides agents in strategically introducing color to UI designs. It's well-written with clear steps for assessment, planning, and implementation, including accessibility considerations and a confirmation gate before making changes. No scripts included — pure instruction-based. Relies heavily on other skills in the claudefiles suite (i-frontend-design, i-teach-impeccable) which limits standalone usability.
Well-crafted design instruction skill. Good accessibility awareness (WCAG, color blindness). OKLCH color space recommendation is modern and correct. The dependency chain on other claudefiles skills reduces portability but makes sense within its ecosystem.