Create new design file

I need a new design file for the mobile product we’ll show investors on Thursday. Create a fresh file named Mobile Investor Demo — include an assets page, a components page, and a notes page. Populate the assets page with the brand colors I pasted (DeepBlue #0A3F66, Coral #FF6B5B, Slate #F4F6F8), and add the logo I uploaded. On the components page create a button component with primary, secondary, and disabled states, and a text style set for H1, H2, body and caption. Leave an editable notes page for version and author information.

Before I start extending this file for the team, make the new file easy to pick up: copy the brand colors to an assets swatch, create a component for primary CTA with the filled and outline states, add a reusable text style named ‘Investor H1’ set to 28/34, and add a short usage note at the top telling engineers which font weights to load. Flag any missing assets or inconsistent color values that would slow handoff.

I duplicated last quarter’s app file into Mobile Investor Demo and kept the old messy layers. I’m worried I copied deprecated components and wrong color tokens and the engineers will grab the wrong assets. I can’t tell which components are live or which text styles map to tokens. What’s the most likely places the team will trip, and what quick sweep should I do now to make the file safe to hand off for Friday’s build?

Every time I spin up a demo or feature file I copy from an existing file and end up with duplicate components, inconsistent tokens, and version confusion. It costs me hours later cleaning and costs engineers time. What three habits should I change when creating a new file so future handoffs are clean and predictable? Give concrete steps I can follow the next four times I make a file.