arjun988/blender-skills / .claude/skills/lod-pipeline
lod-pipeline
VerifiedDedicated LOD generation, naming, screen-size targets, and validation for game meshes in Blender via MCP.
LOD Pipeline
Intentional LOD chains. Preserve silhouette. Validate reductions.
When to Use
- Game assets needing LOD0–N
- Batch LOD for modular kits
- Before Unity/Unreal/Godot export
Workflow
Approve LOD0 → Generate LOD1..N → Fix silhouette breaks
→ Naming → Screen-size table → Export verify
Typical Budgets (guide)
| LOD | Tris vs LOD0 | Keep |
|---|---|---|
| LOD0 | 100% | Full detail |
| LOD1 | 40–60% | Major forms |
| LOD2 | 15–30% | Silhouette |
| LOD3 | 5–10% | Blob / impostor candidate |
Tune per asset importance and camera.
Generation Methods
- Decimate (planar/collapse) — fast props
- Manual retopo low — hero characters/vehicles
- Delete interiors / small parts — vehicles, buildings
- Bake normals from LOD0 → low — when detail must move to texture
Naming
SM_Asset_LOD0
SM_Asset_LOD1
SM_Asset_LOD2
Collection: COL_LODs_[Asset]
Validation Checklist
- Silhouette matches at intended distance
- No major holes / inverted normals
- UVs still valid (or rebaked)
- Materials slots consistent across LODs
- Vertex colors/UVs needed by shader preserved
- LOD transitions planned (screen size %)
Screen Size Starters
| LOD | Screen size (UE-like guide) |
|---|---|
| LOD0 | 1.0 – 0.5 |
| LOD1 | 0.5 – 0.25 |
| LOD2 | 0.25 – 0.1 |
| LOD3 | 0.1 – 0.0 |
Constraints
MUST DO
- Protect silhouette before poly reduction
- Keep LOD0 as source of truth
- Document budgets in production brief
MUST NOT DO
- Blind decimate until unrecognizable
- Different material slot counts across LODs without reason
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Lod Budgets | references/lod-budgets.md | When needed |
| Lod Validation | references/lod-validation.md | When needed |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |