Use when turning an exported material package such as a Unity `manifest.json` plus optional `shadergraph.json` into a `material-reconstruction-plan/0.1`. Use for package inspection, reconstruction-mode selection, plan JSON structure, approximations, unresolved branches, and readable graph layout. Do not use this skill for direct Unreal execution; pair it with `ue-harness` when applying the plan.
Use this skill to plan a reconstruction.
This skill plans only. It does not replace Unreal execution tools.
When execution is about to begin, also read ../ue-harness/SKILL.md.
Read these in order:
../../docs/material-package.md../../docs/material-reconstruction-plan.mdmanifest.json, if presentshadergraph.json, if present../../docs/examples/, if presentsuccess: true from one MCP call as proof of correctnessExtract at least these facts:
For Unity Shader Graph packages, also check:
shadergraph.json existsCustomFunctionNode existsshader_sources/If a custom function exists but its source evidence is missing, stop and fix export first.
If a branch depends on runtime state such as world-space arrays, scene-driven masks, or global shader values, stop and export that runtime state before planning that branch as reconstructable.
Prefer one of these:
semantic_surfacegraph_guided_semantic_surfacemanual_custom_graphpartial_reconstructionDecision rule:
semantic_surfacegraph_guided_semantic_surfaceDo not default to exact graph replay when the source exposes opaque slot ids, missing subgraph bodies, or source-specific node types.
Always emit these sections:
strategyresourceBindingsexecutionapproximationsunresolvedverificationGoalsAlso emit these when execution is expected in the same task:
executionOrderstopConditionsvalidationGateverificationArtifactsKeep the boundary clear:
strategy, approximations, and unresolved explain planning decisionsresourceBindings, execution, and verificationGoals are execution-facingWhen the source graph already has meaningful subgraph boundaries, preserve those boundaries in the plan.
Planning rules:
The detailed execution rules for function reuse, custom-node constraints, and stop conditions live in ../ue-harness/SKILL.md.
When generating execution.graph.recipe.nodes, choose readable coordinates.
Default layout:
Recommended lanes:
BaseColorOpacity or OpacityMaskNormalMetallicRoughnessAmbientOcclusionEmissiveRecommended placement rules:
When execution begins, follow the material execution order, stop conditions, and validation rules in ../ue-harness/SKILL.md.
This planner should not duplicate those execution instructions.
Be explicit when simplifying source behavior.
Common approximations:
Common unresolved items:
Output one converged material-reconstruction-plan/0.1 JSON object.
Prefer:
executionstrategy.reasonverificationGoals for properties, output connections, and resource bindingsRecommended verificationArtifacts:
Do not hardcode task-specific package knowledge into this skill.
Do not claim reconstruction alignment until all of the following are true:
../ue-harness/SKILL.md