Agent recipes

These examples assume Fanta is running with a project open and the plugin or direct MCP connection is active.

Build a card

/design On the active page, create a 320×180 frame called Welcome card. Add a heading and a primary button inside it. Build one visible section at a time with auto-layout where needed. Show a screenshot and summarize the .fnx change.

Revise a selection

Inspect the current selection. Change its fill to #4F46E5 and its corner radius to 12. Keep its size and position, then show a screenshot.

Reuse a component

Inspect the selected card and similar copies. If their layer structures match, componentize them so the first is the master and the others become instances with their different text and fills preserved. Verify the result on canvas.

Review before committing

Inspect and screenshot the active page. Check for unparented layers. Read relevant .fnx source and summarize the design changes visible in Git.

Reuse the design system

Inspect the current component properties, variant sets, variable collections, and modes. Reuse the existing spacing and color tokens in a new card; show a screenshot and list the bindings you applied.

Address review comments

List unresolved comments on the active page. Address the comment on the selected card, capture a screenshot, then reply to that exact thread with what changed.

The agent can use get_design_system, batch_get, get_screenshot, and list_comments for verification. With report_agent_activity and the same identity in batch_design.activity, Fanta can follow its streamed canvas edits and file changes. prepare_design_asset only opens a reviewed generation draft. Export and commit remain app or filesystem workflows, rather than additional local MCP tools.

Lay out a grid

Build three card columns in one grid frame. Use 1fr tracks with 16 px gaps, pin the featured card across two columns, and show a screenshot at the intended size.