frontend-patterns · rsmdt — Claude Code skill: features and installation
The frontend-patterns skill gives Claude Code task-specific guidance for React UI work with shadcn/ui and Tailwind CSS. Use it for component choices, theming, forms, and accessibility.
MIT ★ 587 updated 2026-10-26
/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startupWhat frontend-patterns does
The skill identifies which UI frameworks apply to the requested work, then retrieves their documentation. It turns that material into guidance on component APIs, theme customization, and built-in accessibility features. Recommendations are tied to the interface goal you provide.
Its references cover shadcn/ui and Tailwind CSS. The skill favors library components when they fit and checks documentation rather than guessing at component APIs. It needs to retrieve relevant reference material before giving guidance; without that, it cannot verify whether a component suits the task.
What it helps with
- choose library components for a UI
- configure theme tokens for a page
- plan accessible forms
- check component APIs against documentation
Example prompts for the agent
- Choose shadcn/ui components for the settings page and verify their APIs against the docs.
- Help me configure Tailwind CSS theming for this interface.
- Suggest accessible components for a registration form in my project.
How to install frontend-patterns
1Plugin marketplace
/plugin marketplace add rsmdt/the-startup/plugin install team@the-startupThis installs the whole team plugin with all its skills
2Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill frontend-patterns -a claude-code3Manually: put the files in place
~/.claude/skills/frontend-patterns/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/frontend-patterns/
1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill frontend-patterns -a codex2Manually: put the files in place
.agents/skills/frontend-patterns/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill frontend-patterns -a cursor2Manually: put the files in place
.cursor/skills/frontend-patterns/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rsmdt/the-startup plugins/team/skills/development/frontend-patterns2Manually: put the files in place
.github/skills/frontend-patterns/SKILL.md1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill frontend-patterns -a gemini-cli2Platform CLI
gemini skills install https://github.com/rsmdt/the-startup --path plugins/team/skills/development/frontend-patternsManually: put the files in place
.devin/skills/frontend-patterns/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about frontend-patterns
How do I install frontend-patterns in Claude Code?
Add the marketplace with /plugin marketplace add rsmdt/the-startup, then install the skill with /plugin install team@the-startup.
What does frontend-patterns do?
It identifies relevant UI frameworks, retrieves their documentation, and gives task-specific guidance on components, theming, and accessibility.
Why does the skill identify frameworks before making recommendations?
That lets it retrieve documentation for the technologies relevant to the UI task. It avoids guessing component APIs without checking their docs.
Source text
SKILL.md · MIT
---
name: frontend-patterns
description: Context enrichment for frontend UI development using shadcn/ui and Tailwind CSS. Use when building component libraries, implementing UI designs, theming, or working with accessible React components.
---
## Persona
Act as a frontend UI specialist who enriches implementation context with current component library documentation and design system patterns.
**UI Target**: $ARGUMENTS
## Interface
FrontendContext {
frameworks: string[]
concern: COMPONENTS | THEMING | LAYOUT | FORMS | DATA_DISPLAY | ACCESSIBILITY
}
State {
target = $ARGUMENTS
detectedFrameworks = []
}
## Constraints
**Always:**
- Detect which UI frameworks are in use before fetching documentation.
- Recommend component composition over custom implementations when available.
**Never:**
- Assume component APIs without consulting current documentation.
- Recommend custom components when a library component exists for the use case.
## References
- [shadcn/ui](https://ui.shadcn.com/llms.txt) — Accessible React components, theming, form handling, CLI tooling, Radix UI primitives
- [Tailwind CSS](https://tailwindcss.com/docs) — Utility-first CSS, responsive design, custom configuration, dark mode (no llms.txt available)
## Workflow
### 1. Detect Framework Need
Identify which frameworks are relevant from the UI target. Fetch the corresponding reference documentation.
### 2. Synthesize Context
Combine fetched documentation into actionable guidance:
- Available components and their APIs for the target use case.
- Theming tokens and customization approach.
- Accessibility features built into components.
### 3. Deliver Enriched Context
Provide framework-specific guidance integrated with the UI target.
© Rudolf S. · MIT · rsmdt/the-startup
Similar skills
All skills for Frontend and UI →frontend-patterns by other authors comes first.