Prompt Tools

Prompts That Keep a Design System Whole

Two tools that write the prompt, so a model builds in Figma from a design system’s own tokens instead of guessing. The first builds the foundation and records it in a design-system.md file. The second reads that file and specs one component at a time. Both run in the browser and send nothing anywhere.

How the Two Fit Together

Foundation First, Then One Component at a Time

A model builds the wrong thing when it has to guess a color, a space or a text style. These two tools take the guessing out, in this order.

  1. Describe the Foundation

    In the Fundamental Design System Prompt Composer, list the modes, colors, spacing, sizes, radii, text styles and effects, with their values.

  2. Run the Prompt in Figma

    Copy the Figma prompt into an agent with the Figma connector, or into a chat model that writes a plugin script. It creates exactly those variables and styles.

  3. Keep the design-system.md

    The same form writes a plain text file of the token names, modes, library components and house rules. Values stay in Figma, so a model cannot paste them in place of a binding.

  4. Load It Into the Component Composer

    The Consistent Component Prompt Composer reads the file and fills in the tokens, modes and rules. Only the component is left to describe.

Nothing is uploaded. Each tool keeps its draft in this browser only.