Know what you’re handing off.

Your coding agent builds the application in your chosen stack. Rebuildez supplies measured reference evidence, component relationships and an implementation checklist. You can ask the agent to reproduce the design or adapt its content.

Through the optional Rebuildez for Figma pilot plugin. Select complete, layered frames. Original PNGs and native design data are retained before conversion to derived HTML. Missing fonts, unsupported nodes and image-only frames are labeled. A static conversion does not prove Figma Smart Animate fidelity.

No. Choose desktop, tablet, mobile or custom sizes. One source screen at one requested size uses one extraction unit. Only the sizes you request are captured.

Supported CSS and Web Animations include targets, timing, state changes and sampled filmstrips. Supported native scroll and view timelines include sampled positions. Arbitrary JavaScript animation, canvas rendering and every continuous instant are not guaranteed. Incomplete or unsupported evidence stays labeled.

Supported assets are bundled and their loading status is recorded. Missing or invalid required assets are reported. Video bytes and metadata can be retained, but this does not verify video playback. Figma image-only frames cannot provide an editable component structure.

Reference evidence is stack-neutral, so an agent can use it for React, Next.js, Flutter or other stacks. A PNG from any implementation can be compared at matching dimensions. Live DOM checks require a browser-rendered app; canvas and native screenshots do not expose ordinary DOM component bindings.

No. Measurements may be usable while a supplied reference PNG differs. Missing references remain unverified. Normal verification checks appearance; full verification additionally checks supported motion. Measured differences and your accepted deviations remain separate.

Reference designs are uploaded for cloud extraction. Complete results download into your project’s .rebuildo folder. Cloud transfer files are temporary and subject to cleanup. Local verification runs against your application on your computer; it does not upload your application code. Review private design contents before committing evidence to Git.

The thin CLI and local MCP adapter use your supported Node.js installation. Browser verification tools are an optional, separate download. The Figma helper is optional too. Windows x64 is the currently qualified terminal installation; Linux and macOS are not qualified for this release.

Yes. Saved reports, component evidence and local verification remain usable without new extraction units. New cloud extraction requires a signed-in account with an available allowance. Your coding agent’s own usage costs are separate.

Not yet. Access is currently a controlled pilot and paid checkout is not open. The proposed allowance is five one-time trial units and 100 units per paid month. Price, payment arrangements and launch terms will be announced before subscriptions open.