aiskillstore/marketplace / skills/aayushbaniya2006/ui-handler
ui-handler
VerifiedImplement UI using Shadcn MCP (atoms/theme) and 21st.dev MCP (complex sections). Use when adding buttons, layouts, or generating landing pages.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
| reference.md | markdown | 1.2 KB |
| skill-report.json | config | 16.4 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-09T12:40:53.619Z",
"slug": "aayushbaniya2006-ui-handler",
"source_url": "https://github.com/AayushBaniya2006/blinkfund/tree/main/.claude/skills/ui-handler",
"source_ref": "main",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "c9abd12e188d63c1a6b3217c5a6f24d905f13d7576d3bf3c9d48e6ee2a0b3f73",
"tree_hash": "1b88fc6c00e5cbbfb986fb0da321efbc12b7a6b8f21cfbc420e89ea09bca41a9",
"provenance": {
"model_requested": "gpt-5.5:high",
"model_effective": "codex:gpt-5.5:high",
"fallback_chain": [
{
"agent": "codex",
"model": "gpt-5.5",
"effort": "high",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "ui-handler",
"description": "Guides agents to build frontend UI with Shadcn MCP, 21st.dev MCP, Tailwind CSS, and project-specific component placement.",
"summary": "Build consistent frontend UI with Shadcn atoms, 21st.dev sections, and theme-aware project structure.",
"icon": "📦",
"version": "1.0.0",
"author": "AayushBaniya2006",
"license": "MIT",
"tags": [
"ui-components",
"shadcn-ui",
"tailwind-css",
"landing-pages",
"frontend"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"filesystem",
"external_commands"
],
"category": "design"
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "I confirmed one medium risk: SKILL.md line 16 recommends an unpinned pnpm dlx command that executes external package code. The other static alerts are markdown path, import, or class examples rather than executable shell use or path traversal. No prompt injection or malicious intent was found in SKILL.md or reference.md.",
"remediation": [
{
"issue": "Unpinned external package command in manual fallback",
"suggestion": "Pin the Shadcn CLI version and require explicit user confirmation before any pnpm dlx command runs.",
"severity": "medium"
},
{
"issue": "Ambiguous ellipsis in component path documentation",
"suggestion": "Replace src/app/.../_components/ with a clearer placeholder path such as src/app/[route]/_components/.",
"severity": "low"
}
],
"risk_factor_evidence": [
{
"factor": "filesystem",
"evidence": [
{
"file": "reference.md",
"line_start": 9,
"line_end": 9
}
]
},
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 16,
"line_end": 16
},
{
"file": "SKILL.md",
"line_start": 22,
"line_end": 22
},
{
"file": "SKILL.md",
"line_start": 23,
"line_end": 23
},
{
"file": "SKILL.md",
"line_start": 26,
"line_end": 26
},
{
"file": "SKILL.md",
"line_start": 29,
"line_end": 29
},
{
"file": "SKILL.md",
"line_start": 33,
"line_end": 33
},
{
"file": "SKILL.md",
"line_start": 34,
"line_end": 34
}
]
}
],
"static_findings": [
{
"id": "filesystem:reference.md:9:path-traversal-sequence",
"category": "filesystem",
"severity": "high",
"pattern": "Path traversal sequence",
"file": "reference.md",
"line_start": 9,
"line_end": 9,
"snippet": "| **Page Specific** | Custom | - | `src/app/.../_components/` |"
},
{
"id": "external_commands:SKILL.md:16:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 16,
"line_end": 16,
"snippet": "2. **Manual Fallback**: `pnpm dlx shadcn@latest add {component}`"
},
{
"id": "external_commands:SKILL.md:22:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 22,
"line_end": 22,
"snippet": "2. **Location**: Place generated files in `src/components/sections/` or `src/components/website/`."
},
{
"id": "external_commands:SKILL.md:23:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 23,
"line_end": 23,
"snippet": "3. **Integration**: Import and use in your `page.tsx`."
},
{
"id": "external_commands:SKILL.md:26:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 26,
"line_end": 26,
"snippet": "Use **Shadcn MCP** or edit `src/app/globals.css` directly."
},
{
"id": "external_commands:SKILL.md:29:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 29,
"line_end": 29,
"snippet": "- **CSS Variables**: We use CSS variables (often OKLCH) in `src/app/globals.css`. Ensure any new s"
},
{
"id": "external_commands:SKILL.md:33:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 33,
"line_end": 33,
"snippet": "2. **Compose**: Use atoms from `@/components/ui` and sections from `@/components/sections`."
},
{
"id": "external_commands:SKILL.md:34:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 34,
"line_end": 34,
"snippet": "3. **Co-location**: If a component is unique to a page, put it in `_components/` next to the page."
}
],
"finding_verdicts": [
{
"id": "filesystem:reference.md:9:path-traversal-sequence",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The text is a documentation placeholder path, src/app/.../_components/, not a traversal sequence used in a file operation. No ../ path access or filesystem read/write logic is present."
},
{
"id": "external_commands:SKILL.md:16:ruby-shell-backtick-execution",
"verdict": "confirmed",
"confidence": 0.88,
"severity": "medium",
"reason": "The line recommends pnpm dlx shadcn@latest add {component}, which runs external package code and uses an unpinned latest package. This creates a real supply-chain and command-execution risk during manual fallback use."
},
{
"id": "external_commands:SKILL.md:22:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.94,
"reason": "The backticked text is a destination folder path for generated components. It is not a shell command or dynamic execution pattern."
},
{
"id": "external_commands:SKILL.md:23:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "The text references page.tsx as an integration target inside markdown. It does not execute Ruby, shell, or any other command."
},
{
"id": "external_commands:SKILL.md:26:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.93,
"reason": "The backticked value is the CSS file path src/app/globals.css. The instruction is about editing a project stylesheet, not invoking a command interpreter."
},
{
"id": "external_commands:SKILL.md:29:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.94,
"reason": "The line contains inline examples of a CSS path and Tailwind class names. These are documentation examples and are not executable shell syntax."
},
{
"id": "external_commands:SKILL.md:33:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "The backticked strings are TypeScript import aliases for component folders. They are not commands and do not create an external execution path."
},
{
"id": "external_commands:SKILL.md:34:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "The text names a local folder convention for page-specific components. It is not shell execution and has no user-controlled command input."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [
{
"title": "Ruby/shell backtick execution",
"description": "2. **Manual Fallback**: `pnpm dlx shadcn@latest add {component}`",
"locations": [
{
"file": "SKILL.md",
"line_start": 16,
"line_end": 16
}
],
"review_kind": "capability",
"source_category": "external_commands",
"source_severity": "medium",
"confidence": 0.88,
"confidence_reasoning": "The line recommends pnpm dlx shadcn@latest add {component}, which runs external package code and uses an unpinned latest package. This creates a real supply-chain and command-execution risk during manual fallback use."
}
],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 2,
"total_lines": 65,
"audit_model": "codex",
"audited_at": "2026-07-09T12:40:53.619Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Build UI with Shadcn and 21st.dev",
"value_statement": "Frontend teams need consistent UI components and page sections. This skill guides Claude, Codex, and Claude Code to use Shadcn MCP and 21st.dev MCP.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"Shadcn MCP",
"21st.dev MCP",
"UI handler skill",
"frontend components",
"Tailwind CSS",
"landing page generation",
"Next.js UI"
],
"actual_capabilities": [
"Guides Shadcn MCP use for foundational UI atoms like buttons, inputs, and dialogs.",
"Uses 21st.dev Magic MCP for complex sections such as heroes, landing pages, and dashboards.",
"Defines preferred folders for UI atoms, sections, website components, and page-specific components.",
"Explains theme updates through Shadcn MCP or src/app/globals.css CSS variables.",
"Recommends Tailwind utility classes, responsive layouts, and semantic color tokens.",
"Provides a manual Shadcn CLI fallback for component installation."
],
"limitations": [
"Depends on Shadcn MCP and 21st.dev MCP being available in the agent environment.",
"The manual fallback uses pnpm dlx and should only run with user approval.",
"Does not verify third-party generated component quality by itself.",
"Does not replace accessibility, performance, or visual review."
],
"use_cases": [
{
"title": "Add Standard UI Controls",
"description": "Use Shadcn MCP to add buttons, inputs, and dialogs, then compose them in app layouts.",
"target_user": "Frontend developer"
},
{
"title": "Generate Landing Sections",
"description": "Create hero, footer, and dashboard sections with 21st.dev MCP for product pages.",
"target_user": "Product designer"
},
{
"title": "Apply Consistent Theme Rules",
"description": "Update theme variables and Tailwind classes so new screens match the existing design system.",
"target_user": "Full-stack engineer"
}
],
"prompt_templates": [
{
"title": "Add Basic Components",
"scenario": "Beginner setup for standard controls",
"prompt": "Use the ui-handler skill to add a button and dialog with Shadcn MCP for my Next.js page."
},
{
"title": "Create a Responsive Section",
"scenario": "Intermediate landing page work",
"prompt": "Use 21st.dev MCP to generate a responsive SaaS hero section. Place it in the sections folder and explain integration steps."
},
{
"title": "Update Theme Tokens",
"scenario": "Theme maintenance for an existing app",
"prompt": "Use the ui-handler skill to update the app theme with semantic colors, CSS variables, and Tailwind utilities."
},
{
"title": "Compose a Product Dashboard",
"scenario": "Advanced layout composition",
"prompt": "Use Shadcn atoms and 21st.dev sections to design a responsive dashboard with header, sidebar, content area, and empty states."
}
],
"output_examples": [
{
"input": "Add a landing page hero with an email capture form.",
"output": [
"Generated a responsive hero section plan with email capture and a clear call to action.",
"Placed shared section guidance in the correct component area.",
"Listed integration steps and noted that external commands need confirmation."
]
},
{
"input": "Update the app theme to use a neutral base and blue primary color.",
"output": [
"Reviewed the theme update path through Shadcn MCP or the global stylesheet.",
"Recommended semantic color tokens for light mode and dark mode.",
"Flagged hard-coded color choices that could break theme consistency."
]
},
{
"input": "Create a dashboard shell with navigation and content sections.",
"output": [
"Outlined a header, sidebar, and main content structure.",
"Recommended Shadcn atoms for controls and 21st.dev sections for larger blocks.",
"Defined where shared and page-specific components should live."
]
}
],
"best_practices": [
"Prefer MCP tools before writing custom components from scratch.",
"Place shared atoms and sections in the documented component folders.",
"Use semantic Tailwind tokens so dark mode remains consistent."
],
"anti_patterns": [
"Run pnpm dlx commands without user confirmation or version review.",
"Place one-off page components in global UI folders.",
"Hard-code colors that bypass theme variables."
],
"faq": [
{
"question": "What does this skill help with?",
"answer": "It helps agents build UI components, page sections, layouts, and theme updates with project conventions."
},
{
"question": "Which tools does it expect?",
"answer": "It expects Shadcn MCP for atoms and theme work, plus 21st.dev MCP for larger sections."
},
{
"question": "Can it work with Claude, Codex, and Claude Code?",
"answer": "Yes. The report lists Claude, Codex, and Claude Code as supported tools."
},
{
"question": "Does it require command execution?",
"answer": "Not always. The manual fallback includes a pnpm dlx command that should require user approval."
},
{
"question": "Can it update an existing theme?",
"answer": "Yes. It guides theme updates through Shadcn MCP or global CSS variables."
},
{
"question": "Does it replace design review?",
"answer": "No. Users should still review accessibility, responsiveness, visual quality, and dependency choices."
}
]
},
"file_structure": [
{
"name": "reference.md",
"type": "file",
"path": "reference.md",
"lines": 27
},
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 38
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |