Magic Ui Generator

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.