lighting-material-plan
Purpose
Create a high-quality, practical lighting/material plan that balances visual intent and web portability constraints.
Quick start
- confirm this skill fits your goal
- provide required inputs first
- keep runtime claims evidence-bound
- follow suggested next-skill handoff
When to use
- look-development strategy is needed
- lighting/material choices drive scene mood
- web/GLB portability caveats must be explicit
When not to use
- to claim final rendered quality or executed results → use
../camera-composition/SKILL.md (Delegates out-of-scope requests to camera-composition)
- to skip composition/camera context from camera-composition → use
../camera-composition/SKILL.md (Delegates out-of-scope requests to camera-composition)
- to validate existing lighting or materials → use
../lighting-quality-checker/SKILL.md (use lighting-quality-checker and material-quality-checker)
- to decide render engines (cycles-vs-eevee-decision), color management (color-management-decision), or file formats (output-format-decision) → use
../color-management-decision/SKILL.md (output-format-decision)
- to execute Blender or generate Python scripts → use
../color-management-decision/SKILL.md (Delegates out-of-scope requests to color-management-decision)
Trigger phrases
- "plan lighting and materials"
- "design cyberpunk lookdev"
- "define PBR and reflection strategy"
Prerequisites / readiness
- framing and camera plan received from
camera-composition when chaining upstream planners (or clear subject and destination context for standalone use)
- upstream constraints known from
cycles-vs-eevee-decision, color-management-decision, and output-format-decision when applicable
- target delivery context known
Input schema
Required inputs
- style intent
- subject material constraints
- output destination
Optional inputs
- brand color/style constraints
- performance budget hints
- preferred mood references
Assumptions to confirm
- realism vs stylized priority
- reflection intensity tolerance
- portability strictness for web handoff
Output schema
Primary output
- lighting rig strategy (key/fill/rim, mood accents, reflection behavior) + material lookdev strategy (hierarchy, PBR targets, naming)
Secondary output
- portability simplification recommendations
Evidence / caveat output
- unverified visual assumptions
- explicit truth states:
Runtime: Not Run, Artifacts: Not Produced (downgrade-only, never upgrade)
Required laws
- ../../laws/evidence-before-done.md
- ../../laws/non-blender-user-language.md
- ../../laws/official-runtime-only.md
- ../../laws/no-arbitrary-python-interface.md
Official runtime boundary
This is a planning-only skill: no Blender execution, no Python, and no artifact generation. Runtime status always remains Not Run and artifact status always remains Not Produced (truth states are downgrade-only, never upgrade). If referencing Eevee engine tokens from upstream cycles-vs-eevee-decision, use BLENDER_EEVEE on Blender 4.0–4.1 and 5.x, and BLENDER_EEVEE_NEXT only for 4.2–4.x — never present Eevee Next as the current name.
Operating procedure
- Define lighting objective (readability vs drama balance).
- Choose key/fill/rim strategy.
- Add neon/cyberpunk accent pattern where requested.
- Define reflective floor behavior and caveats.
- Choose material classes and hierarchy.
- Define PBR portability assumptions.
- Identify web simplification opportunities.
- Define texture/material naming expectations.
- Add GLB/web handoff caveats.
- Provide user-facing summary with uncertainty markers.
Decision tree
- If style is cyberpunk + product clarity required → neon accents + controlled reflections.
- If web performance priority high → simplify material stack and reflection complexity.
- If portability uncertain → keep assumptions explicit and request runtime validation.
Playbooks
- Playbook A: text-only lookdev planning (
Runtime: Not Run, Artifacts: Not Produced)
- Playbook B: runtime-ready lookdev planning with verification targets prepared for
lighting-quality-checker and material-quality-checker (Runtime: Not Run, Artifacts: Not Produced)
- Playbook C: blocked-runtime conservative lookdev planning with strict portability caveats (
Runtime: Not Run, Artifacts: Not Produced)
Mode handling
Text-only mode
- produce lighting rig and material lookdev plan only
- report
Runtime: Not Run and Artifacts: Not Produced
Runtime-ready mode
- produce lookdev plan and define checklist targets for downstream
lighting-quality-checker and material-quality-checker
- keep
Runtime: Not Run and Artifacts: Not Produced within this skill
Blocked runtime mode
- provide conservative lookdev plan and explicit portability caveats
- keep
Runtime: Not Run and Artifacts: Not Produced with no rendered output claims
Validation checklist
Pass / Warn / Fail rubric
| Category |
Pass |
Warn |
Fail |
| Lighting strategy |
Clear and goal-aligned |
Basic but usable |
Missing/contradictory |
| Material strategy |
Coherent and portable-aware |
Partial portability |
No portability consideration |
| Web caveats |
Explicit and actionable |
Present but vague |
Missing caveats |
| Evidence boundary |
No visual overclaims |
Minor ambiguity |
Claims rendered results without evidence |
Failure handling
- Missing style detail: request targeted clarification.
- Conflicting constraints: output option sets with trade-offs.
- Unknown runtime state: keep plan-only with explicit caveats.
Troubleshooting
- Overly harsh reflections: reduce floor reflectance assumptions.
- Muddy lighting plan: simplify key/fill ratio assumptions.
- Material complexity too high for web: propose simplification tiers.
Best practices
- prioritize readability before stylization extremes
- map each lookdev decision to user-facing outcome
- preserve portability caveats explicitly
Good examples
“Use key+soft fill for product readability, neon rim accents for mood, and limit reflective floor intensity to avoid detail washout in web contexts.”
Bad examples
“Make it look cool with neon materials.” (no constraints, no caveats)
User-facing response template
- Lighting plan summary
- Material plan summary
- Portability caveats
- Truth states:
Runtime: Not Run | Artifacts: Not Produced
- Next handoff step (
lighting-quality-checker, material-quality-checker, scene-readiness, glb-web-handoff)
Anti-patterns
- skipping required laws or runtime boundary statements
- claiming runtime/artifact success without evidence
- upgrading truth states above
Runtime: Not Run or Artifacts: Not Produced
- blurring roles by validating lighting/materials instead of handing off to
lighting-quality-checker and material-quality-checker
- making render engine, color config, or file format decisions owned by
cycles-vs-eevee-decision, color-management-decision, or output-format-decision
- presenting
BLENDER_EEVEE_NEXT / Eevee Next as the current Blender 5.x engine name
- including Python snippets, Blender execution commands, or unhedged jargon
Cross-skill handoff
- [upstream_reference] Upstream input from (camera-composition) →
../camera-composition/SKILL.md
- [progression] Upstream input from (color-management-decision) →
../color-management-decision/SKILL.md
- [progression] Upstream input from (cycles-vs-eevee-decision) →
../cycles-vs-eevee-decision/SKILL.md
- [progression] Upstream input from (output-format-decision) →
../output-format-decision/SKILL.md
- [progression] Next validation (lighting-quality-checker) →
../lighting-quality-checker/SKILL.md
- [progression] Next validation (material-quality-checker) →
../material-quality-checker/SKILL.md
- [progression] Then scene check →
../scene-readiness/SKILL.md
- [progression] Then delivery →
../glb-web-handoff/SKILL.md
Non-goals
- shader/runtime implementation code
- rendered quality claims without evidence
References
1---2name: lighting-material-plan3description: Design studio lighting rigs (key/fill/rim ratios, Kelvin pairs) and Principled BSDF materials with AgX/PBR Neutral and glTF portability caveats.4metadata:5 source: https://skillmd.com/skills/thanhnguyxnorg/lighting-material-plan6---78# lighting-material-plan910## Purpose11Create a high-quality, practical lighting/material plan that balances visual intent and web portability constraints.1213## Quick start14- confirm this skill fits your goal15- provide required inputs first16- keep runtime claims evidence-bound17- follow suggested next-skill handoff1819## When to use20- look-development strategy is needed21- lighting/material choices drive scene mood22- web/GLB portability caveats must be explicit2324## When not to use25<!-- blendops:generated:start exclusions -->26- to claim final rendered quality or executed results → use `../camera-composition/SKILL.md` (Delegates out-of-scope requests to camera-composition)27- to skip composition/camera context from camera-composition → use `../camera-composition/SKILL.md` (Delegates out-of-scope requests to camera-composition)28- to validate existing lighting or materials → use `../lighting-quality-checker/SKILL.md` (use lighting-quality-checker and material-quality-checker)29- to decide render engines (cycles-vs-eevee-decision), color management (color-management-decision), or file formats (output-format-decision) → use `../color-management-decision/SKILL.md` (output-format-decision)30- to execute Blender or generate Python scripts → use `../color-management-decision/SKILL.md` (Delegates out-of-scope requests to color-management-decision)31<!-- blendops:generated:end exclusions -->3233## Trigger phrases34<!-- blendops:generated:start triggers -->35- "plan lighting and materials"36- "design cyberpunk lookdev"37- "define PBR and reflection strategy"38<!-- blendops:generated:end triggers -->3940## Prerequisites / readiness41- framing and camera plan received from `camera-composition` when chaining upstream planners (or clear subject and destination context for standalone use)42- upstream constraints known from `cycles-vs-eevee-decision`, `color-management-decision`, and `output-format-decision` when applicable43- target delivery context known4445## Input schema4647### Required inputs48- style intent49- subject material constraints50- output destination5152### Optional inputs53- brand color/style constraints54- performance budget hints55- preferred mood references5657### Assumptions to confirm58- realism vs stylized priority59- reflection intensity tolerance60- portability strictness for web handoff6162## Output schema6364### Primary output65- lighting rig strategy (key/fill/rim, mood accents, reflection behavior) + material lookdev strategy (hierarchy, PBR targets, naming)6667### Secondary output68- portability simplification recommendations6970### Evidence / caveat output71- unverified visual assumptions72- explicit truth states: `Runtime: Not Run`, `Artifacts: Not Produced` (downgrade-only, never upgrade)7374## Required laws75- ../../laws/evidence-before-done.md76- ../../laws/non-blender-user-language.md77- ../../laws/official-runtime-only.md78- ../../laws/no-arbitrary-python-interface.md7980## Official runtime boundary81This is a planning-only skill: no Blender execution, no Python, and no artifact generation. Runtime status always remains `Not Run` and artifact status always remains `Not Produced` (truth states are downgrade-only, never upgrade). If referencing Eevee engine tokens from upstream `cycles-vs-eevee-decision`, use `BLENDER_EEVEE` on Blender 4.0–4.1 and 5.x, and `BLENDER_EEVEE_NEXT` only for 4.2–4.x — never present Eevee Next as the current name.8283## Operating procedure841. Define lighting objective (readability vs drama balance).852. Choose key/fill/rim strategy.863. Add neon/cyberpunk accent pattern where requested.874. Define reflective floor behavior and caveats.885. Choose material classes and hierarchy.896. Define PBR portability assumptions.907. Identify web simplification opportunities.918. Define texture/material naming expectations.929. Add GLB/web handoff caveats.9310. Provide user-facing summary with uncertainty markers.9495## Decision tree96- If style is cyberpunk + product clarity required → neon accents + controlled reflections.97- If web performance priority high → simplify material stack and reflection complexity.98- If portability uncertain → keep assumptions explicit and request runtime validation.99100## Playbooks101- Playbook A: text-only lookdev planning (`Runtime: Not Run`, `Artifacts: Not Produced`)102- Playbook B: runtime-ready lookdev planning with verification targets prepared for `lighting-quality-checker` and `material-quality-checker` (`Runtime: Not Run`, `Artifacts: Not Produced`)103- Playbook C: blocked-runtime conservative lookdev planning with strict portability caveats (`Runtime: Not Run`, `Artifacts: Not Produced`)104105## Mode handling106107### Text-only mode108- produce lighting rig and material lookdev plan only109- report `Runtime: Not Run` and `Artifacts: Not Produced`110111### Runtime-ready mode112- produce lookdev plan and define checklist targets for downstream `lighting-quality-checker` and `material-quality-checker`113- keep `Runtime: Not Run` and `Artifacts: Not Produced` within this skill114115### Blocked runtime mode116- provide conservative lookdev plan and explicit portability caveats117- keep `Runtime: Not Run` and `Artifacts: Not Produced` with no rendered output claims118119## Validation checklist120- [ ] key/fill/rim strategy documented121- [ ] style-specific lighting notes documented122- [ ] reflective floor caveats documented123- [ ] material hierarchy documented124- [ ] PBR portability assumptions documented125- [ ] web simplification recommendations provided126- [ ] naming expectations provided127- [ ] handoff caveats provided128- [ ] uncertainty markers explicit129- [ ] no evidence overclaims130131## Pass / Warn / Fail rubric132133| Category | Pass | Warn | Fail |134|---|---|---|---|135| Lighting strategy | Clear and goal-aligned | Basic but usable | Missing/contradictory |136| Material strategy | Coherent and portable-aware | Partial portability | No portability consideration |137| Web caveats | Explicit and actionable | Present but vague | Missing caveats |138| Evidence boundary | No visual overclaims | Minor ambiguity | Claims rendered results without evidence |139140## Failure handling141- Missing style detail: request targeted clarification.142- Conflicting constraints: output option sets with trade-offs.143- Unknown runtime state: keep plan-only with explicit caveats.144145## Troubleshooting146- Overly harsh reflections: reduce floor reflectance assumptions.147- Muddy lighting plan: simplify key/fill ratio assumptions.148- Material complexity too high for web: propose simplification tiers.149150## Best practices151- prioritize readability before stylization extremes152- map each lookdev decision to user-facing outcome153- preserve portability caveats explicitly154155## Good examples156“Use key+soft fill for product readability, neon rim accents for mood, and limit reflective floor intensity to avoid detail washout in web contexts.”157158## Bad examples159“Make it look cool with neon materials.” (no constraints, no caveats)160161## User-facing response template162- Lighting plan summary163- Material plan summary164- Portability caveats165- Truth states: `Runtime: Not Run` | `Artifacts: Not Produced`166- Next handoff step (`lighting-quality-checker`, `material-quality-checker`, `scene-readiness`, `glb-web-handoff`)167168## Anti-patterns169- skipping required laws or runtime boundary statements170- claiming runtime/artifact success without evidence171- upgrading truth states above `Runtime: Not Run` or `Artifacts: Not Produced`172- blurring roles by validating lighting/materials instead of handing off to `lighting-quality-checker` and `material-quality-checker`173- making render engine, color config, or file format decisions owned by `cycles-vs-eevee-decision`, `color-management-decision`, or `output-format-decision`174- presenting `BLENDER_EEVEE_NEXT` / Eevee Next as the current Blender 5.x engine name175- including Python snippets, Blender execution commands, or unhedged jargon176177## Cross-skill handoff178<!-- blendops:generated:start handoffs -->179- [upstream_reference] Upstream input from (camera-composition) → `../camera-composition/SKILL.md`180- [progression] Upstream input from (color-management-decision) → `../color-management-decision/SKILL.md`181- [progression] Upstream input from (cycles-vs-eevee-decision) → `../cycles-vs-eevee-decision/SKILL.md`182- [progression] Upstream input from (output-format-decision) → `../output-format-decision/SKILL.md`183- [progression] Next validation (lighting-quality-checker) → `../lighting-quality-checker/SKILL.md`184- [progression] Next validation (material-quality-checker) → `../material-quality-checker/SKILL.md`185- [progression] Then scene check → `../scene-readiness/SKILL.md`186- [progression] Then delivery → `../glb-web-handoff/SKILL.md`187<!-- blendops:generated:end handoffs -->188189## Non-goals190- shader/runtime implementation code191- rendered quality claims without evidence192193## References194- https://www.blender.org/lab/mcp-server/195- https://claude.com/resources/tutorials/using-the-blender-connector-in-claude196- https://docs.blender.org/manual/en/latest/advanced/command_line/index.html