Tutorials
Claude Opus 5.5: Name Ad Assets Without Losing the Right Version
Ask Claude Opus 5.5 to propose a filename mapping and delivery manifest before it touches a folder.
Ask Claude Opus 5.5 to propose a filename mapping and delivery manifest before it touches a folder. Keep the original files, review collisions, then copy approved assets into a new delivery directory. A naming scheme should tell a teammate which product, language, placement and revision a file belongs to without opening it.
This is a proposed handoff workflow with fictional filenames, not a timed model test. A designer's file-naming discussion describes how repeated “final” labels make versions hard to distinguish. More inventive labels do not solve that problem; a stable schema does.
Define the fields before the separator
Use a compact pattern such as `campaign_sku_locale_placement_revision.ext`. Store approval state in the manifest as well as the delivery folder. A filename ending in `v03` does not prove anybody approved revision three.
| Field | Example | Rule |
|---|---|---|
| Campaign | autumn26 | Fixed project identifier |
| SKU | 0042 | Text; preserve leading zeros |
| Locale | en-US | Match the approved copy locale |
| Placement | feed-4x5 | Controlled label, not an inferred platform rule |
| Revision | v03 | Increment for a changed deliverable |
The fictional file `autumn26_0042_en-US_feed-4x5_v03.png` names an output precisely. It does not prove that the pixels are 4:5 or that the text is English. Verify those properties from the actual image and approved copy. Keep dimensions in the manifest if adding them to filenames makes the names cumbersome.
Make an explicit mapping
Start with a read-only inventory: relative path, file type, pixel dimensions and the known product identifier. Include the full relative path because two different folders can contain `export.png`. Ask Claude to flag unknown locale or SKU instead of guessing from appearance.
A mapping row should contain source path, proposed destination, reason, approval status and a checksum if you compute one. Two different sources mapping to the same destination are a blocking collision, even if their extensions differ only by case. Resolve case-insensitive collisions before moving between operating systems.
Apple's Finder documentation covers basic batch replacement, added text and numbered formats. Use those ordinary tools for simple jobs. An AI-generated script is useful only when the mapping logic is more involved and can be inspected.
Copy this planning prompt
Build a delivery naming plan from the supplied inventory. Do not rename, delete, overwrite or upload files.
Pattern: campaign_sku_locale_placement_revision.ext.
Campaign is autumn26. Preserve SKU strings exactly, including leading zeros. Preserve real file extensions. Use only the provided locale and placement mapping; mark unknown fields unresolved.
Return CSV columns: source_relative_path, destination_relative_path, reason, approval_status, unresolved_fields.
Check duplicate destinations after case folding, missing sources, names that escape the delivery directory, and unsupported filename characters. Report conflicts before the proposed mapping.
Use a new delivery directory and copy approved files only after the mapping is reviewed. Keep originals unchanged. Provide a verification plan comparing source/destination counts, bytes or hashes, dimensions and approved revision identifiers.
Do not mark a file approved because its old name contains “final.”Work through a collision
Suppose `round2/export.png` and `approved/export.png` both map to the same v03 destination. Do not automatically append `_2`: that conceals which version is intended. Compare the approval record, inspect the images, and select the approved source. If both serve different placements, fix the placement field rather than adding a meaningless suffix.
For three products, two languages and two placements, a complete fictional delivery has 3 × 2 × 2 = 12 assets. A folder containing twelve files can still be incomplete if one combination appears twice and another is absent. Validate the expected combination matrix, not just the total count.
After copying, verify that every manifest destination exists, each approved source has exactly one intended destination, and file bytes are unchanged when no conversion was requested. If resizing is part of delivery, record it as a separate transformation with its own dimensions and output checksum. Renaming a `.jpg` extension to `.png` does not convert an image.
Keep the production handoff readable
Export finished visuals from Panelly Studio and bind them to the manifest after review. The workflow does not assume Panelly runs Opus or automatically follows this naming pattern. The manifest travels with the assets so a recipient can trace a file to its product and approved copy.
Use contact-sheet selection to choose the right source images first. Use product-variant review when a filename is correct but the pictured product is not.
Common questions
Can every file share one sequential counter?
Yes for a simple proof set, but the counter alone loses product and placement meaning. Keep a manifest connecting it to those fields.
Should the script overwrite an existing delivery folder?
Use a new versioned folder and compare it with the prior manifest. Overwriting makes it harder to discover an accidental downgrade or missing asset.
