Community Questions
Real questions designers ask about design systems, tokens, AI workflows, and team processes. Curated from Reddit discussions with the most valuable answers.
Real questions from r/DesignSystems and r/FigmaDesign, sorted by community engagement. Use these to understand what practitioners actually struggle with.
Source: Reddit, scraped March 2026
AI + Design Systems
The hottest topic in design systems right now. How teams are integrating AI into their workflows.
- In the Age of Vibe Coding, Design Systems Become the Product (109 upvotes, 25 comments)
- Has anyone actually cracked a 10/10 AI workflow for Figma to React Native? (33 upvotes, 18 comments)
- How are you using AI to build design systems? (24 upvotes, 14 comments)
- How are you incorporating AI into your design process? (23 upvotes, 29 comments)
- I connected my Design System to AI. Now I can re-theme the entire UI with one prompt (23 upvotes, 4 comments)
- Design technologists, UX engineers: how is your role changing? (21 upvotes, 14 comments)
- Design to Engineering Handoff and Documentation gaps are serious pain (20 upvotes, 17 comments)
- Vibe coded this site from Figma, Claude Sonnet 4 + Kombai (302 upvotes, 56 comments)
Design Tokens
Naming, governance, dark mode, multi-brand. The questions your prompt library should answer.
- I built an offline color engine for Design System audits. 1ms AAA scores (53 upvotes)
- How I learned the hard way that token architecture IS governance (41 upvotes)
- Design tokens won’t fix brand consistency if the real problem is governance (37 upvotes)
- I built a Figma Plugin to find values in raw and suggest token replacements (31 upvotes)
- I built a free Figma plugin that generates changelogs for your design system (29 upvotes)
Team Process and Governance
How teams adopt, scale, and govern design systems. Real experiences, not theory.
- I’m building a design system generator + Figma plugin to speed up UI (113 upvotes, 23 comments)
- Adding more liveliness and joy to design system documentation (58 upvotes)
- A closer look at clean and functional design system documentation (34 upvotes)
- Do you maintain a UX pattern library for your team? (18 upvotes, 12 comments)
Figma and Tools
Plugins, workflows, and techniques from r/FigmaDesign.
- I created plugin that generates mathematically perfect shades and tints (705 upvotes, 77 comments)
- Figma just announced Slots component feature (668 upvotes, 181 comments)
- Google just dropped Stitch and it might actually threaten Figma (647 upvotes, 278 comments)
- How to easily calculate radius values in Figma (911 upvotes, 40 comments)
- I made a Figma plugin that generates patterns based on any selected objects (334 upvotes, 25 comments)
Key Takeaways for Your Practice
From analyzing these discussions, the community’s biggest pain points are:
- Token governance, not token naming. People know naming matters but can’t get their team to follow conventions.
- AI workflow gaps. Everyone wants Figma to code with AI, but few have a reliable end-to-end pipeline.
- Documentation is the bottleneck. Teams build components but skip docs, then struggle with adoption.
- Design-dev handoff remains broken. MCP and AI tools are starting to fix this, but most teams are still copy-pasting.
- Component variants are underused. Teams build the happy path but miss states, edge cases, responsive behavior.
These pain points map directly to the prompts, guides, and workflows in this library.
Try with Prompts
Ready-to-use prompts related to this guide
Review AI-generated or hand-written code against a Figma design to catch visual mismatches, missing states, and token drift.
Review a component or page for WCAG 2.1 compliance, covering contrast, keyboard navigation, screen readers, and motion.
Translate brand guidelines (PDF, style guide) into a structured set of design tokens with proper naming and hierarchy.