Shared Asset Library and File Naming Audit for a Design Team
Check how design files and assets are named, stored and versioned.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit a design team's file organisation. A description of folder structure, file naming examples, how versions are saved, where fonts and brand assets live, and how files are shared: [FILE_ORGANISATION]. Problems we have had (wrong versions sent, missing links, duplicate logos): [PROBLEMS]. Evaluate naming consistency, version control, duplicated assets, missing source files, linked files that break, font licensing documentation, access permissions, and archive rules. Make a table with Area, Finding, Effect, and Fix. Count how many example file names follow a pattern with the arithmetic. Propose a naming convention (client_project_asset_version_date), a folder tree, a hand-off checklist (packaged files, fonts, exports), and a 30-day clean-up plan with owners. Draft a short team guide. Mark licensing and storage features [VERIFY] with the team's admin. Do not recommend unlicensed fonts or software. Add a worked naming example: 'AcmeSpring_FlyerA5_v03_2025-03-14.indd' decoded field by field, versus 'final_final2.indd', and a count of 40 sampled files where 14 follow the pattern (35 percent). Include a one-page hand-off checklist listing packaged links, fonts used and exports.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.