Marketplace ui-handler
Implement UI using Shadcn MCP (atoms/theme) and 21st.dev MCP (complex sections). Use when adding buttons, layouts, or generating landing pages.
install
source · Clone the upstream repo
git clone https://github.com/aiskillstore/marketplace
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aiskillstore/marketplace "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/aayushbaniya2006/ui-handler" ~/.claude/skills/aiskillstore-marketplace-ui-handler && rm -rf "$T"
manifest:
skills/aayushbaniya2006/ui-handler/SKILL.mdsource content
UI Handler
Instructions
1. Installing Standard Components (Atoms)
Use the Shadcn MCP for foundational UI elements (buttons, inputs, dialogs).
- Action: Ask the Shadcn MCP to add the component.
"Add the button and dialog components using Shadcn MCP."
- Manual Fallback:
pnpm dlx shadcn@latest add {component}
2. Generating Complex Sections (Blocks)
Use the 21st.dev Magic MCP for high-level sections (Landing pages, Heros, Dashboards).
- Action: Prompt the 21st.dev MCP with a description.
"Generate a modern SaaS hero section with a dark gradient background and email capture form."
- Location: Place generated files in
orsrc/components/sections/
.src/components/website/ - Integration: Import and use in your
.page.tsx
3. Theming & Styling
Use Shadcn MCP or edit
src/app/globals.css directly.
- Theme Updates: Ask Shadcn MCP to apply a specific theme or color palette.
"Update the app theme to use a 'zinc' neutral base with 'blue' primary color."
- CSS Variables: We use CSS variables (often OKLCH) in
. Ensure any new styles use these variables (e.g.,src/app/globals.css
,bg-background
).text-primary
4. Creating Layouts
- Identify: Header, Sidebar, Content Area.
- Compose: Use atoms from
and sections from@/components/ui
.@/components/sections - Co-location: If a component is unique to a page, put it in
next to the page._components/
Reference
For detailed architecture and best practices, see reference.md.