ChatGPT Prompt for Design Systems
Create a governance plan for maintaining a geometric design system in a entertainment organization.
More prompts for Design Systems.
Define a complete component library spec with atomic design hierarchy, props, variants, states, and implementation guidelines for a scalable design system.
Create a detailed icon set brief that ensures visual consistency, appropriate metaphors, and production-ready specifications for a custom icon library.
Document the Collapsible Sidebar Navigation design pattern for use in a survey builder design system.
Define a detailed component specification for Pagination in a monochromatic design system.
Document the Split-Button Dropdown design pattern for use in a chat application design system.
Define a detailed component specification for Alert Banner in a skeuomorphic design system.
You are a design operations strategist with a track record of helping startup founders achieve increase revenue. Create a governance plan for building and maintaining a geometric design system in a entertainment organization. **Team audience:** CMOs **Design tool:** Knapsack **Framework:** Angular **Goal:** increase revenue ## Design System Mission & Principles - Mission statement: why this design system exists - 5 guiding principles for contribution and decision-making - Success metrics: how to measure the design system's impact - Alignment with entertainment business objectives ## Team Structure & Roles - Core team roles: design system lead, design technologist, UX writer, accessibility specialist - Contributor roles: feature team designers, front-end developers - Stakeholder roles: product managers, engineering managers - RACI matrix for key activities (Responsible, Accountable, Consulted, Informed) ## Contribution Process ### Proposing New Components or Patterns 1. Submission template: problem statement, use cases, proposed solution, alternatives considered 2. Review criteria: reusability threshold (minimum 3 use cases across 2 products) 3. Design review process: critique session format and cadence 4. Approval workflow: who approves and timeline expectations ### Modifying Existing Components 1. Change request template 2. Impact assessment: which products and teams are affected 3. Deprecation policy: notice period, migration guide, sunset date 4. Breaking change protocol: versioning and communication plan ## Quality Standards - Design quality: geometric aesthetic consistency checklist - Code quality: linting, type safety, test coverage requirements - Accessibility: WCAG 2.1 AA minimum, AAA for critical components - Performance: bundle size budgets per component - Documentation: required sections for every component page - Browser/device support matrix ## Release & Versioning - Semantic versioning rules (major.minor.patch) with examples - Release cadence: how often the system ships updates - Changelog format and communication channels - Migration guide requirements for breaking changes - Canary and beta release process for early testing ## Documentation Standards - Required documentation for each component: overview, usage, API, accessibility, changelog - Documentation platform: Knapsack for design, Storybook for code, Zeroheight for unified docs - Content style guide for writing component documentation - Screenshot and example update policy ## Adoption & Evangelism - Onboarding program for new team members - Office hours and support channels - Adoption tracking: component usage metrics across products - Internal showcase: monthly design system highlights - Training workshops: quarterly deep-dives on new patterns ## Roadmap Planning - Quarterly roadmap process: input gathering, prioritization, communication - Prioritization framework for new component requests - Alignment with product roadmaps in the entertainment organization - Technical debt allocation: percentage of capacity reserved for maintenance Structure as a playbook with: Overview, Prerequisites, Step-by-step Plays, Metrics to Track, and Troubleshooting Guide.