Cluster overview
What this DCC topic cluster covers
Art Direction and Asset Brief Production Guide is the broad overview page for art direction and production planning. It collects related terminology such as Asset List, Art Specification, Style Guide, Visual Target, Mood Board, and Concept Art and explains how those terms split into narrower production checks, vendor notes, and review briefs.
Use this hub when the reader is still choosing the right review path. Use the detailed leaf guides when the task has already narrowed to one file, pass, node, rig behavior, engine import, surface repair, or delivery checklist.
Term map
How the keywords are grouped before review
A cluster page should not pretend every keyword has the same job. Some terms name source controls, some name target outputs, and some name review evidence. Sort them first; then the leaf pages can go deeper without becoming duplicate copies of this overview.
Asset List - The practical question around Asset List is what evidence would make another reviewer agree with the same decision. Asset List (资产清单 / アセットリスト) is useful in a brief only when it points to an inspectable source state. Put the term beside the file, target output, and owner who can verify it. If that proof cannot be attached, the term should remain in review rather than be treated as covered.
Art Specification - Treat Art Specification as a production checkpoint: it should narrow the review, not decorate the page with another synonym. Art Specification (美术规范 / アート仕様) is useful in a brief only when it points to an inspectable source state. Put the term beside the file, target output, and owner who can verify it. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.
Style Guide - Style Guide should be read through 美术管理, not as a loose label in a translation sheet. Style Guide (风格指南 / スタイルガイド) should be tied to the exact part of asset brief, visual target, style guide, revision policy, or delivery list that it changes. Record the setting, reviewer, and proof artifact so the term is not reduced to a loose label. The translation is therefore tied to evidence, not to an isolated glossary row.
Visual Target - When 视觉目标 or ビジュアルターゲット appears in a review note, the English term still needs the file state beside it. Visual Target (视觉目标 / ビジュアルターゲット) can be translated safely only after the production meaning is known. Keep the English label visible when it is also a UI label, plug-in name, or channel name. That keeps the article searchable while still giving art director, producer, or outsourcing lead something concrete to approve.
Mood Board - Mood Board becomes useful only when the reviewer can point to the part of asset brief, visual target, style guide, revision policy, or delivery list that it changes. Mood Board (情绪板 / ムードボード) is useful in a brief only when it points to an inspectable source state. Put the term beside the file, target output, and owner who can verify it. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.
Concept Art - For a vendor-facing brief, Concept Art is the anchor term and the localized labels explain the same inspected state. Concept Art (概念图 / コンセプトアート) can be translated safely only after the production meaning is known. Keep the English label visible when it is also a UI label, plug-in name, or channel name. If that proof cannot be attached, the term should remain in review rather than be treated as covered.
Silhouette Readability - The practical question around Silhouette Readability is what evidence would make another reviewer agree with the same decision. Silhouette Readability (轮廓可读性 / シルエットの可読性) can be translated safely only after the production meaning is known. Keep the English label visible when it is also a UI label, plug-in name, or channel name. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.
Kitbash - Treat Kitbash as a production checkpoint: it should narrow the review, not decorate the page with another synonym. Kitbash (套件拼装 / キットバッシュ) is useful in a brief only when it points to an inspectable source state. Put the term beside the file, target output, and owner who can verify it. The translation is therefore tied to evidence, not to an isolated glossary row.
Search and answer intent
Why the hub stays broad
Searchers may arrive through Visual Target, Mood Board, Concept Art, Silhouette Readability, Kitbash, and Revision / Rework while actually needing a narrower answer. The hub preserves that discovery path without counting as the final proof page for every term.
For GEO, the quotable answer is the routing rule: identify the production surface, choose the leaf guide with the matching proof requirement, and keep Chinese, English, and Japanese wording attached to the same verified state.
Handoff index
Questions this overview should answer
- Which terms belong to art direction and production planning, and which are only adjacent vocabulary?
- Which proof artifacts matter most: asset list, visual target, style note, scope boundary, and review cadence?
- Which terms should be reviewed together because they share one owner?
- Which leaf guide should be used when the page reader has a concrete asset, render, scene, or engine task?
- Which translated labels need extra context before an outsourcing team can act on them?
Workspace prompt
Turn the cluster into a review plan
Ask SEELE AI to convert Art Direction and Asset Brief Production Guide into a routing plan. The plan should group Asset List, Art Specification, Style Guide, Visual Target, Mood Board, and Concept Art, name the owner for each group, point to the right leaf guide, and state the evidence required before any term becomes an approved production label.
Terminology reference
Chinese, English, and Japanese terms used by this article
This table is kept as a reference for SEO coverage, outsourcing review, and localization alignment. Treat the article sections above as the decision guide; treat this table as the vocabulary index.
| Chinese | English | Japanese | Workflow context |
|---|---|---|---|
| 资产清单 | Asset List | アセットリスト | 项目管理 |
| 美术规范 | Art Specification | アート仕様 | 项目规范 |
| 风格指南 | Style Guide | スタイルガイド | 美术管理 |
| 视觉目标 | Visual Target | ビジュアルターゲット | 美术管理 |
| 情绪板 | Mood Board | ムードボード | 概念设计 |
| 概念图 | Concept Art | コンセプトアート | 前期 |
| 轮廓可读性 | Silhouette Readability | シルエットの可読性 | 美术检查 |
| 套件拼装 | Kitbash | キットバッシュ | 环境/概念 |
| 返修 | Revision / Rework | 修正戻し | 外包 |
| 每日构建 | Daily Build | デイリービルド | 开发 |
| 冻结范围 | Scope Freeze | スコープ凍結 | 项目管理 |
| 命名后缀 | Naming Suffix | 命名サフィックス | 管线 |
Related detailed guides
Related pages and next step
Open SEELE AI workspaceArt Direction and Asset Brief Production Guide FAQ
How should this hub be used?
Use it to choose the right detailed guide. The hub maps Asset List, Art Specification, Style Guide, and Visual Target to owners, evidence, and leaf pages instead of acting as the final approval note for every term.
What makes the coverage article-like instead of card-like?
The page explains cause, risk, evidence, and approval language before the reference table. The table supports the article; it does not replace the article.
When does Asset List need escalation?
Escalate when asset list, visual target, and style note are missing, when asset brief, visual target, style guide, revision policy, or delivery list differs from the source preview, or when another department owns the final verification.
Why keep 资产清单 and アセットリスト beside Asset List?
For Art Direction and Asset Brief Production Guide, the translated labels are useful only when they point to the same verified production context in art direction and production planning. Keep the local terms beside the proof, not in a detached word list.
How should Asset List, Art Specification, Style Guide, and Visual Target appear in an outsourcing ticket?
Put the English term in the task title, add the Chinese and Japanese wording in the acceptance note, and attach the evidence that proves the requested production context in art direction and production planning.