Demo Asset Layout
Demo content is organized by owning object, not by asset kind: card art stays with the card, and an enemy prefab stays with the enemy
Root folders
📦 Demo/Content/ # All shipped presentation assets, grouped by owner
├── 🎨 Art/ # Cross-object shared assets only
├── 🃏 Cards/ # Card-family frames, prefabs, and per-card artwork
├── 🗂️ Decks/ # Starting/reward deck cover icons for each class
├── 🌄 Encounters/ # Class backgrounds, parallax layers, and encounter UI
├── 🎯 Intents/ # Enemy-intent icons and the widgets that display them
├── ✨ Statuses/ # Status icons, status widgets, and status-owned VFX
└── 🧙 Units/ # Player/enemy artwork, prefabs, and shared unit widgets
Cards
🃏 Content/Cards/ # Five card families plus their one shared glow sprite
├── ⚔️ Basic/ # Basic-family frame, prefab, and card artwork
│ ├── 🖼️ Artwork/ # Art for Basic cards such as Strike and Defend
│ ├── 🎨 Basic.png # Basic card-frame sprite
│ └── 🧩 Basic.prefab # Basic card-view prefab
├── 💥 Burst/ # Burst-family frame, prefab, and artwork
├── 🕯️ Curse/ # Curse-family frame, prefab, and artwork
├── 🛠️ Skill/ # Skill-family frame, prefab, and artwork
├── 🤝 Support/ # Support-family frame, prefab, and artwork
└── ✨ CardGlow.png # Glow sprite shared by every card family
The five folders are the card template families; each one owns its frame sprite, its card prefab, and an Artwork/ folder holding the art of every card rendered with that frame. CardGlow.png sits at the Cards/ root because every card shares it
If a single card later gets bespoke VFX, audio, or animation, those assets go under the card family that uses them, in a VFX/, Audio/, or Animation/ subfolder; A kind-based bucket such as Content/VFX/Cards/ would separate the assets from their owner and should be avoided
Units
🧙 Content/Units/ # Unit-owned art/prefabs plus unit-wide shared assets
├── 👹 Enemy/ # Enemy folders grouped first by class, then by unit
│ ├── 🏹 Enemy_Hunter/ # Hunter enemy roster
│ │ ├── 🐍 Enemy_PlagueStalker_Normal/ # Normal enemy artwork and prefab
│ │ ├── 🍄 Enemy_SporeBrute_Elite/ # Elite enemy artwork and prefab
│ │ ├── 💀 Enemy_MireReaper_Boss/ # Boss artwork and prefab
│ │ └── 🌱 Enemy_BogPolyp_Summon/ # Summoned-unit artwork and prefab
│ ├── 🪄 Enemy_Mage/ # Mage enemies, each in its own tier-suffixed folder
│ ├── ✨ Enemy_Priest/ # Priest enemies, each in its own tier-suffixed folder
│ └── ⚔️ Enemy_Warrior/ # Warrior enemies, each in its own tier-suffixed folder
├── 🦸 Player/ # Player-unit assets grouped by class
│ ├── 🏹 Hunter/ # Avatar, full-body art, and player prefab
│ ├── 🪄 Mage/ # Avatar, full-body art, and player prefab
│ ├── ✨ Priest/ # Avatar, full-body art, and player prefab
│ ├── ⚔️ Warrior/ # Avatar, full-body art, and player prefab
│ └── 🌟 Shine.png # Highlight sprite shared by player units
├── 🧩 Prefabs/ # Unit-wide widgets such as HpWidget.prefab
└── 🌑 Shadow.png # Ground shadow shared by every unit
Each enemy gets its own folder named Enemy_<Name>_<Tier> inside its class folder, holding that enemy's art and prefab side by side; player classes each own one folder with the avatar, the full-body art, and the unit prefab; widgets shared by every unit, such as the HP bar, live in Units/Prefabs/
Encounters
🌄 Content/Encounters/ # Presentation assets owned by each encounter class
├── 🏹 Hunter/ # Hunter encounter presentation
│ ├── 🖼️ Background.png # Full-screen class background
│ ├── 🏞️ Layer/ # Foreground/background parallax layers
│ └── 🧭 UI/ # Hunter-specific encounter UI art
├── 🪄 Mage/ # Mage background, parallax layers, and UI art
├── ✨ Priest/ # Priest background, parallax layers, and UI art
└── ⚔️ Warrior/ # Warrior background, parallax layers, and UI art
Encounter backgrounds and their parallax layers belong to the class folder; the scene files themselves are not content; they live under Demo/Scenes/<Class>/
Statuses and intents
✨ Content/Statuses/ # Status-owned icons, widgets, and presentation effects
├── 🧩 Prefabs/ # StatusWidget.prefab and StatusIconEntry.prefab
├── 💫 VFX/ # 25 status apply/expire effect prefabs
└── 🖼️ Status_<Name>.png # 30 status icons selected in Workbench
🎯 Content/Intents/ # Assets used to telegraph enemy actions
├── 🧩 Prefabs/ # IntentWidget.prefab and IntentEntry.prefab
└── 🖼️ Intent_<Kind>.png # Eight icons: Attack through Unknown
Each status definition points at its icon through the Icon field you set in Workbench Status mode; the statuses with a signature visual keep those effect prefabs in Statuses/VFX/, and their apply / expire presentation is configured directly on the status FlowGraph with Status Apply FX and Status Expire FX nodes; the intent icons match the intent kinds enemies telegraph above their heads, and the two Prefabs/ folders hold the widgets the demo battle UI uses to display both
Shared art only
Content/Art/ is reserved for assets used by multiple owning objects:
🎨 Content/Art/ # Shared presentation infrastructure used across owners
├── 🔊 Audio/ # Mixer, BGM, ambience, gameplay SFX, UI, stingers, and voices
├── 🔤 Fonts/ # Runtime fonts and TextMesh Pro font assets
├── 🧪 Materials/ # Shared UI, environment, and VFX materials
├── 🧩 Prefabs/ # Cross-object widgets and reusable presentation prefabs
├── 📦 Resources/ # TinyGiants assets loaded through Unity Resources
├── 🧬 Shaders/ # Shared UI, sprite, environment, and particle shaders
├── 🖼️ Sprites/ # Shared cursor, UI, and VFX textures
└── 💥 VFX/ # Shared combat and class-ambience effect prefabs
The audio tree is the clearest example of a legitimate shared asset: one mixer and category folders (BGM, ambience, card sounds, combat hits, intent telegraphs, status clips, stingers, UI, enemy voices) that every scene routes through; A single card's signature sound would not belong here; it would go under that card's family folder
Place an object's private assets directly under that owner and reserve Art/ for content used by more than one owner; deciding the owner first avoids touching unrelated references when assets move later
Placement rules for audio, VFX, and animation
When a production pass adds final presentation assets, the ownership rule decides the destination:
| The asset belongs to | Put it under |
|---|---|
| One card family | Content/Cards/<Family>/VFX/ (or Audio/, Animation/) |
| One enemy | its Content/Units/Enemy/Enemy_<Class>/Enemy_<Name>_<Tier>/ folder |
| One player class | Content/Units/Player/<Class>/VFX/ (or Audio/, Animation/) |
| One encounter class | Content/Encounters/<Class>/VFX/ (or Audio/, Animation/) |
| Many unrelated objects | Content/Art/VFX/ (or Audio/, Animations/) |
The per-object subfolders are created on demand, the first time such an asset exists; an empty Audio/ folder under every card family would be noise
Applying the rule to your project
The layout is mandatory for demo content and recommended for yours; to mirror it:
- Decide which object owns the asset before importing it
- Put the asset in that object's folder, creating the subfolder if needed
- Use a shared folder only when more than one object owns or uses the asset
- Keep databases separate from presentation assets
- Keep demo content and production content in separate roots, so a demo cleanup never touches your game