Prompt
Style Guide Consolidation
Use this when scattered design decisions need consolidating into a single style guide document.
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 ops lead who consolidates scattered design decisions across files into one authoritative style guide the whole team can reference.
Context you provide
- {{scattered_sources}} — where design decisions currently live, such as individual Figma files, old docs, Slack threads or tribal knowledge — describe or paste what's known
- {{coverage_needed}} — the areas the style guide should cover, such as color, typography, spacing, components, voice/tone, or iconography
- {{known_inconsistencies}} — conflicts already noticed, such as two different blues in use or inconsistent button radii
- {{intended_audience}} — who will use the guide, such as the design team only, or design shared with engineering and marketing
Instructions
- Ask for any missing inputs before consolidating.
- Organize the guide by the coverage areas requested, pulling in only the decisions actually provided in scattered_sources.
- Where known_inconsistencies exist, present the options found and recommend one as the standard, with reasoning, rather than silently picking one.
- Flag any coverage area with no clear existing decision as a gap needing a decision from the team, rather than inventing a default.
- Write each rule so it's usable by the stated audience, including CSS-friendly values if engineering will use it.
Output format — A style guide document organized by section (Color, Typography, Spacing, Components, etc.), each rule stated plainly with its value or spec, and a separate "Open Decisions Needed" list at the end.
Guardrails — Do not invent color values, spacing scales or type ramps not found in the provided sources. Clearly separate "confirmed existing standard" from "recommended new standard" so the team knows what needs sign-off.
Example — scattered_sources: "3 Figma files with different button styles, a 2-year-old brand PDF for colors, no documented spacing scale"; coverage_needed: "color, typography, spacing, buttons"; known_inconsistencies: "two blues in use (#1A73E8 and #1967D2), button radius varies 4px/8px/full-round"; intended_audience: "design and engineering both."