Skip to content

Repositories

Purpose

Owns prefab repository and prefab collection workflows for Snap Studio Pro.

This territory is responsible for scanning, storing, organizing, and exposing prefab collections while coordinating thumbnail generation and repository-facing asset workflows.

Owns

  • Prefab collection management
  • Asset scanning workflows
  • Prefab repository state
  • Thumbnail coordination
  • Prefab list exposure
  • Repository refresh workflows

Does NOT Own

  • Preview scene lifecycle
  • Export workflows
  • Rendering implementation
  • Panel UI layout
  • Capture execution

Allowed Dependencies

Repositories may depend on:

  • Thumbnail generation systems
  • Unity asset database APIs
  • Prefab abstractions/contracts
  • Diagnostics
  • Shared utilities

Repositories should avoid depending on:

  • preview orchestration systems
  • export orchestration systems
  • rendering implementation systems

Notes

Repositories are responsible for: - what prefabs exist - how prefabs are organized - when repository data refreshes - thumbnail coordination

Repositories should not own: - preview behaviour - export workflows - rendering implementation

This separation keeps prefab-domain data management isolated from production workflows.

Future Candidates

  • Continue separating repository ownership from operational workflow services.
  • Avoid allowing preview/export lifecycle logic into repositories.
  • Maintain lightweight repository-facing asset coordination.