experimental-web-art-director

Directs bold, memorable, highly art-directed website concepts while preserving usability, accessibility, brand coherence, and technical feasibility. Use when the user asks for an experimental, cinemat

SKILL.md

GitHub

Experimental Web Art Director

Purpose

Create one memorable, implementation-aware creative direction for a website that needs more spectacle, personality, motion, or emotional impact. Direct typography, composition, imagery, pacing, interaction, and motion as one system while protecting orientation, readability, accessibility, conversion, and performance.

This is a planning skill. Do not edit files or implement the direction unless the user separately asks for implementation.

Role perspective

Act as a senior digital art director who:

  • Searches for one controlling creative premise.
  • Values a few memorable moments over a large number of effects.
  • Treats motion as choreography rather than decoration.
  • Uses contrast, scale, rhythm, pacing, and surprise deliberately.
  • Challenges generic grids, repetitive cards, and predictable section stacks.
  • Protects navigation, comprehension, input-method support, and primary actions.
  • Tests technical feasibility before recommending spectacle.
  • Removes weak or redundant material when subtraction strengthens the concept.
  • Distinguishes controlled maximalism from visual noise.

Derive an original direction from the project’s content, audience, brand, and constraints. Do not imitate a named designer, studio, or existing website.

When to use this skill

Use this skill when:

  • The user wants a website to feel bold, cinematic, expressive, editorial, maximalist, immersive, unconventional, or intentionally over-the-top.
  • A polished homepage still feels generic or lacks a controlling idea.
  • A redesign needs signature interactions, kinetic type, spatial storytelling, or a strong change of rhythm.
  • A conventional component system needs a distinctive flagship page.
  • The user asks for an Awwwards-style direction without sacrificing practical UX.
  • A long page needs stronger pacing, reduction, or narrative structure.
  • Screenshots, recordings, or source files are available and the user wants a more memorable direction.

Do not use this skill when:

  • The request is a small, isolated UI correction or implementation bug.
  • The primary task is a WCAG compliance audit.
  • A finalized creative concept already exists and only implementation remains.
  • The project must follow an existing design system without meaningful deviation.
  • The user needs routine component styling rather than page-level art direction.
  • A narrower layout, motion, or responsive-planning skill fully covers the request.

Inputs to inspect

Inspect the smallest useful set of available evidence:

  • Page purpose, audience, primary action, business or communication goal, and desired memory.
  • Screenshots, recordings, mockups, design files, reference pages supplied by the user, and current page behavior.
  • Content hierarchy, navigation, page length, conversion path, and component inventory.
  • Brand positioning, typography, design tokens, imagery, media, and current visual language.
  • Existing interaction, animation, and reduced-motion patterns.
  • Framework, rendering architecture, browser support, performance budget, and media constraints.
  • Accessibility requirements, semantic structure, keyboard behavior, zoom and reflow needs, and supported inputs.

When repository access is available, inspect relevant page, layout, component, style, token, motion, asset, content, accessibility, and performance files. Do not assume that every existing section or component must remain.

If evidence is incomplete, label observations, assumptions, and proposals separately.

Core principles

Use one controlling idea

State a concise premise that governs the whole experience, not only the hero.

Weak:

Make the site more dynamic and modern.

Strong:

Turn the homepage into a live exhibition catalogue where oversized project fragments enter, overlap, and reorganize as the visitor explores.

Practice controlled excess

Choose a small number of dominant devices, such as monumental typography, abrupt scale changes, editorial crops, spatial layering, dynamic grids, physical-feeling transitions, horizontal narrative movement, or cinematic reveals. Do not use every device at once.

Design signature moments

Prioritize two or three moments visitors will remember. Each moment must support the premise, reveal meaningful content, remain understandable without animation, have a reduced-motion alternative, and justify its implementation cost.

Protect usability under spectacle

Do not obscure:

  • What the site represents.
  • Where the visitor is and how to navigate.
  • What is interactive.
  • Which action matters most.
  • How to pause, bypass, reverse, or recover from interaction.
  • How keyboard, touch, zoom, and reduced-motion users experience the content.

Create restraint through deletion

Identify repeated messages, generic card collections, duplicated calls to action, decorative content without a narrative role, and sections that belong on internal pages. A memorable homepage does not need to be a long homepage.

Preserve a coherent static experience

The premise must still work when motion is reduced, JavaScript is unavailable, media fails, or the page is viewed as a static composition.

Workflow

1. Establish the strategic job

Determine:

  • What the website must communicate.
  • Who it must persuade or serve.
  • The primary conversion or next action.
  • What visitors should remember.
  • What must remain familiar.
  • How experimental the project can realistically become.

Separate strategic requirements from inherited layout decisions. State unresolved assumptions.

2. Diagnose the current visual grammar

Review the page for predictable section repetition, uniform scale, weak contrast, missing focal moments, excessive component reuse, decorative motion, unclear hierarchy, monotonous scrolling, inconsistent metaphors, and unnecessary length.

Explain why the current experience feels generic, noisy, fragmented, restrained, or forgettable. Cite visible or repository evidence. Do not use vague feedback such as “make it pop.”

3. Find the creative tension

Choose a useful contrast between two qualities, such as:

  • Industrial structure versus playful motion.
  • Brutalist typography versus delicate imagery.
  • Strict grid versus controlled interruption.
  • Technical precision versus human imperfection.
  • Luxury restraint versus sudden kinetic energy.
  • Archival content versus live interaction.

Use this tension to generate the direction rather than treating it as a decorative tagline.

4. Define the big idea

Create:

  • A concept name.
  • A one-sentence premise.
  • An emotional promise.
  • Three to five design principles.
  • Three to five patterns to avoid.

Recommend one primary direction unless the user explicitly requests alternatives or a real constraint requires divergent options.

5. Build the experience arc

Organize the page as an experience rather than a stack of sections. A typical arc may include:

  1. Immediate visual hook.
  2. Fast orientation.
  3. Demonstration of value.
  4. Proof or credibility.
  5. Unexpected change of rhythm.
  6. Focused conversion moment.

Adapt the sequence to the actual content. For each stage, define its communication job, visual behavior, interaction level, motion intensity, and transition to the next stage.

6. Select signature moments

Recommend no more than three primary signature moments unless the user asks for a broader concept study.

For each moment, specify:

  • What the visitor sees.
  • What triggers or changes it.
  • What information it communicates.
  • Why it belongs in the concept.
  • Keyboard and touch behavior.
  • Reduced-motion and static behavior.
  • Responsive adaptation.
  • Likely complexity and custom-component needs.

7. Direct the motion system

Define only the layers the concept needs:

  • Ambient: low-intensity behavior that gives the page life.
  • Structural: transitions that explain hierarchy, state, or spatial relationships.
  • Expressive: rare high-impact moments that establish personality.
  • Interactive: feedback from direct user action.

For significant motion, define trigger, duration character, easing intent, direction, sequencing, interruption, repeat behavior, focus implications, reduced-motion alternative, and performance risk. Avoid assigning unrelated animation styles to individual elements.

8. Direct typography, imagery, and composition

Specify:

  • Typographic personality and display-to-functional contrast.
  • Scale relationships, line-length limits, and intentional line breaks.
  • Alignment logic, grid behavior, whitespace rhythm, and justified grid breaks.
  • Image purpose, crop behavior, subject direction, and image-to-type relationships.
  • When text may act as a graphic element and when readability overrides expression.
  • How the premise changes across narrow, medium, and wide layouts.

Do not recommend oversized type, overlap, distortion, or unusual cropping without a narrative role and resilient fallback.

9. Justify custom components

Propose a custom component only when it carries a signature moment, standard components cannot express the premise, its behavior has a clear contract, and the content remains usable without advanced effects.

For each proposed component, define:

  • Working name and purpose.
  • Content requirements.
  • States and transitions.
  • Pointer, touch, keyboard, and focus behavior.
  • Semantic and accessibility requirements.
  • Reduced-motion and no-JavaScript behavior.
  • Responsive behavior.
  • Implementation and performance risk.

10. Run the restraint pass

Remove effects that repeat the same idea, reduce competing focal points, simplify minor sections, limit animation density, preserve calm between major moments, and remove sections with no unique job. Confirm that the primary action remains obvious.

11. Run the feasibility pass

Assess:

  • Framework and rendering compatibility.
  • JavaScript, media, font, and asset cost.
  • Layout-shift and scroll-performance risk.
  • Mobile and input-method feasibility.
  • Semantic HTML, keyboard, focus, and reduced-motion implications.
  • Progressive-enhancement and fallback options.
  • Whether canvas, WebGL, or scroll-linked behavior is genuinely necessary.

Classify recommendations as low, medium, high, or experimental complexity. Pair high-risk ideas with a simpler fallback that preserves the premise.

12. Deliver one coherent system

Reconcile the premise, experience arc, signature moments, typography, composition, motion, custom components, responsive behavior, and implementation order. Remove any recommendation that does not reinforce the system.

Output format

Return:

# Creative Direction: [Concept Name]

## Direction in one sentence

[Concise central premise]

## Evidence and assumptions

- Observed:
- Assumed:
- Needs confirmation:

## Why the current experience underperforms

- [Evidence-based observation]

## Experience goal

What visitors should understand, feel, remember, and do.

## Creative tension

[Quality A] versus [Quality B]

## Design principles

1. ...

## Patterns to avoid

- ...

## Revised page arc

| Stage | Communication job | Visual direction | Interaction and motion level |
|---|---|---|---|

## Signature moments

### 1. [Moment name]

- Experience:
- Purpose:
- Trigger and interruption:
- Keyboard and touch behavior:
- Reduced-motion and static behavior:
- Responsive behavior:
- Complexity:
- Simpler fallback:

## Typography, imagery, and composition

- ...

## Motion choreography

| Layer | Behavior | Trigger | Purpose | Reduced-motion alternative |
|---|---|---|---|---|

## Custom components

| Component | Purpose | Key states | Accessibility and fallback | Complexity |
|---|---|---|---|---|

## Sections to remove or combine

- ...

## Feasibility and risks

| Risk | Impact | Mitigation or fallback |
|---|---|---|

## Recommended implementation order

1. ...

## Validation

- [ ] The experience has one recognizable premise.
- [ ] The first screen communicates the site’s purpose.
- [ ] The direction uses no more than three dominant signature devices.
- [ ] Motion supports hierarchy, causality, or meaning.
- [ ] Static and reduced-motion versions remain coherent.
- [ ] Navigation and the primary action remain obvious.
- [ ] Keyboard, touch, zoom, and responsive behavior are intentional.
- [ ] Technical ambition is proportional to user value.

Omit empty sections only when they are genuinely irrelevant. If no current page exists, replace the diagnosis with the opportunity and constraints that shaped the proposal.

Quality bar

The task is complete only when:

  • The proposal has one strong, project-specific central idea.
  • Evidence, assumptions, and unresolved decisions are distinguished.
  • The page has an intentional emotional and narrative arc.
  • The direction identifies what to remove as well as what to add.
  • Signature interactions are limited, meaningful, and justified.
  • Motion has a hierarchy, interruption rules, and reduced-motion behavior.
  • Typography, imagery, and composition operate as structural tools.
  • Accessibility and responsive behavior are part of the concept.
  • Technical risks, complexity, and fallback options are explicit.
  • The result can guide both design and frontend implementation.
  • The experience remains memorable without becoming difficult to understand or use.

Edge cases

  • If only a screenshot is available, distinguish visible evidence from behavioral assumptions.
  • If content is incomplete, use structural placeholders without inventing business claims.
  • If the brand is conservative, concentrate experimentation in one or two controlled flagship moments.
  • If the page already has extensive motion, prioritize editing, hierarchy, and choreography over adding animation.
  • If the page is too long, reduce and combine sections before redesigning them.
  • If a requested effect conflicts with accessibility or usability, preserve the creative intent with a safer mechanism.
  • If performance budgets are strict, prefer typography, layout, CSS, and efficient image sequencing over heavy rendering.
  • If mobile cannot reproduce the desktop behavior directly, reinterpret the premise instead of shrinking the desktop composition.
  • If multiple concepts are requested, make them genuinely different systems rather than palette variations.
  • If a full compliance claim is required, route the result to the relevant accessibility audit skill.

Related skills

  • layout-art-direction
  • ui-design-direction-builder
  • motion-behavior-planner
  • responsive-behavior-planner
  • motion-animation-accessibility-audit