Naming Conventions

An asset named "final_v2_revised_FINAL.png" is a failure of process. Naming conventions are not bureaucracy — they are the interface between the generation pipeline and every downstream system that consumes the asset.

The naming schema: {type}-{subject}-{variant}-{dimensions}-{version}.{ext}. Type: hero, card, thumb, og, banner, icon. Subject: slugified topic identifier. Variant: a/b/c for A/B test variants, or "solo" for single outputs. Dimensions: WxH in pixels. Version: semantic version matching the style specification version.

Examples: hero-agent-teams-a-1920x1080-v2.0.png. card-quality-loops-solo-1200x630-v2.0.png. thumb-style-transfer-b-400x400-v2.0.png. Every filename encodes what the asset is, what content it depicts, which variant it is, its dimensions, and which style version produced it. The downstream consumer does not need to open the file to know what it contains.