What Onefold reads
- Components and sets
- Published components and component sets from the libraries you select, with their Figma identifiers retained so a rename does not lose the thread.
- Variants and properties
- The variant axes and their values, which are the strongest signal available for matching a design component to a code component's props.
- Variables and styles
- Design variables, their collections and modes, and the styles that predate them. These are compared against the tokens found in code.
- Descriptions
- Component descriptions, which are usually the only place the intent behind a component was ever written down, and which almost always score badly.
Onefold does not read your design files as pixels, does not render frames, and has no interest in work-in-progress canvases. It reads the published library, because that is the part that claims to be the system. There is no Figma plugin to install.
How mapping works
Deterministic signals first, model judgement only where the signals disagree. Every mapping carries its evidence and a confidence value.
- Confirmed
- A person has verified this mapping. It outranks everything below it and does not get overwritten by later inference.
- High confidence
- Multiple independent signals agree: the name, the variant structure and the description all line up. Safe to rely on, still worth confirming once.
- Possible
- Something matches, but not enough to act on. Usually a renamed component, or two candidates that both fit.
- Unmapped
- A Figma component with no implementation, or an implementation with no design counterpart. Both are findings, and they mean different things.
- Conflict
- Two plausible mappings that cannot both be true. Surfaced rather than silently resolved, because the resolution is a decision, not a calculation.
Why a person always wins
Mapping is the one place in the product where being wrong is expensive, because a bad mapping does not look wrong. It looks like an answer. So confirmation is a first-class action: you can accept or reject any mapping, and your decision becomes stronger evidence than any model inference, permanently.
This is also why unmapped is a real status rather than a gap in the table. A Figma component with no implementation might be a missing feature, or it might be a component design abandoned two quarters ago. Only you know which, and the product should ask rather than guess.
Connect Figma when it helps, not to complete a set. Until you do, the design and code mapping dimension is excluded from your readiness score rather than counted as zero. A GitHub-only report is a complete report, just a narrower one. See AI Readiness.
See where design and code disagree
Figma reconciliation follows GitHub analysis in early access. The waiting list is the way in.
Request early access