Design System Component Spec

Create a precise, production-ready specification for a reusable UI component that developers and designers can implement consistently.

Category
Design & UX
Output
Markdown
Fields
3
  • specification
  • design-review
  • documentation
  • best-practices
  • technical-writing
  • ux-critique

Fill in the details

The UI element you want to specify (e.g., button, dropdown, card).

Design system guidelines, color palette, typography rules, or visual references.

Where and how this component will be used (e.g., dashboard header, checkout flow, mobile app).

Prompt

You are an expert UI/UX designer and design systems architect. Your task is to create a precise, production-ready specification for a reusable UI component that developers and designers can implement consistently. Use the following inputs to build the specification: - Component: Component Name - Brand & Style Context (if provided): Brand & Style Context - Usage Context (if provided): Usage Context Follow these steps to structure your response: 1. Anatomy & Variants: Break the component into its core visual parts. List all logical variants (e.g., primary/secondary, sizes, orientations). 2. Interactive States: Define visual and behavioral rules for default, hover, focus, active, disabled, loading, and error states. Present these in a clear table. 3. Spacing, Sizing & Design Tokens: Specify padding, margins, border radii, and font sizes. Map all values to abstract design tokens (e.g., `--space-md`, `--color-primary-500`) rather than hardcoded values. 4. Behavior & Interaction Rules: Describe click/tap targets, animation durations, transition easing, and any conditional logic or state transitions. 5. Accessibility Requirements: Detail keyboard navigation, focus management, ARIA attributes, minimum contrast ratios, and screen reader announcements. 6. Usage Guidelines: Provide clear do/don't examples and edge cases to prevent misuse across the product. Constraints: - Rely strictly on the provided inputs. Do not invent brand colors, token names, platform constraints, or technical implementations. - If brand context or usage details are omitted, infer standard design system conventions for the specified component type and note any assumptions in the Open Questions section. - If any critical detail is missing or ambiguous, append a brief "Open Questions" section at the end instead of guessing. - Format the entire response as a clean Markdown document using headings, bullet points, and tables where appropriate.

How to use this prompt

  1. Fill in the fields above. Required ones are marked with *.
  2. Check the prompt preview: your answers appear highlighted in place.
  3. Select Copy prompt and paste it into ChatGPT, Claude, Gemini or any AI assistant.
See all Design & UX prompts