A beautiful Figma file isn’t always a buildable one. When a design leaves out the mobile layout, hover states or what happens with a longer headline, the developer has to guess. Guesses are where websites start to drift from the design. Here is how we prepare files so nothing is left to guesswork, whether we are building the site or handing it to your team.
1. Styles before screens
Before any page is designed, we set up:
- Colour styles, named by role (background, text, accent) rather than by colour
- Text styles for every heading level, body size and label
- Spacing and grid, so layouts follow a consistent rhythm
- Variables for values that change between light and dark themes, if needed
These map directly to the CSS a developer will write, so the build matches the file.
2. Components, not copies
Buttons, cards, navigation, form fields and section layouts are built once as components with variants. Every page uses those components, so a change to the button updates every button. Developers see exactly which pieces repeat and can build them once too.
3. Every breakpoint
We design key pages at desktop, tablet and phone widths. Auto layout in Figma shows how elements stack and wrap, not just where they sit at one screen size.
4. Every state
A page is more than its default view. We include:
- Hover, focus and pressed states for buttons and links
- Open and closed menus
- Form errors and success messages
- Empty states, like a blog category with no posts yet
- Loading states where content takes a moment to appear
5. Real content
Placeholder text hides problems. We design with real headlines, real product names and real photos wherever we can, and test what happens with the longest and shortest versions.
The best handoff is a file a developer can build from without sending a single question.
6. Notes where they matter
We annotate interactions, animations, link destinations and anything that behaves differently from how it looks. Short and specific, right next to the element.
7. Accessibility checked in the design
Colour contrast, text sizes, tap target sizes and focus states are checked in Figma, before they become expensive to fix in code.
What you receive
- An organised Figma file with pages for styles, components and screens
- A short guide to the design system
- Exported assets: icons, logos and images
- A walkthrough call with your developers, if someone else is building