art-director

Define brand identity, visual language, and design-system architecture before UI implementation.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill art-director-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: art-director
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/eye-of-the-beholder/skills/art-director
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill art-director-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When building a new product or refreshing a brand, visual choices get made by feel—a hue from a default palette, an arbitrary corner radius—because no brand standard exists in writing. This Skill establishes that standard upfront, producing concrete artifacts (brand brief, visual language document, design-system skeleton) that later UI work can reference instead of re-choosing per feature. ## Core Features & Use Cases - Brand identity discovery: A five-phase process (research, strategy, identity design, touchpoints, governance) based on Alina Wheeler's model, producing a brand.md with positioning, personality, anti-personality, and voice examples. - Visual language translation: Converts brand attributes into concrete decisions across five axes—type, color (in OKLCH), form, motion, and photography/illustration—recorded in visual-language.md with rationale and references. - Design-system architecture: Sets up Nathan Curtis's three-layer token taxonomy (primitive, semantic, component), Brad Frost's atomic component taxonomy, component contracts, semver governance, and deprecation policy. - Use Case: Starting a new SaaS product with no brand yet, you run this Skill once to produce brand.md, visual-language.md, and a design-system/ skeleton; every subsequent feature build then references those artifacts for hues, type, and motion instead of improvising. ## Quick Start Ask the agent to define the visual identity and design-system foundation for your new product using the art-director skill.

Frequently Asked Questions about art-director

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a design system for a new product?▼

Start with brand identity discovery (research, strategy, personality), then translate attributes into a visual language covering type, color, form, and motion. Finally, set up a three-layer token taxonomy (primitive, semantic, component) with atomic component organization and governance rules.

What is the three-layer design token model?▼

Nathan Curtis's model splits tokens into primitive (physical palette like --blue-500), semantic (role-based like --color-accent), and component layers. Application code references only semantic tokens, so a brand change updates one alias instead of every component.

When should I use art direction versus visual review?▼

Use art direction once per project or brand refresh to define the standard upfront. Per-feature visual implementation and per-change visual verification are separate concerns handled by build-time and review disciplines, not by brand definition work.

Why choose brand colors in OKLCH instead of HSL?▼

OKLCH is perceptually uniform, meaning two colors with the same lightness value feel equally light, which is not true in HSL. This keeps a brand hue stable across light and dark themes and aligns with the CSS Color 4 specification.

How do design systems handle token deprecation?▼

Mark tokens as deprecated with comments, add console or linter warnings on usage, and communicate via changelog. Keep a minimum window of two minor releases or six months before removal, which then ships as a breaking major version bump.