Prompts / design_md

Create or check a DESIGN.md Free

Interviews you or reads an existing site or Figma file, then writes a DESIGN.md (the context file models read before building) and checks it.

Run it

• Claude Code: /mcp__designers__design_md
• Claude Desktop and claude.ai: plus menu, Add from Designers, Create or check a DESIGN.md
• Any app: Use the design_md prompt from the Designers server on a live url, a figma link, or a description of the product and brand.

Arguments

* required

What your assistant is told to do

The full instructions, so you can see exactly what you are asking for:

Create or improve a DESIGN.md: the file that tells a model how this product looks and sounds before it builds anything.

Source: <source>
Existing file: <existing>

1. Read resource designers://templates/design-md for the structure and resource designers://reference/slop-tells for what generic output looks like.
2. If an existing DESIGN.md was given, call lint_design_md on it and fix what it flags. Otherwise gather facts: for a live URL read its CSS values (colours, fonts, spacing) with detect_design_slop and audit_page_accessibility for what they show; for Figma If the input is a Figma link: parse it (figma.com/design/:fileKey/..., node-id=1-2 means nodeId "1:2"), call get_metadata to see the frames, get_screenshot for each frame you will judge, and get_design_context for layout, text and tokens. Read the picture before the code. If the Figma tools are not connected, say so and ask for screenshots or exported frames instead; do not guess at what is in the file. then call get_variable_defs for tokens. Never guess a value you can read.
3. Ask the person up to five short questions you cannot infer: who uses it and in what state of mind, three words for the feel and two it must not feel like, the one thing the design must never do, a screen they think is right and one that is wrong.
4. Write the DESIGN.md from the template with real values: hex colours with roles, typefaces with fallbacks and a scale, spacing unit and layout rule, component rules with states, a never-list of specific defaults to reject, and references. Check every text and background pair with check_contrast and fix failures.
5. Call lint_design_md on the result and fix any high or medium finding. Keep it under 1,500 words.
6. Tell the person where to save it (the project root as DESIGN.md) and how to use it ("read DESIGN.md before any UI work"). With Pro, offer to store it with save_project_context.