Three complementary Agent Skills for TypeScript, React, and Tailwind frontend
work. Use oh-my-frontend as the lightweight triage entry for frontend tasks,
frontend-engineering for implementation rules, and
tailwind-classname-categorization for related work on long, multi-concern
Tailwind className values when an existing compatible helper can group them.
Each skill has a short SKILL.md; detailed guidance is loaded from references
only when needed.
| Skill | Use it for |
|---|---|
| frontend-engineering | Standalone readable, explicit TypeScript and React implementation rules |
| oh-my-frontend | Frontend triage and risk-based orchestration layer |
| tailwind-classname-categorization | Semantic grouping of long Tailwind className values through existing helpers |
frontend-engineering — Code principles and implementation quality
Standalone TypeScript and React implementation rules for readable, explicit, and predictable frontend code. No Planner, `/docs`, approval interview, or parallel agent is required.- TypeScript contracts, narrowing, and data boundaries
- React rendering, components, hooks, context, and state ownership
- Forms, errors, async resilience, and URL state
- Testing, accessibility, security, modules, naming, and file structure
Start with SKILL.md.
oh-my-frontend — Documentation, approval, and agent orchestration
Frontend task triage and risk-based orchestration for project memory, approval, parallel work, specialist review, and verification. It may enter any frontend task, exits clear mechanical work at Level 0, and adds workflow only when the changed risk requires it. It does not replace `frontend-engineering` implementation rules.- Repository-canonical project memory: domain language, business rules, features, decisions, and architecture; recommend a minimal structure only when no durable convention exists
- Batched blocking questions, focused approval, bounded Worker briefs, and safe parallel lanes
- Component architecture, UI state, browser/visual verification, accessibility, and debugging
- Data fetching, routing, performance, security, responsive UI, forms, i18n, compatibility, and observability routing
- Risk-based testing without mandatory TDD or excessive test code
Start with SKILL.md.
tailwind-classname-categorization — Tailwind className readability
Groups long, multi-concern Tailwind `className` values through an existing compatible classname helper. It preserves dynamic values and conflict-sensitive order; it does not sort canonical class order, format line breaks, or implement a helper.- Tailwind utility categories and variant buckets
- Tailwind v3/v4 prefix, separator, and important syntax
- State, responsive, arbitrary, and container-query variants
- Safe handling of helper and
cva()structures
Start with SKILL.md.
Install all skills:
npx skills add fe-dudu/skillsInstall one skill:
npx skills add fe-dudu/skills --skill frontend-engineering
# or: npx skills add fe-dudu/skills --skill oh-my-frontend
# or: npx skills add fe-dudu/skills --skill tailwind-classname-categorizationUse multiple skills when the task spans their scopes:
npx skills add fe-dudu/skills --skill frontend-engineering
npx skills add fe-dudu/skills --skill oh-my-frontend
npx skills add fe-dudu/skills --skill tailwind-classname-categorizationInstall through the Claude Code plugin CLI:
claude plugin marketplace add fe-dudu/skills
claude plugin install frontend-engineering@fe-dudu
claude plugin install oh-my-frontend@fe-dudu
claude plugin install tailwind-classname-categorization@fe-duduOr run the plugin commands inside Claude Code:
/plugin marketplace add fe-dudu/skills
/plugin install frontend-engineering@fe-dudu
/plugin install oh-my-frontend@fe-dudu
/plugin install tailwind-classname-categorization@fe-dudu
The repository also includes the Claude marketplace catalog at
.claude-plugin/marketplace.json.