Cursor generates frontends from design systems

Cursor’s docs show teams can encode a design system as a rules file (example:.cursor/rules/design-system.mdc) that lists canonical component imports, token variables (e.g., var(--color-primary)), spacing scales, and patterns so generated code imports existing UI components instead of inventing new ones. (cursor.com)) Figma on March 24, 2026 released a use_figma tool for its MCP server that lets AI agents — including Cursor — create and modify native Figma frames, components, variables and auto‑layout while honoring a project’s design tokens and example skills. (aihola.com)) Cursor’s product updates in March 2026 shipped Composer 2 (announced Mar 19, 2026) with token pricing tiers (Standard: $0.50/M input, $2.50/M output; Fast: $1.50/M input, $7.50/M output) and added JetBrains IDE support via the Agent Client Protocol on Mar 4, 2026. (cursor.com)) A field report from Mirumee on Nov 18, 2025 found Cursor could generate directionally correct UI from a connected Figma design system but frequently improvised styles outside the system and failed to produce reliable component variants without heavy prompt engineering. (mirumee.com)) Multiple community tutorials and video demos published since 2025 walk through wiring Figma MCP to Cursor to generate component libraries, a docs site, and live prototypes — several example walkthroughs show end‑to‑end runs that output component files and a functioning docs site for iterative designer–developer review. (youtube.com)) Cursor’s Mar 2026 changelog also lists 30+ new marketplace plugins (Atlassian, Datadog, GitLab, Hugging Face, PlanetScale) and automated agents that run on Slack/Linear/GitHub triggers and spin up cloud sandboxes, enabling pipelines that pull tokens from Figma, generate code, and run tests as part of the same agentic workflow. (cursor.com))