Claude Prompts for Enterprise Design Strategists: Create a Brand Style Guide That Fixes Design-Dev Misalignment

You are a senior design strategist with 10 years of experience building brand systems and design documentation for large enterprise organisations. Help me create a brand style guide so I can build a consistent brand identity and reduce the misalignment between design and development teams. My situation: - Organisation size: [under 500 / 500-5,000 / 5,000+ employees] - Primary misalignment symptom: [e.g., "developers use outdated colour values" / "different teams interpret the brand differently" / "no single source of truth exists"] - Current documentation state: [no documentation / outdated PDF guide / partial Figma library / full design system in progress] - Who will use this style guide: [designers only / designers and developers / all staff including marketing and comms] - Brand maturity: [new or unestablished / evolving / established but inconsistently applied] - Number of product teams or business units affected: [1 / 2-5 / 6+] - One rule that is consistently broken across teams right now: [describe in one sentence] Deliver: 1. Style Guide Architecture — the section structure for the full guide, ordered so both designers and developers can find what they need without reading the whole document 2. Brand Decision Log — a format for recording why key brand decisions were made, so future teams do not reverse them without context 3. Colour System Documentation — a structured way to document primary, secondary, and functional colours with hex, RGB, and token values, and rules for when each is used 4. Typography Usage Rules — guidelines for typeface, size scale, weight, and line-height that translate directly into developer-ready CSS or token values 5. Component Usage Guidelines — how to document when to use which UI component, with explicit do/don't examples written for a developer audience 6. Design-Dev Handoff Protocol — a repeatable process for how design decisions move from the style guide into production without reinterpretation 7. Governance Model — who owns the style guide, how updates are approved, and how violations are flagged and corrected across teams 8. Adoption Rollout Plan — a phased plan for getting existing teams to migrate to the new guide rather than continuing with old habits **Write the style guide as a working tool, not a showcase document — every section should answer a question that a developer or designer would actually ask at 11am on a Tuesday.**