UI Component Library with Inventory and Prioritization
Comprehensive audit of required components, organized by category, with a prioritized build roadmap.
Conduct a UI inventory and determine which components to build first for the design system, maximizing impact with minimal initial effort.
At a glance
Access
Free prompt
Open to copy without upgrading.
Prompt objective
Conduct a UI inventory and determine which components to build first for the design system, maximizing impact with minimal initial effort.
Real use case
A marketing SaaS company decided to build their design system from scratch after years of using ad hoc components. The initial inventory identified 340 button variations across 12 products. They need to define the core library and build order.
Customize these fields first
Replace the placeholders with your own context before you run the prompt. That usually improves the first output more than adding more instructions later.
Prompt
Plan the component library for [COMPANY/PRODUCT]'s design system, which spans [NUMBER] products/applications and [NUMBER] designers and developers.\\\\\\\\n\\\\\\\\nDevelopment stack: [REACT/VUE/ANGULAR] with [CSS FRAMEWORK/APPROACH].\\\\\\\\nDesign tool: [FIGMA/ADOBE XD].\\\\\\\\n\\\\\\\\n**1) Interface Inventory:**\\\\\\\\n- Audit existing products:\\\\\\\\n - How many distinct buttons exist? (count all variations)\\\\\\\\n - How many inputs, cards, modals, tables?\\\\\\\\n- Categorize by usage frequency (how many screens use each component)\\\\\\\\n- Identify inconsistencies (same component, different designs)\\\\\\\\n- Screenshot every variation found\\\\\\\\n\\\\\\\\n**2) Component Taxonomy:**\\\\\\\\nOrganize into categories:\\\\\\\\n- **Primitives**: Button, Input, Select, Checkbox, Radio, Toggle, Badge, Avatar, Icon\\\\\\\\n- **Composite**: Card, Modal, Drawer, Toast, Dropdown, Tabs, Accordion, Pagination\\\\\\\\n- **Patterns**: Form, Table, Navigation, Header, Footer, Sidebar, Empty State\\\\\\\\n- **Layout**: Grid, Stack, Container, Divider, Spacer\\\\\\\\n\\\\\\\\nFor each component:\\\\\\\\n- Required variants (size, variant, state)\\\\\\\\n- Props/properties (text, icon, disabled, loading)\\\\\\\\n- Slots/children (what can be inserted inside)\\\\\\\\n- Real usage example from the product\\\\\\\\n\\\\\\\\n**3) Prioritization:**\\\\\\\\n- Impact vs. effort matrix for each component\\\\\\\\n- Tier 1 (Week 1-2): components used in >80% of screens\\\\\\\\n- Tier 2 (Week 3-4): components used in >50% of screens\\\\\\\\n- Tier 3 (Month 2+): specialized components\\\\\\\\n- Dependencies between components (Button before Modal)\\\\\\\\n\\\\\\\\n**4) Documentation Standard:**\\\\\\\\nFor each component in the library:\\\\\\\\n- Anatomy (labeled component parts)\\\\\\\\n- Visual variants with guidance on when to use each\\\\\\\\n- Do's and Don'ts with visual examples\\\\\\\\n- Accessibility specs (keyboard, screen reader, ARIA)\\\\\\\\n- Code examples\\\\\\\\n\\\\\\\\n**5) Governance:**\\\\\\\\n- Contribution process (how to propose a new component)\\\\\\\\n- Acceptance criteria (design review + code review + a11y check)\\\\\\\\n- Semantic versioning\\\\\\\\n- Deprecation of legacy components\\\\\\\\n\\\\\\\\nGoal: deliver Tier 1 in [TIMELINE] with [NUMBER] dedicated designers/devs.
Open directly in an AI — the text is pre-filled:
How to use this prompt
- 1Replace the key placeholders first: COMPANY/PRODUCT, NUMBER, REACT/VUE/ANGULAR, CSS FRAMEWORK/APPROACH.
- 2Replace any bracketed placeholders like [this] with your own context.
- 3Add extra background information when you want more tailored results.
- 4Combine multiple prompts in one conversation when you need a richer output.
- 5Save your best-performing prompts so they are easy to reuse later.
Next best step
Open the guide first, then branch only if you still need more.
A starter guide to the first prompt categories and patterns worth using when you need better output without prompt guesswork.
If this prompt is close but not quite right, generate variants next. If the job is recurring, move into the course library after the guide.
Related prompts
View allMulti-Platform Design Tokens with Figma-to-Code Synchronization
Design token architecture that works across Figma, React, React Native, and CSS, with automated synchronization pipeline.
Best for
Implement a design token system that serves as the single source of truth between design and code, eliminating visual inconsistencies across platforms.
Design System Documentation in Storybook with Live Examples
Interactive Storybook documentation structure that serves as a unified reference for designers and developers.
Best for
Create design system documentation in Storybook that becomes the single reference for the entire organization, with interactive examples, usage guidelines, and a playground for experimentation.
Design System Versioning Strategy and Breaking Changes Management
Semantic versioning, migration guides, and breaking change communication for a design system used by multiple product teams.
Best for
Implement a versioning process that allows the design system to evolve without breaking existing products, with clear migration paths and efficient stakeholder communication.
Design System Adoption Strategy for Resistant Organizations
Tactical plan to increase adoption of a design system in an organization where teams prefer building custom solutions.
Best for
Create a change management strategy that transforms an underutilized design system into an organizational standard, overcoming resistance from autonomous teams.
Explore other prompt categories
Move sideways into adjacent libraries when the current category is not the full answer.
Free browsing stays open. Premium prompts unlock the reusable workflow layer.
Use the guides and role paths to validate the job first. Upgrade when you want the full prompt text, editable premium prompts, and the surrounding course paths in one place.
Free access
- Browse guides, role paths, and category pages.
- Preview prompts before you decide to upgrade.
- Find the right starting point without friction.
Membership access
- Unlock premium prompts and the full copy text.
- See more workflow paths and course connections.
- Keep the reusable templates in one place.
