aesthetic-direction-framework

name

aesthetic-direction-framework

description

Define the sensory identity of a game — how it looks, sounds, and feels in service of the vision and pillars. The bridge between design intent and sensory execution. Use this skill when: (1) establishing the visual, audio, and tactile identity for a new project, (2) a game "feels wrong" and the sensory layer may be misaligned with mechanics or vision, (3) pillar changes require aesthetic re-evaluation (bidirectional with Skill 2), (4) defining art direction or audio direction pillars, (5) establishing game feel targets (juice, responsiveness, weight), (6) ensuring sensory coherence across all elements, (7) defining component aesthetics for tabletop (table presence, material quality). Co-equal with Design Pillars (Skill 2) at Tier 2. Medium-agnostic.

Aesthetic Direction Framework

The sensory identity of the game. Not "what does it look like?" but "what does every sense experience in service of the core fantasy?" This is MDA's Aesthetics made actionable.

Aesthetic Components

1. Art Direction Pillars

Visual identity expressed as principles, not specifications. Art direction pillars are not "the character wears blue" — they are "every visual element reinforces the feeling of isolation in vastness."

Define:

• Visual philosophy — What feeling should every frame/scene/card communicate?
• Color strategy — Not a palette, but a philosophy. (Muted earth tones for grounded realism? Saturated primaries for arcade energy? Limited palette for focus?)
• Silhouette language — Can every important element be identified by silhouette alone? What does shape communicate? (Sharp angles = danger, curves = safety, asymmetry = unease)
• Detail philosophy — Where does detail live and where is it absent? (High detail on characters, low on environments? Uniform detail everywhere? Detail as reward?)
• Visual hierarchy — What does the player's eye go to first, second, third?

2. Audio Direction Pillars

Sound is half the experience and gets a fraction of the design attention. Define it early.

Define:

• Music philosophy — Adaptive or fixed? Layered or monolithic? Diegetic or non-diegetic? When does music play and when does silence speak?
• Sound design philosophy — Realistic or stylized? Punchy or subtle? How does sound communicate game state?
• Silence as design tool — Where is silence used deliberately? Silence before a boss. Silence after a critical decision. Silence as tension.
• Audio feedback loop — How does sound reward player actions? (Satisfying click of card placement, crunch of a critical hit, chime of resource collection)
• Ambient philosophy — Does the world have a soundscape? Does it change with game state?

3. Game Feel Targets

The tactile/kinesthetic dimension — how the game feels in the hands, whether those hands hold a controller or cards.

For digital games:

• Responsiveness — Input-to-response latency target. Frame-perfect? Deliberately weighty?
• Juice — Screen shake, particles, freeze frames, camera movement. How much? Where?
• Weight — Does movement feel heavy or floaty? Do impacts feel solid?
• Animation philosophy — Snappy or fluid? Anticipation-action-recovery or instant?

For tabletop games:

• Component tactility — Card stock weight, token material, dice feel, miniature vs. meeple
• Table presence — What does the game look like mid-play from across the room? Does it invite curiosity?
• Interaction feel — How does it feel to place a worker, flip a card, roll dice? Physical satisfaction matters.
• Box/shelf presence — Size, weight, visual impact. First impression.

4. Sensory-Emotion Mapping

Map aesthetic choices to intended emotional beats. For each key moment in the player experience:

MOMENT: [Description of the game moment]
INTENDED EMOTION: [What the player should feel]
VISUAL: [How visuals deliver this emotion]
AUDIO: [How sound delivers this emotion]
FEEL: [How tactile/kinesthetic elements deliver this emotion]

Example:

MOMENT: Player discovers a hidden area
INTENDED EMOTION: Wonder, reward for curiosity
VISUAL: Sudden expansion of space, new color palette, increased detail
AUDIO: Music layer adds, ambient sound shifts, discovery chime
FEEL: Camera pulls back smoothly, brief pause in gameplay to let it breathe

Tabletop example:

MOMENT: Player reveals a critical card
INTENDED EMOTION: Tension breaking into triumph or dread
VISUAL: Card art designed for dramatic reveal (information hierarchy top-to-bottom)
AUDIO: Table reaction (designed for — the card should provoke gasps)
FEEL: Card physically separated from the deck, revealed by flipping (not drawing from hand)

5. Coherence Checklist

All sensory layers must reinforce the same fantasy. Run this check:

• Visual style serves the core fantasy (not just "looks cool")
• Audio style matches visual style (a pixel art game with orchestral audio is a deliberate choice, not an accident)
• Game feel matches the fantasy weight (a stealth game should not feel like an arena shooter)
• UI/HUD aesthetic (when designed later) will fit naturally into this identity
• Key emotional moments have all three sensory layers aligned
• Nothing in the aesthetic contradicts a design pillar
• The aesthetic is distinctive enough to identify in a screenshot/photo (attention niche)

Bidirectional Relationship with Design Pillars (Skill 2)

Aesthetic Direction and Pillars sit at the same tier and inform each other:

• A pillar like "Readable Chaos" demands an aesthetic where complex states are visually parseable — this constrains color strategy, silhouette language, and UI clarity
• An aesthetic commitment to "hand-painted storybook warmth" might reshape how a pillar about procedural generation manifests
• A pillar about "Earned Mastery" implies audio feedback that rewards skill (satisfying sounds for precise execution)
• When they conflict, resolve against Vision (Skill 1) — which resolution better serves the core fantasy?

Always cross-reference when either skill's outputs change.

Workflow

Establishing aesthetic direction for a new project

1. Gather inputs — Core fantasy and player persona from Vision (Skill 1), initial pillars from Skill 2
2. Draft art direction pillars — What visual philosophy serves the fantasy?
3. Draft audio direction pillars — What sonic identity serves the fantasy?
4. Define game feel targets — How should this feel in the hands?
5. Map sensory-emotion connections — For 3-5 key moments, how do all layers align?
6. Run coherence checklist — Do all elements agree?
7. Cross-check with Pillars (Skill 2) — Bidirectional alignment
8. Identify reference touchstones — 3-5 existing games/films/music that capture aspects of the intended aesthetic (not to copy, but to communicate intent)

Aesthetic reality check

When "something feels off" but the mechanics seem right:

1. Identify the moment or system that feels wrong
2. Check sensory-emotion mapping — is the intended emotion clear? Are all three layers delivering it?
3. Check for aesthetic-pillar misalignment — does the aesthetic contradict what the mechanics are trying to achieve?
4. Check for internal aesthetic contradiction — do different sensory layers conflict with each other?
5. Propose resolution and flag to Coherence Engine (Skill 0)

Outputs

This skill produces:

1. Art direction pillars — visual philosophy, color strategy, silhouette language, detail philosophy
2. Audio direction pillars — music philosophy, sound design, silence, feedback, ambience
3. Game feel targets — responsiveness, juice, weight (digital) or tactility, presence (tabletop)
4. Sensory-emotion mapping — key moments mapped to visual + audio + feel delivery
5. Coherence checklist — verified alignment across all sensory layers
6. Reference touchstones — 3-5 existing works that capture the intended aesthetic

These outputs feed into:

• Skill 2 (Pillars) — bidirectional, may reshape or be reshaped by pillars
• Skill 4 (Experience) — aesthetic delivers the emotional arc
• Skill 5 (Pitch) — pitch must convey the sensory identity
• Skill 7 (Core Loop) — game feel targets shape how the loop plays
• Skill 13 (Levels) — visual/audio pacing per encounter
• Skill 15 (Prototype) — aesthetic fidelity targets for prototype
• Skill 21 (Tech Bridge) — aesthetic has technical requirements
• Skill 18 (UI/UX) — interface must fit the sensory identity