Skip to main content
ReactCustom Hooksadvanced

Compound Component & Polymorphic Slot Pattern Architect

Optimized for Claude, Chatgpt, Gemini • Verified Prompt Template

Design flexible, headless design system primitives with compound subcomponents, context injection, and accessible keyboard navigation.

Compatibility & Specs

Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedApr 1, 2026
Customizable Variables3 parameters

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

01

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

02

2. Send to AI Model

Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.

03

3. Review and Iterate

Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.

Prompt Variables & Parameters

Reference breakdown of every dynamic variable embedded in this prompt template.

PlaceholderParameter NameTypeStatusDescription & Guidance
[component_type]Component TypeselectRequiredThe UI primitive you want to architectDefault: Accordion (single or multiple expansion)
[styling_paradigm]Styling ParadigmtextRequiredCSS solution usedDefault: Tailwind CSS with clean data-state attributes
[accessibility_requirements]Accessibility RequirementstextareaRequiredWCAG standards and keyboard patternsDefault: Follow W3C WAI-ARIA Accordion Pattern: Up/Down arrow navigation between headers, Home/End to jump to first/last, Space/Enter to toggle, correct aria-expanded and aria-controls linking.

Example Output & Parameters Breakdown

Inspect verified benchmark AI responses and review how parameters, system constraints, and input variables calibrate generation.

Parameters & Variable Breakdown

3 Inputs
[component_type]
Accordion (single or multiple expansion)
[styling_paradigm]
Tailwind CSS with clean data-state attributes
[accessibility_requirements]
Follow W3C WAI-ARIA Accordion Pattern: Up/Down arrow navigation between headers, Home/End to jump to first/last, Space/Enter to toggle, correct aria-expanded and aria-controls linking.

Verified AI Benchmark Response

Grounded Output
### 1. Consumer Usage Example ```tsx <Accordion type="single" collapsible defaultValue="item-1"> <Accordion.Item value="item-1"> <Accordion.Trigger>What is our cancellation policy?</Accordion.Trigger> <Accordion.Content>Cancel anytime with 1-click in your account dashboard.</Accordion.Content> </Accordion.Item> <Accordion.Item value="item-2"> <Accordion.Trigger>Do you offer annual invoicing?</Accordion.Trigger> <Accordion.Content>Yes, annual billing includes a 20% discount.</Accordion.Content> </Accordion.Item> </Accordion> ``` ### 2. Context Safety Guard ```typescript const AccordionContext = React.createContext<AccordionContextValue | null>(null); export function useAccordion() { const context = React.useContext(AccordionContext); if (!context) { throw new Error('Accordion subcomponents must be used within an <Accordion> provider.'); } return context; } ```

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Design system teams building enterprise UI component libraries
Frontend engineers replacing fragile boolean-prop dialogs with flexible composition
Developers mastering headless accessibility patterns and keyboard navigation

Tips for Best Results

Techniques to elevate response fidelity

  • •Specify your exact runtime and dependency versions (e.g. Next.js 15, React 19, TypeScript 5.4) to eliminate outdated syntax hallucinations.
  • •Ask the model to enumerate potential runtime failure modes, concurrency issues, or null boundary states before generating code.
  • •Request idiomatic, type-safe solutions with clear unit test skeletons rather than monolithic scripts.

Common Mistakes to Avoid

Frequent failure modes and anti-patterns

  • •Pasting large unformatted code dumps without indicating the specific function or error you want analyzed.
  • •Deploying AI-generated code directly to production without verifying memory safety, edge cases, and security vulnerabilities.
  • •Omitting architectural constraints (such as SSR vs. client component boundaries or database indexing).

Frequently Asked Questions About This Prompt

Technical guidance on model compatibility, parameter substitution, iteration techniques, and commercial usage.

Q1.Which AI models work best with the "Compound Component & Polymorphic Slot Pattern Architect" prompt?

This prompt is thoroughly tested and compatible with Claude, Chatgpt, Gemini. For multi-step reasoning, architectural planning, and code refactoring, Claude 3.7/3.5 Sonnet and ChatGPT-4o provide the highest constraint adherence. For large-document synthesis, Google Gemini 2.5 Pro is also recommended.

Q2.How do I customize the parameters in this prompt template?

This template features 3 customizable parameter(s): [component_type], [styling_paradigm], [accessibility_requirements]. Replace each bracketed placeholder with your project's specific details, constraints, or code before submitting to your AI model. You can also use our interactive workbench on this page to populate and copy the completed prompt in one click.

Q3.Can I use this prompt and its outputs for commercial projects?

Yes. All prompts published on Beautiful AI Prompt are 100% free for both personal and commercial use. You hold full ownership of all code, copy, strategies, or imagery generated by your selected AI model when running this prompt.

Q4.How does this prompt prevent AI hallucinations and ensure output accuracy?

This template enforces explicit negative constraints, few-shot parameter boundaries, and schema requirements (such as tabular comparisons or step-by-step logic). This suppresses speculative drift and forces the AI model to ground its response in your provided inputs.

Part of Curated Collections

This prompt is sequenced as part of these goal-oriented workflows

View all collections

Related AI Prompts

Complementary workflows in React

View all React prompts
Reactadvanced

React 19 Server Components & Actions Architecture Review

Audit React components for optimal Server/Client component boundary placement and zero hydration shift.

[Copy & Paste Template]2 parameters

›You are a Principal Frontend Architect specializing in React 19, React Server Components (RSC), and modern rendering pipelines. Component Hierarchy Description: [component_hierarchy] Interactive Requirements: [interactive_requirements] Provide the optimal React 19 architecture: 1. Server vs. Client Boundary Map: Clearly designate which components remain Server Components and which require `'use client'` at the lowest leaf nodes. 2. Data Fetching Strategy: Show how data fetching occurs natively in async Server Components without client-side `useEffect` waterfalled fetching. 3. Form & Mutation Handling: Demonstrate modern React 19 Server Actions paired with `useActionState` and `useOptimistic`. 4. Hydration & Bundle Analysis: Explain the exact JavaScript bundle savings achieved by keeping presentation logic server-side.

claudechatgpt
#react#react-19#server-components
Reactadvanced

React Re-render Thrashing & Memoization Auditor

Diagnose unnecessary child re-renders, unstable object references, and misuse of useMemo/useCallback in React components.

[Copy & Paste Template]3 parameters

›You are a Principal React Performance Engineer and React DevTools Profiler Specialist. I have a React component tree that experiences severe re-render thrashing, sluggish input response, or dropped animation frames. React Version: [react_version] Component Code Tree: [component_code] Observed Performance Lag & Profiler Clues: [observed_symptoms] Deliver an authoritative React rendering optimization audit: 1. Re-render Cascade Root Cause: Identify the exact mechanism causing unnecessary re-renders (e.g. inline callback recreation, object literal recreation in props, broad React Context value updates, un-memoized component boundaries). 2. Myth vs. Reality on useMemo/useCallback: Objectively evaluate whether adding `useMemo` or `useCallback` here is genuinely beneficial or counter-productive overhead. 3. Optimized Component Refactoring: Drop-in replacement code utilizing state collocation, children-as-props slot isolation, atomic context splitting, or `React.memo` with custom comparison. 4. Verification Steps in React DevTools Profiler: Exact guide to recording a profile before and after to prove render durations dropped from milliseconds to sub-millisecond ranges.

claudechatgptgemini
#react-performance#re-renders#usememo
Reactadvanced

Zustand & Finite State Machine Architecture Designer

Model complex asynchronous UI workflows using Zustand slices or XState finite state machines to prevent invalid UI states.

[Copy & Paste Template]3 parameters

›You are a Principal Frontend Architect and State Management Guru. I need to model a complex, asynchronous user interaction in React that currently suffers from boolean explosion (`isLoading`, `hasError`, `isEditing`, `isSaving`) and inconsistent UI states. Target Feature / Flow: [feature_flow] State Management Tool of Choice: [state_tool] Async Transitions & User Actions: [async_transitions] Deliver an authoritative State Architecture Blueprint: 1. State Transition Diagram & Invariant Matrix: Enumerate the exact finite states (e.g. `idle`, `authenticating`, `authenticated`, `error`) and legal transitions, proving mathematically that impossible states cannot occur. 2. Complete Store / State Machine Code: Type-safe TypeScript implementation using [state_tool] with clean slice organization, atomic selectors, and immutability. 3. Error & Retry Boundary Mechanics: How network failures or expired tokens are trapped and recovered without losing un-submitted user inputs. 4. Consumer React Component Example: Demonstrating how clean the UI layer becomes when querying explicit state tags (`state === 'submitting'`) instead of nested booleans.

claudechatgptgemini
#state-management#zustand#state-machine