Asset Library Organization Planner

asset-library-organization-planner

Purpose

Set up a maintainable internal asset library so future recipes can:

• find existing assets quickly,
• avoid re-licensing the same source,
• reuse PBR materials and HDRIs,
• track versions and revisions.

Quick start

• pin folder structure (kebab-case, by category)
• pin naming convention (asset name + version + license slug)
• pin metadata schema (license, source, date, version, hash)
• pin version control rules (LFS for large binaries, plain text for metadata)
• emit a library-init plan

When to use

• starting a new BlendOps repo with multiple recipes
• existing library is disorganized; recipes can't find assets
• before scaling to 50+ assets

When not to use

• single-recipe repo with

Limitations:

## Required laws
- `../../laws/evidence-before-done.md`
- `../../laws/non-blender-user-language.md`
- `../../laws/no-arbitrary-python-interface.md`
- `../../laws/official-runtime-only.md`

## Official runtime boundary

Planning skill — does not move files, does not run Blender, does not configure version control. Outputs a structure spec.

## Operating procedure
1. Read asset categories.
2. Pin folder structure (see `references/folder-structure-rules.md`).
3. Pin naming convention (see `references/naming-rules.md`).
4. Pin metadata schema (see `references/metadata-schema.md`).
5. Pin version control rules (LFS thresholds, branching).
6. Pin license tracking (one license file per asset folder).
7. Recommend a review process for new asset additions.
8. Emit library-init plan + migration steps.

## Decision tree

```txt
 50MB?
  → Git LFS or external storage
> 1GB total?
  → External DAM strongly recommended

Playbooks

Playbook A: Small repo ( 4 levels gets confusing).

Good examples

• "assets/models/products/sneaker-v01-cc0.glb + assets/models/products/sneaker-v01-cc0.metadata.json + assets/models/products/sneaker-v01-cc0.LICENSE.txt"

Bad examples

• "Just use a Drive folder." — no version, no license tracking.

User-facing response template

Library size estimate: 
VCS: 

Folder structure:
  

Naming convention: 

Metadata schema (per asset):
  

Version control:
  

License tracking: 

Review process: 

Migration steps (if applicable): 
Limitations: 
Next: implement plan; future recipes use this library

Anti-patterns

• "Just a folder."
• No license file.
• Mutable "latest" pointers.
• Mixing assets and recipes in the same folders.

Cross-skill handoff

• Asset discovery → ../blender-asset-discovery-planner/SKILL.md
• License → ../asset-license-checker/SKILL.md
• Style → ../asset-style-consistency-checker/SKILL.md
• Fallback → ../asset-fallback-strategy/SKILL.md

Non-goals

• Move files.
• Configure git / DAM.
• Run Blender.
• Buy assets.

References

• references/folder-structure-rules.md
• references/naming-rules.md
• references/metadata-schema.md
• ../../docs/skill-system.md

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: ThanhNguyxnOrg
• Source: ThanhNguyxnOrg/blendops
• License: MIT
• Homepage: https://github.com/ThanhNguyxnOrg/blendops

Install and usage instructions live in the source repository linked above.