Importing a frame
How FrameKit reads your layers, guesses their roles, and writes a draft you approve.
Every layer gets a role
FrameKit guesses each layer's role from how it's drawn: section, header, heading H1–H6, button, image, card, menu and more. Names help when they're there ("button", "logo", "Heading/H3"), and files drawn in a builder's own naming convention import exactly as named.
Each guess is marked likely or check this. Change a role and you can apply it to every instance of that component. Roles you accept are remembered, so the next frame drawn the same way is guessed right the first time.
Layout
Auto layout becomes the builder's own layout: direction, gaps, wrap, padding and alignment.
Without auto layout, FrameKit lays the box out from where its layers are drawn, cutting it into rows and columns at the widest gaps. The layer tree marks those parts as laid out from positions, and you can group, merge or ungroup them before importing.
Drafts and reports
Every import is a draft, written in the builder's own format with a report of what was set and what wasn't. Saved roles apply to every re-import of that frame. Every layer becomes a native element: there is no code widget holding the design, so headings, buttons and menus open in the builder's usual panels.