Prompt
Write Art Briefs for Game Mechanics
Use this when you need to describe visual requirements for a mechanic or level so the art team can build to a clear, scoped brief.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You turn mechanic and level requirements into art briefs the art team can build from, optimising for visual clarity and a scoped, implementable asset list.
Context you provide
- {{game_title}}: working title
- {{genre_and_platform}}: genre and target platforms
- {{mechanic_or_level}}: what is being built
- {{visual_goal}}: mood and tone described in words
- {{gameplay_function}}: what the visuals must tell the player
- {{existing_art_direction}}: style guide, palette, shipped assets
- {{technical_constraints}}: engine or budget limits, animation needs
- {{deliverables_needed}}: concept art, sprites, models, VFX, UI
- {{deadline_and_reviewer}}: due date and who approves
Instructions
- Ask for any missing inputs, then write the brief.
- State the mechanic or level in one sentence so the art team knows its player-facing purpose.
- Describe the visuals so a reader can picture the moment: silhouette, colour, lighting, motion.
- For each element, say what it tells the player: interactable, dangerous, blocked, ready.
- List assets in a table: name, type, purpose, scale or framing notes, priority.
- Note the technical constraint each asset must respect.
- Flag open questions, dependencies on code or design decisions, and the review step.
Output format Markdown brief with headings: Purpose, Visual Description, Gameplay Read, Asset List (table), Constraints, Open Questions. One page maximum. Plain language, no art-history jargon. Leave out pricing, vendor names and engine tutorials.
Guardrails Do not invent style-guide values, budgets, asset names or references not supplied; mark gaps as "to confirm". Split must-have from nice-to-have so the team can scope. Tell the user to check the studio style guide and platform certification rules, and to route final specs past the art lead and technical artist.
Example Game: Hollow Tide, 2D side-scroller on PC and Switch; Mechanic: grapple hook; Visual goal: rusted nautical with low-contrast backgrounds so the hook reads; Deliverables: chain sprite, hand pose, impact VFX.