Sprite/Icon Organization

[Bitstachio]

Summary

Sprite assets, particularly icons, are currently scattered across inconsistent locations throughout the project with no clear organizing convention. This makes it hard to locate, reuse, and maintain visual assets.

Current State

• Some sprites live under Assets/Sprites.
• Some sprites live inside individual feature directories.
• On the Guide page specifically, icons for different items come from entirely different sources:
  • Shield icon is a custom-made image.
  • Some icons come from a general icons directory.
  • Blaster and laser icons come from a third-party asset directory.
• No consistent convention currently governs where a sprite/icon should live based on its origin (custom vs. third-party) or usage (shared vs. feature-specific).

To Investigate

• Establish a clear convention for sprite/icon placement, e.g.:
  • Shared/reusable icons (used across multiple features or UI screens) vs. feature-specific sprites (only relevant to one feature).
  • Custom-made assets vs. third-party assets — should third-party assets stay isolated (e.g., consistent with the existing Assets/ThirdParty/Vendor.PackageName convention) rather than mixed into general icon directories.
• Audit all current sprite/icon usages project-wide (starting with the Guide page as a known example) and catalog where each currently lives and where it should live under the new convention.
• Decide whether icons need further sub-categorization (e.g., by feature, by UI vs. gameplay, by weapon type) or a flat shared directory is sufficient.
• Migrate existing sprites to match the new convention and update all prefab/scene references accordingly.

Goal

Establish and document a consistent, predictable convention for where sprites/icons live in the project, then migrate existing assets (starting with Guide page icons) to follow it.