MC Blockbench Art Direction and Review
Purpose
Define refinement as the clarity and richness of effective information, not the number of pixels, color steps, voxels, decorative parts, or keyframes. Judge detail by six kinds of information: recognition, structure, material, space, action state, and theme.
Use this skill to plan, improve, and review the art of blocks, items, entities, equipment, characters, and their animations. Software procedures and technical implementation are outside its scope. It provides cross-tool art judgment and acceptance criteria, and can be distributed on its own or used alongside other workflows.
Establish the Task Context
Before giving advice, establish:
- Asset type: item, block, entity, equipment, character, scene part, or animation.
- Function and character: purpose, rarity, weight, material, mood, and theme keywords.
- Viewing conditions: actual display size, expected distance, angle, background, and whether the asset is static or moving.
- Core recognition features: retain a small set of essential traits instead of preloading decoration.
- Style target: vanilla Minecraft fit, series matching, or another explicit style.
- Existing specification: read project conventions. Do not impose one resolution or borrow another project's signature palette.
When information is missing and would materially change the advice, ask the most important question first. Otherwise, state the assumption and continue with reusable guidance.
Build a Three-Tier Visual Hierarchy
- Silhouette and major color masses: remain identifiable when reduced, viewed from a distance, or seen in motion.
- Structure and material: communicate volume, part relationships, lighting, and surface differences.
- Focus and ornament: reward close inspection without damaging the first two tiers.
Preserve quiet areas and a contrast budget. The strongest value, color, texture, and motion contrast should support one visual strategy instead of making every area a focal point.
See Visual Foundations and Effective Detail.
Validate the Minimum Readable Solution
Confirm in order:
- The subject remains recognizable after tier-three detail is removed.
- Major color masses and shading already describe basic volume.
- The model's overall shape works instead of relying on texture to rescue a weak silhouette.
- Animation key poses already communicate the action instead of relying on easing to hide weak posing.
If the minimum solution fails, fix silhouette, proportion, major masses, or key poses before adding micro-detail.
Allocate a Detail Budget by Information Value
For every added pixel cluster, color step, voxel layer, decorative part, or key-pose change, ask:
- What new information does it add?
- Can it be perceived under the actual viewing conditions?
- Is it a better focal point than what already exists?
- Does it fit the pixel density, lighting, theme, and motion language?
- Does it remain effective when tiled, viewed from another angle, or played in a loop?
Prefer the clearest expression with the least interference:
- If a major color mass communicates it, do not add broken pixels.
- If texture communicates it, do not add unnecessary voxels.
- If silhouette and key posing communicate it, do not add redundant keyframes.
- If one clear material cue communicates it, do not stack competing patterns.
Give both addition and removal advice. When goals conflict, follow this order: game state and recognition > silhouette and key poses > structure and material > thematic focus > pure ornament.
Read the Relevant Reference
| Task | Reference |
|---|---|
| Palette, pixel density, shading, material, texture detail, item/block/entity differences | Texturing |
| Silhouette, proportion, voxel layering, surface ornament, geometry-texture split, form in motion | Modeling |
| Timing, key poses, easing, loops, secondary motion, game feedback | Animation |
| Minecraft fit, in-game readability, thematic consistency, detail overload, cross-asset disputes | Visual foundations |
| Existing specifications, mixed-resolution assets, limits of 16x16, rule precedence | Project conventions |
| Final review, issue severity, revision and removal decisions | Review checklists |
Load only the references relevant to the current task. Do not repeat every topic in one response.
Organize Art Direction Feedback
Classify advice as:
- Must fix: recognition or state failure, severe style conflict, inconsistent density, or a broken loop.
- Worth strengthening: vague material, weak volume, insufficient weight, or an unclear thematic focus.
- Optional ornament: the base goal is already met and the change only improves close-up appeal.
- Recommended for removal: no information, imperceptible, repetitive, or disruptive to higher-priority content.
Explain the information purpose and expected viewing conditions of each important recommendation. Prefer testable principles such as "merge nearby color clusters that do not communicate a material difference" over vague demands to "add detail" or "make it more polished."
Review in a Fixed Order
- Are recognition and game state clear?
- Are the Minecraft style and project theme coherent?
- Are material, space, and motion credible?
- Does detail create focus rather than noise?
- Do the assets hold up alone and in combination, when tiled, from multiple angles, and in motion?
Use the review checklists for final acceptance. Do not call an asset refined merely because it has many details if recognition, material, structure, or motion has not improved.