Start Building

Lesson 6: Art Direction & Asset Creation

You have a plan and a timeline. Next is turning your art style and scope into a concrete asset list and pipeline so art supports your timeline instead of blocking it. This lesson walks you through defining art direction, creating a style guide, building an asset list, and choosing tools and workflows that fit your team and budget.

What You'll Learn

By the end of this lesson you will be able to:

  • Define art direction and visual style so your game looks consistent
  • Create a simple style guide (mood, color, reference) for yourself or contractors
  • Build an asset list tied to your scope and milestones
  • Choose tools and a pipeline (2D/3D, bought vs custom) that fit your budget
  • Plan asset delivery so art is ready when dev needs it

Why This Matters

Clear art direction prevents scope creep and rework. An asset list keeps you from over-creating or under-creating. A pipeline that matches your tools and team keeps art flowing on time. Without this, art can become the bottleneck or the source of last-minute cuts.

Step 1: Define Art Direction and Visual Style

Before you list assets, lock what the game should look and feel like.

Art direction in one page

  • Mood – One sentence: how should the player feel? (e.g. cozy, tense, silly, epic.)
  • Reference – 5–10 reference images (screenshots, concept art, photos) that capture the look. Save them in a folder or mood board.
  • Constraints – What you will not do (e.g. no realistic blood, no 4K textures, no custom rigs for every character). Constraints keep scope and style consistent.

Visual style

  • Aesthetic – Stylized, realistic, pixel, low-poly, hand-painted, etc. Pick one and stick to it for v1.
  • Color – Dominant palette (e.g. warm/cool, saturated/muted). A simple color script (3–5 main colors) helps you and any contractors stay consistent.
  • Technical – Resolution, format, and engine requirements (e.g. Unity URP, 1024px textures, PNG with alpha). Write this down so assets are engine-ready.

Pro Tip: Share the one-pager and reference folder with anyone who makes art for the game. It reduces back-and-forth and keeps the look coherent.

Common mistake: Skipping reference and describing style only in words. Visual reference is faster and clearer than long written briefs.

Step 2: Create a Simple Style Guide

A style guide is a short document (or board) that anyone creating art can follow.

Include:

  • Mood and references – Link or attach the same references from Step 1.
  • Color palette – Hex or RGB for main colors; note which are for UI, characters, environment.
  • Do and do not – 3–5 "do" examples (e.g. flat shading, simple silhouettes) and 3–5 "do not" (e.g. no gradients on characters, no photorealistic skin). Use small example images if you have them.
  • Technical specs – Canvas size, DPI, format, naming (e.g. char_hero_idle_01.png). Match your engine and pipeline.

Pro Tip: Keep it to one or two pages. A style guide is a guardrail, not a textbook. Update it when you make a deliberate style change.

Common mistake: Making the style guide too long or vague. Short, visual, and specific works better.

Step 3: Build an Asset List Tied to Scope and Milestones

Your asset list should match your v1 scope and map to milestones so art is ready when dev needs it.

Categories (adjust to your game)

  • Characters – Hero, NPCs, enemies. List by name/role and count (e.g. 1 hero, 3 NPCs, 2 enemy types).
  • Environment – Levels, props, tiles, backgrounds. List by level or zone and key assets (e.g. Level 1: 1 background, 10 props, 1 tileset).
  • UI – Buttons, panels, icons, fonts. List screens and elements (e.g. main menu: 3 buttons, 1 background, 1 logo).
  • VFX/Audio – If you are including art for particles or placeholders, list them; otherwise note "use placeholders" or "buy pack."

Tie to milestones

  • For each milestone (e.g. alpha, beta), note which assets must be done by then. Example: "Alpha: hero sprite set, Level 1 background and props, main menu UI."
  • This prevents "we need everything at once" and helps you order work (e.g. hero first, then first level, then UI).

Pro Tip: Use a spreadsheet: columns = asset name, category, owner, status, milestone. Sort by milestone to see what is due when.

Common mistake: Listing every asset you can imagine instead of only what is in v1 scope. Cut the list to match your "Version 1 is done when..." statement.

Step 4: Choose Tools and Pipeline

Your pipeline is how you go from idea to engine-ready asset. It depends on your style (2D vs 3D), budget, and skills.

2D

  • Tools – Aseprite, Photoshop, GIMP, Krita, Spine, etc. Pick one for sprites and one for UI if needed.
  • Pipeline – Sketch → clean art → export at correct size/format → import to engine. Define export settings (resolution, format, naming) once and document them.
  • Bought vs custom – Asset packs can cover placeholders or whole areas (e.g. tilesets, UI kits). If you use packs, note license and how you will make them consistent with your style (recolor, redraw key elements).

3D

  • Tools – Blender, Maya, etc. for models; Substance, Photoshop, etc. for textures. Pick a small set so you are not switching tools every asset.
  • Pipeline – Model → UV → texture → rig (if animated) → export (FBX/GLTF) → import to engine. Define poly count, texture size, and export settings per asset type (hero vs prop).
  • Bought vs custom – Marketplace or kitbash for props and environments; custom for hero and key characters if budget allows. Document what is custom vs bought so you know what to replace or credit.

Pro Tip: Do one asset end-to-end (from concept to in-engine) and write down each step. That becomes your pipeline. Fix bottlenecks (e.g. re-export, wrong size) before scaling.

Common mistake: Using a different process for every asset. Standardize export settings, naming, and folder structure so nothing gets lost or re-done.

Step 5: Plan Asset Delivery So Art Is Ready When Dev Needs It

Art and dev need to align so levels and features are not blocked.

Order of work

  • First – Hero or core character (so movement and animation can be tested).
  • Second – First level or first screen (so the core loop is playable and looks right).
  • Third – UI and feedback (menus, HUD, basic VFX/sound placeholders).
  • Later – Extra characters, levels, and polish. Match this order to your milestone plan.

Handoff

  • Naming – Use a consistent naming scheme (e.g. level1_bg.png, char_hero_walk_01.png) and a single folder or drive for "ready for engine."
  • Versions – If you iterate (e.g. v2 of hero), keep the latest clearly marked so dev does not use an old file.
  • Specs – In the asset list or style guide, note resolution, format, and any engine-specific needs (e.g. pivot point, slicing for UI). One source of truth reduces back-and-forth.

Pro Tip: Sync with your project manager or timeline at least once per milestone. If art slips, adjust the milestone or cut scope; do not assume dev can wait indefinitely.

Common mistake: Delivering all art at the end. Stagger delivery so dev can integrate as they go and you can catch style or technical issues early.

Mini Challenge

  1. Write your art direction in one page: mood, 5–10 references, and 3 constraints.
  2. Add a simple style guide: color palette (3–5 colors), 3 "do" and 3 "do not" with short notes or images.
  3. Build an asset list for v1 only (characters, first level/screen, UI). Use a spreadsheet with columns: asset, category, milestone.
  4. Pick one character or one level and list the exact assets (e.g. hero: idle, walk, jump, attack x4 frames each).
  5. Do one asset from start to engine (or document the steps if you have not made it yet). Write down export settings and naming so the next asset follows the same pipeline.

Save this; you will use it when you plan programming and technical implementation in Lesson 7 and when you prepare for QA and marketing later in the course.

Troubleshooting

"I am not an artist."
Use strong reference and a tight style guide; consider buying asset packs or hiring a contractor for key art. You can still own direction (mood, palette, do/do not) and review against the guide.

"I have too many ideas and the list is huge."
Cut to v1 scope only. Put "nice to have" assets in a separate list for post-launch. Revisit the "Version 1 is done when..." sentence and remove anything that is not required for it.

"My contractor delivers in the wrong format."
Add technical specs and export steps to your style guide and asset list. Do one sample asset together and agree on naming and folder structure before they do the rest.

"Art is always late."
Align asset delivery to milestones and reorder work so the most critical assets (hero, first level, UI) come first. If art slips, move the milestone or cut scope instead of letting dev wait.

Recap and Next Steps

You have:

  • Defined art direction and visual style (mood, reference, constraints).
  • Created a simple style guide (palette, do/do not, technical specs).
  • Built an asset list tied to v1 scope and milestones.
  • Chosen tools and a pipeline that fit your style and budget.
  • Planned asset delivery so art is ready when dev needs it.

In Lesson 7: Programming & Technical Implementation, you will turn your scope and plan into a technical roadmap (engine, architecture, and key systems) so development stays on track and aligned with your art and design.

For more on art and pipelines, see our Game Art and Creating Game Assets guides. Bookmark this lesson and revisit your asset list when you add scope or hire contractors.