Asset Generation Workflow

Tooling reference

com.unity.ai.generators provides Unity Editor tools for generating and refining assets directly in the project. It supports text-to-asset and reference-driven workflows for images, sprites, PBR materials, meshes, sound effects, ambient audio, and humanoid animations.

Use this as an asset-production assistant, not as a replacement for design direction. The agent should help write prompts, organize outputs, compare candidates, and wire selected assets into prefabs.

Useful for this lab

Rack equipment placeholders

Generate rough meshes or visual concepts for switches, routers, servers, patch panels, cable organizers, and rack accessories before committing to final models.

Materials and labels

Create PBR materials for metal racks, plastic wall plates, cable jackets, rubber feet, workstation surfaces, and room finishes. Use generated textures as a starting point, then simplify for WebGL.

Training UI art

Generate icon concepts for link up, link down, power, warning, wall jack, patch panel, workstation, router, and server states.

Audio feedback

Create small sound effects for rack doors, cable insertion, cable removal, error feedback, terminal confirmation, and lesson completion.

Animation ideas

Explore simple humanoid or UI motion references, but keep the first version focused on camera transitions and interaction feedback instead of complex character animation.

Agent workflow

1. Define the asset job

Ask the agent for a specific asset brief: purpose, scale, location in the scene, style constraints, polygon/detail budget, WebGL constraints, and success criteria.

2. Generate variations

Use the generator tools to create multiple candidates. Keep the prompt tied to the lab: vocational training, realistic network closet, readable ports, labels, and clear student feedback.

3. Review like a training asset

Choose assets that teach clearly. A switch face with readable ports is better than a beautiful model that hides the interaction points.

4. Promote and organize

Move approved outputs into project folders, name them clearly, attach materials, create prefabs, and document where each asset is used.

5. Wire into simulation state

Once an asset is accepted, connect it to the data model: ports, endpoints, LEDs, cable sockets, colliders, labels, and interaction scripts.

Prompts to reuse

“Act as an art director for a Unity WebGL networking training lab. Write five prompt variations for a readable 24-port switch front panel.”
“Review this generated rack equipment asset for training clarity, WebGL cost, port readability, and prefab readiness.”
“Create a naming and folder plan for generated Unity assets: models, materials, icons, sounds, prefabs, and rejected candidates.”
“Help me turn this generated switch mesh into a prefab with clickable port endpoints, LED locations, colliders, and labels.”
“Write concise generation prompts for patch panels, punch down blocks, wall jacks, cable bundles, and server rack props.”

Asset brief template
Purpose: teach or support ______
Scene location: ______
Student interaction point: ______
Required readable details: ______
WebGL constraints: low/medium detail, optimized textures
Accept when: ______

Guardrails

Do not let generated assets decide the training design. Start with the lesson, then generate only what supports that lesson.

Favor clear silhouettes, readable ports, labels, and interaction hotspots over decorative realism.
Optimize generated textures and meshes before using them in WebGL.
Keep source prompts and selected outputs documented so assets can be regenerated or revised.
Avoid protected brand logos or exact copies of real networking hardware unless you have permission.
Use generated assets as drafts; final training-critical visuals should be reviewed manually.