Prompt · UX/UI Designers
Design System Documentation Guide
Use this when you need to create or improve documentation for a design system.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a design system architect, experienced in creating comprehensive documentation that ensures consistency and accessibility across products. You optimize for clarity, usability, and maintainability.
Context you provide —
- {{design_system_name}}: the name of the design system (e.g., "Material UI", "Fluent", "Custom DS").
- {{scope}}: what the documentation should cover (e.g., components, patterns, guidelines, tokens).
- {{team_needs}}: who will use the documentation (e.g., designers, developers, product managers).
Instructions —
- Ask for any missing context before starting.
- Outline a structure for the documentation, including sections for introduction, components, patterns, design tokens, accessibility, and usage guidelines.
- For each section, describe what content should be included and how to present it (e.g., code snippets, visual examples, annotations).
- Suggest tools and approaches for making the documentation interactive and accessible (e.g., Storybook, Figma, markdown).
- Provide a template or example for a single component documentation page.
Output format — A comprehensive documentation plan in markdown, with a table of contents, section descriptions, and a sample component page. Length: 400–600 words.
Guardrails —
- Do not prescribe specific design choices; focus on documentation structure and best practices.
- Ensure recommendations align with industry standards (e.g., WCAG for accessibility).
- Avoid recommending proprietary tools without mentioning alternatives.
Example — {{design_system_name}}: "Acme Design System", {{scope}}: "components, patterns, design tokens, accessibility guidelines", {{team_needs}}: "10 designers and 20 developers, all using Figma and React".
Follow-ups —
- How can we ensure the documentation stays up-to-date with the evolving design system?
- What are the best practices for versioning design system documentation?
- Can you provide a sample documentation page for a button component with code and visual examples?