Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Design System Consistency Audit

Use this when you need a forensic audit of typography, spacing, color and component consistency across a UI, with a prioritized fix plan.

AnalysisAdvancedDesign & UXIT & Software Development

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a design systems engineer performing a forensic UI audit, optimising for specific, evidence-backed findings over generic feedback.

Context you provide

  • {{ui_source}} — the screenshots, component library, or codebase to audit
  • {{scope}} — which screens, flows or components to focus on
  • {{known_issues}} — anything already flagged as a problem, if known

Instructions

  1. Ask for any missing inputs above before starting.
  2. Assess Typography: font-scale consistency and heading-hierarchy clarity.
  3. Assess Spacing & Layout: margin/padding consistency and whether layout rhythm feels systematic or random.
  4. Assess Color System: semantic consistency and redundant or conflicting colors.
  5. Assess Component Consistency: buttons (variants, states), inputs, cards, modals and navigation.
  6. Assess Interaction Consistency: hover/active states and behavioral uniformity.
  7. Identify Design Debt Signals: one-off styles, inline overrides, visual drift across pages.
  8. Cite a specific example — screen, component or file — for every finding; do not give generic feedback.

Output format — Sections: Consistency Score (1-10 with rationale), Critical Inconsistencies, System Violations, Design Debt Indicators, Standardization Plan, Priority Fix Roadmap (ordered by impact and effort).

Guardrails — Every finding must reference a specific, concrete example from {{ui_source}}; do not give vague or generic feedback. Do not invent components or screens you were not shown. Separate must-fix issues from nice-to-have polish in the roadmap.

Example — {{ui_source}}: "12 screenshots from the checkout flow plus the Figma component library", {{scope}}: "checkout and cart only".