Frontend & Design · warpdotdev/warp

Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

warpdotdev/warp

Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

warpdotdev/warp

Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

warpdotdev/warp

Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.

warpdotdev/warp

Maps published Figma components to their code implementations with Code Connect, using the Figma MCP suggestion and mapping tools.

warpdotdev/warp

Creates a new blank Figma design or FigJam file in your drafts folder through the Figma MCP server, resolving the plan key first when needed.

warpdotdev/warp

Builds or updates full Figma screens from code or a description by reusing the file's published design system components, variables and styles.

warpdotdev/warp

Creates or revises Figma designs from a written description using the Figma MCP authoring tools, in a new blank file or an existing one.

warpdotdev/warp

Steps for adding a one-time launch or announcement modal to the Warp desktop GUI, gated by a feature flag and tracked by a settings field.

warpdotdev/warp

How to build a settings page in the Warp desktop client so widgets, page titles and settings search behave correctly, and which common mistakes to avoid.

warpdotdev/warp

Rules for writing UI code in Warp's headless TUI front-end with the cell-grid TuiElement library, kept separate from the pixel-based GUI app.

warpdotdev/warp

Guidelines for writing UI code in Warp's GUI desktop client, centered on reusing shared components and themes instead of adding one-off styling.

warpdotdev/warp