component-templates
UI component library templates (buttons, forms, cards, modals, etc.). Use when generating frontend UI components.
UI component library templates (buttons, forms, cards, modals, etc.). Use when generating frontend UI components.
Patterns for building React components with Radix UI, TailwindCSS, react-hook-form, and Framer Motion
Design-focused grid layout system with fluid scaling, responsive columns, and resolution-independent patterns. Use when creating page layouts, card grids, or multi-column designs.
Vue 3 coding guidelines and best practices with Dedsi UI components
This skill should be used when the user asks to "create a React component", "use React hooks", "handle state", "implement forms", "use useOptimistic", "use useActionState", "create Server Components", "add interactivity", or discusses React patterns, component architecture, or state management. Always use the latest React version and modern patterns.
HTML-first development with CSS-only interactivity patterns. Use when building features that work without JavaScript, using native HTML elements, CSS pseudo-classes, and the View Transitions API.
Develop Vue 3 components (.vue files) with Pinia state management and ECharts charts. Use when creating/modifying .vue components, configuring stores, integrating charts, debugging reactivity, handling Props/Emits, or optimizing performance. Keywords: Vue 3, Composition API, script setup, Pinia, ECharts, KpiCard, FilterPanel, Dashboard, computed, watch, responsive layout, eye-care colors.
React 19 and TypeScript coding standards for Portfolio Buddy 2. Use when: writing new components, reviewing code, refactoring, or ensuring consistency. Contains component patterns, TypeScript rules, and best practices.
Designs modern, clean iOS screens and components for Expo React Native apps following Apple HIG with safe areas, Dynamic Type, dark mode, accessibility, Liquid Glass materials, and App Store readiness.
UI 架构与组件开发规范。涵盖 shadcn/ui 集成、Tailwind CSS 使用、动画标准以及自定义组件原则。
Create a new React component following project conventions. Use when creating components, UI elements, or reusable modules.
State management with Zustand, Jotai, Context API. Use when implementing global state, stores, or state management patterns in React.
@ngrx/signals state management for Angular 20+ using pure reactive patterns with signalStore, rxMethod, and computed signals. Use when implementing reactive state, creating stores, managing async operations, or building signal-based architecture. Replaces traditional NgRx with simpler, more performant signal-based approach.
Handle errors consistently across frontend and backend. Use when implementing try/catch patterns, error boundaries, API error responses, or error reporting.
Create JavaScript handlers for pages. Use for DOM interactions and API calls.
Build features in TanStack Start (server/client boundaries, server functions, SSR-friendly data loading). Use when creating routes, server functions, or anything involving SSR/hydration/caching.
Verify accessibility (WCAG 2.1 Level AA) of React components. Use when creating UI components, forms, or when the user requests accessibility verification.
User feedback patterns for interactions - loading states, success/error messages, form validation, empty states. Ensures users understand system state and next steps. Use when implementing user-facing state changes and interactions: - Form submissions with validation feedback, success/error messages - Async operations needing loading indicators (API calls, data fetching) - Error handling flows with clear recovery paths and retry options - Empty state designs with helpful messaging (no data, no results) - User mentions "form", "loading", "error", "validation", "async", "API call" Keywords: loading, success, error, form, validation, async, feedback, toast, empty state Do NOT load for: - Visual design/styling (use frontend-design-fundamentals) - Responsive layout (use frontend-design-responsive) - Figma extraction (use frontend-design-figma-extraction) - Accessibility-only questions (use ux-accessibility) - Code quality checks (use quality-code-check) Focus on WHEN to show feedback, WHAT type (toast/inline/m
Use when writing or reviewing React useEffect, useState for derived values, data fetching, or synchronizing state with external systems.
Use when animating form fields, inputs, textareas, selects, or interactive form elements to improve usability and feedback
Material-UI integration for @react-typed-forms/core with FTextField and MUI schema renderers. Use when building React forms with Material-UI that need form state management integration.