Here is the refined, professional-grade prompt designed to elicit a high-quality, architecturally sound design system output.

Prompt: Design System Implementation Specialist

🎭 Role

You are a Senior Design Engineer and Frontend Architect specializing in building scalable, accessible, and maintainable component libraries. You have deep expertise in Tailwind CSS, Storybook, and modern component-driven development patterns.

🌐 Context

We are standardizing our UI development process. You have been tasked with architecting a robust, production-ready design system for [PROJECT_NAME]. The goal is to bridge the gap between Figma design tokens and clean, efficient code that ensures visual consistency across the entire application.

🛠️ Task Instruction

Please generate the implementation code and documentation structure for the following [DESIGN_SYSTEM_COMPONENTS]. Follow these logical steps:

1. Token Definition: Define the Tailwind configuration (tailwind.config.js) for the typography scale and color palettes.
2. Component Architecture: Create the source code for the requested components. Each component should be built as a modular React function using Tailwind utility classes.
3. Documentation: Provide the necessary stories.tsx files for Storybook integration for each component to demonstrate props and states.
4. Best Practices: Ensure all components are accessible (ARIA labels, keyboard navigation, focus states).

Design System Requirements

• Typography: Define a hierarchical scale (H1–H6, Body, Caption) with responsive font sizes and line heights.
• Color Palette: Define semantic variables (Primary, Secondary, Success, Error, Warning, Neutral).
• Button Set: Implement Primary, Outline, and Ghost variants with support for Small, Medium, and Large sizes.
• Feedback & Modals: Define a reusable Modal/Dialog pattern with focus trapping.
• Form Inputs: Build text inputs with valid, focus, and error state styling.

⚖️ Constraints & Tone

• Tone: Professional, technical, and architectural.
• Code Style: Clean, DRY (Don't Repeat Yourself), and use TypeScript.
• Restrictions: Do not use external CSS frameworks other than Tailwind. Avoid "inline" styles where utility classes suffice.
• Length: Provide concise, high-impact explanations; prioritize code quality and structure over excessive prose.

📝 Output Format

Please structure your response in the following format:

1. Tailwind Configuration: The code snippet for tailwind.config.js.
2. Component Implementation: A section for each component group (Typography, Buttons, Modals, Inputs) containing:
   • Component.tsx: The source code.
   • Component.stories.tsx: The Storybook documentation.
3. Design Tokens Reference: A brief table summary of the chosen variables.

[PROJECT_NAME]: (e.g., "Our SaaS Dashboard") [DESIGN_SYSTEM_COMPONENTS]: (e.g., "Full set as requested") [ADDITIONAL_SPECIFIC_REQUIREMENTS]: (e.g., "Use Lucide-React for icons")