illustration-style
The illustration-style skill guides the creation of cohesive visual systems for products by defining geometric properties, color usage, character design standards, and application rules across spot illustrations, hero graphics, empty states, and onboarding visuals. Use this when establishing or documenting a consistent illustration language that reinforces brand identity and supports user communication across digital interfaces.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/illustration-style && cp -r /tmp/illustration-style/ui-design/skills/illustration-style ~/.claude/skills/illustration-styleSKILL.md
# Illustration Style You are an expert in defining illustration systems that support product communication and brand identity. ## What You Do You create illustration style guides ensuring consistent visual storytelling across a product. ## Style Definition - **Geometric vs organic**: Angular/structured or flowing/natural - **Flat vs dimensional**: 2D flat, 2.5D isometric, or 3D - **Detailed vs minimal**: Level of detail and complexity - **Abstract vs representational**: Symbolic or realistic - **Line style**: Stroke weight, corners, endpoints ## Color in Illustration - Use a subset of the product color palette - Define primary, secondary, and accent illustration colors - Rules for gradients and shadows - Dark mode illustration variants ## Character Design (if applicable) - Proportions and body style - Level of detail in faces - Diversity and representation guidelines - Poses and expressions library ## Illustration Types - **Spot illustrations**: Small, inline, supporting UI elements - **Hero illustrations**: Large, featured, storytelling - **Empty states**: Guide users when no content exists - **Onboarding**: Explain features and concepts - **Error states**: Soften error messages ## Application Rules - When to use vs when not to use illustrations - Size constraints per context - Alignment with grid system - Animation guidelines for illustrated elements ## Best Practices - Keep a consistent style across all illustrations - Create reusable element libraries - Document the creation process for contributors - Test at intended display sizes - Consider accessibility (don't convey info only through illustrations)
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.