Figma File Structure and Page Organisation Guide
Create a convention for pages, frames and naming.
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.
Plan the organisation of a Figma file or project. Type of work: [WORK_TYPE]. Team: [TEAM]. Problems now: [PROBLEMS]. Give the page list with a one-line purpose for each (Cover, Working, Ready for dev, Archive, Components), frame naming at three levels with an example (feature/screen/state), and a status system with simple tags such as Draft, In review and Ready. Write the cover page content with fields: project name, owner, status, links and last updated. Explain section use and version practices in plain words, marking features that depend on my plan [VERIFY]. Archiving: move old explorations to an Archive page with a date, never deleting them in the middle of a project. Add a ten-minute weekly tidy, a pre-handoff cleanup checklist, a quarterly archive routine, and a one-page guide for new team members. Keep it simple enough to follow under time pressure. Keep the structure small enough that a new designer can learn it in ten minutes. Say which rule matters most if people only follow one, and where to record exceptions.
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.