Collection · 13 skills
Modern Frontend Stack
Everything a React and Next.js codebase needs, in the order problems tend to appear: component patterns and server boundaries first, then styling, forms and state, then the accessibility and performance work that separates a demo from a product.
Best for Teams building with React, Next.js and Tailwind CSS.
What's inside
Listed in the order we suggest adopting them. You don't call them by name: each skill loads on its own when a request matches it.
- React Patterns Fewer effects, derived state, components that compose
- Next.js App Router Layouts, caching and invalidation that behave in prod
- React Server Components Keep data on the server and props serializable
- Tailwind CSS v4 Tokens in @theme, complete class names, no @apply sprawl
- State Management One owner per value: URL, cache, store or component
- Forms and Validation One schema, server-checked, errors a screen reader hears
- Accessibility Audit WCAG 2.2 AA findings you can hand to engineers
- Core Web Vitals Fix the sub-part that is actually slow
- React Re-renders Profile first, memoize last
- Playwright E2E End-to-end tests that never need a sleep
- Testing Library Component tests that query like a screen reader
- Virtualized Lists Thousands of rows, a few dozen DOM nodes
- Drag and Drop Drag as a shortcut, with a click path behind it
Keep exploring
Other collections
- 10 skills The Starter Pack Ten skills that improve almost every session
- 11 skills Claude Code Power User Teach the agent to configure and extend itself
- 13 skills Production Backend APIs, data and jobs that survive real traffic
- 10 skills Ship to Production From Dockerfile to pager without the drama
- 12 skills Security Review Kit A defensive review your security team would sign
- 12 skills AI Engineering LLM features that are measured, cheap and safe