Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Magic UI Variations Generator

agent creative skill risk: low

Magic UI Variations Generator

Defines a workflow to analyze UI requirements, generate multiple distinct design variations via Magic by 21st.dev, present options side-by-side, and integrate selected production-r…

SKILL 1 file

SKILL.md
---
name: magic-ui-generator
description: "Utilizes Magic by 21st.dev to generate, compare, and integrate multiple production-ready UI component variations."
---
# Magic UI Generator

Leverage [Magic by 21st.dev](https://21st.dev/magic) to build modern, responsive UI components using an AI-native workflow that prioritizes choice and design excellence.

## Context

This skill leverages Magic by 21st.dev to build modern, responsive UI components. Instead of generating a single standard solution, it focuses on providing multiple design variations to choose from, drawing inspiration from a curated library of real-world components and premium design patterns (Shadcn UI, Magic UI, Aceternity, etc.).

## When to Use
Trigger this skill whenever:

- A new UI component is requested (e.g., pricing tables, contact forms, hero sections).
- Enhancing an existing UI element with animations, better styling, or advanced features.
- Brainstorming different design directions for a specific feature.
- Professional logos or icons are needed (via the built-in [SVGL](https://svgl.app/) integration).

## Execution Workflow

1. **Analyze Requirements**: Review the component description. Ensure the target output aligns with the project's stack (e.g., Next.js, TypeScript, Tailwind CSS). Define clear constraints for accessibility and responsiveness.
2. **Generate Variations**: Interface with the Magic MCP server or use the `browser_subagent` to explore 21st.dev/magic to generate _several distinct, unconventional styles_ for the requested component.
   - **Pro Tip**: Use descriptive prompts pushing for modern aesthetics: "avant-garde SaaS pricing table with glassmorphism and animated borders" or "highly immersive contact form with dynamic floating labels."
3. **Present Options**: Briefly describe the generated variations side-by-side. Highlight stylistic differences, layout approaches, and premium features (sticky headers, hover animations, etc.).
4. **Integrate Selection**: Once a favorite variation is chosen:
   - Integrate the fully functional, production-ready TypeScript code.
   - Ensure dependencies (`lucide-react`, `framer-motion`) are installed.
   - Handle proper props, types, and responsive behaviors.

## Strict Rules

- **ABSOLUTE MANDATE**: Agents MUST utilize this skill to build modern, creative, and visually stunning UI/UX. DO NOT build in common, generic, or safe styles. Push boundaries.
- **Choice First**: Always offer multiple premium design variations before writing the final code to the project.
- **Clean Code**: Ensure all generated code is clean TypeScript, accessible, and responsive.
- **Full Ownership**: Treat all generated components as fully owned.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

REQUIRED CONTEXT

  • component description

OPTIONAL CONTEXT

  • project stack
  • design constraints

TOOLS REQUIRED

  • browser_subagent

ROLES & RULES

  1. Agents MUST utilize this skill to build modern, creative, and visually stunning UI/UX
  2. DO NOT build in common, generic, or safe styles
  3. Push boundaries
  4. Always offer multiple premium design variations before writing the final code to the project
  5. Ensure all generated code is clean TypeScript, accessible, and responsive
  6. Treat all generated components as fully owned
  7. Use this skill only when the task clearly matches the scope described above
  8. Do not treat the output as a substitute for environment-specific validation, testing, or expert review
  9. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing

EXPECTED OUTPUT

Format
markdown
Constraints
  • offer multiple design variations before final code
  • use clean TypeScript
  • ensure accessibility and responsiveness

SUCCESS CRITERIA

  • Provide multiple design variations
  • Ensure target output aligns with project's stack
  • Define clear constraints for accessibility and responsiveness
  • Present options side-by-side highlighting differences
  • Integrate fully functional production-ready TypeScript code

CAVEATS

Dependencies
  • component description
  • project's stack
Missing context
  • Exact number of variations to generate
  • Target project tech stack details (beyond the examples given)
  • Preferred output format for presenting options and final code
Ambiguities
  • "several distinct" variations — exact count not specified
  • "Briefly describe" — no guidance on length or format of descriptions
  • "Interface with the Magic MCP server or use the browser_subagent" — unclear which method is preferred or how to choose

QUALITY

OVERALL
0.76
CLARITY
0.85
SPECIFICITY
0.78
REUSABILITY
0.72
COMPLETENESS
0.68

IMPROVEMENT SUGGESTIONS

  • Add explicit input placeholders such as {{component_description}} and {{project_stack}} at the top of the prompt
  • Specify a default number of variations (e.g., "Generate 3–5 variations")
  • Define a consistent output structure (e.g., numbered sections for analysis, variations, and integration)

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT