vitest-testing
Write comprehensive Vitest tests for TypeScript and React. Use when creating unit tests, component tests, improving test coverage, or when user asks about testing patterns, mocking, or test utilities.
Skills correspondant au nom, à la description ou à l’auteur GitHub.
Write comprehensive Vitest tests for TypeScript and React. Use when creating unit tests, component tests, improving test coverage, or when user asks about testing patterns, mocking, or test utilities.
useCallback、useEffect の正しい使い方、無限ループ防止。Biomeチェック後の修正、Client Component作成時に使用。
Cria formulários com React Hook Form, validação Zod e shadcn/ui. Use quando precisar criar ou modificar formulários seguindo os padrões Bewear.
Realiza revisão de código completa seguindo as diretrizes Bewear, verificando padrões de arquitetura, TypeScript, React, Next.js, segurança e boas práticas. Use para revisar PRs ou código antes de merge.
Cria componentes React seguindo os padrões Bewear com shadcn/ui, TypeScript e Tailwind CSS. Use quando precisar criar novos componentes ou modificar componentes existentes.
Cria hooks React Query (queries e mutations) seguindo os padrões Bewear com invalidação de cache e integração com Server Actions.
Mobile Cross-Platform Agent. React Native/Flutter를 사용한 크로스플랫폼 앱 개발을 담당합니다.
컴포넌트 개발 에이전트. React/Next.js 컴포넌트를 설계하고 구현합니다.
Frontend TDD Agent. React/Next.js 기반 TDD 테스트 작성 및 구현을 담당합니다. 테스트 먼저 작성 후 구현하는 Red-Green-Refactor 사이클을 따릅니다.
커스텀 훅 개발 에이전트. React 커스텀 훅을 설계하고 구현합니다.
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, artifacts, posters, or applications (websites, landing pages, dashboards...
Ensure code follows DDD architecture and DAL separation for both frontend and backend. Triggers: DDD, arch, 架構, 新功能, 新模組, new feature, scaffold, 骨架, domain, layer, 分層, structure, 結構, backend, fron...
Best practices for building Panel visualization apps using param.Parameterized classes, reactive binding with pn.bind(), and URL state sync.
Use when building UI components, pages, or features - guides Claude through the approved frontend stack (Next.js 15, React 19, Shadcn, Tailwind) with design-first workflow for complex UIs, enforcing patterns an...
TDD方法論に従ってテストを作成します。テストファイルの配置(コロケーション)、命名規則、テスト構造のベストプラクティスに従います。React/TypeScript、Go、Rustで適切なパターンを使い分けます。「テストを書いて」「テ...
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Trigge...
Use when "LangChain", "LLM chains", "ReAct agents", "tool calling", or asking about "RAG pipelines", "conversation memory", "document QA", "agent tools", "LangSmith"
This skill should be used when the user asks about "React", "React components", "React hooks", "useState", "useEffect", "JSX", "React patterns", "React best practices", or mentions React development.
Use when "evaluating technology", "choosing frameworks", "stack comparison", "technology decisions", or asking about "React vs Vue", "PostgreSQL vs MySQL", "AWS vs GCP", "build vs buy"
Use when "building React artifacts", "creating HTML artifacts", "bundling React apps", "single HTML file", or asking about "artifact builder", "shadcn components", "Tailwind artifacts"
React development patterns and best practices including hooks, state management, and performance optimization.
Build accessible user interfaces using semantic HTML, proper ARIA attributes, keyboard navigation support, sufficient color contrast, and screen reader compatibility. Use this skill when creating or modifying U...
Implement comprehensive input validation with server-side validation (security), client-side validation (UX), fail-early patterns (KISS), specific error messages, allowlists over blocklists, and reusable valida...
Design and build reusable, composable UI components following Single Responsibility Principle with clear prop interfaces, minimal state, and proper encapsulation. Use this skill when creating or modifying React...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.