Loading...
Loading...
Found 261 Skills
用于使用 ArkTS 开发 OpenHarmony UI 时 - 查找布局、组件、状态管理、动画、导航,或处理缺少装饰器、状态不更新、渲染问题等错误
Complete guide for Axum web framework including routing, extractors, middleware, state management, error handling, and production deployment
Provides comprehensive guidance for Terraform infrastructure as code including resource definition, state management, modules, and cloud provider integration. Use when the user asks about Terraform, needs to define infrastructure as code, manage cloud resources, or work with Terraform modules.
MANDATORY for creating Zustand stores. This skill is required when users request state management, creating stores, or mention Zustand. Do NOT create Zustand stores without this skill - all stores must use the required StoreBuilder pattern with immer middleware and factory pattern separation
Apply react-use hooks where appropriate to build concise, maintainable React features.
Server-driven architecture patterns for Inertia Rails + React. Load this FIRST when building any Inertia page or feature — it routes to the right skill. Decision matrix for data loading, forms, navigation, state management. NEVER useEffect+fetch, NEVER redirect_to for external URLs (use inertia_location), NEVER react-hook-form (use Form component). MUST invoke when adding pages, models with views, CRUD, or displaying data in an Inertia Rails app. ALWAYS `render inertia: { key: value }` to pass data — `@ivars` are NOT auto-passed as props.
Skill for implementing actual UI and integrating with APIs. Covers frontend-backend integration, state management, and API client architecture. Use proactively when user needs to connect frontend with backend APIs. Triggers: UI implementation, API integration, state management, UI 구현, API連携, 状态管理, implementación UI, integración API, gestión de estado, implémentation UI, intégration API, gestion d'état, UI-Implementierung, API-Integration, Zustandsverwaltung, implementazione UI, integrazione API, gestione dello stato Do NOT use for: mockup creation, backend-only development, or design system setup.
Specifies best practices and conventions for Expo-based mobile app development.
Real-time ECS state management for TypeScript and React. Use when the user mentions koota, ECS, entities, traits, queries, or building data-oriented applications.
Write React components with minimal state, proper memoization, and type-safe patterns. Use when creating components, managing state, or optimizing renders.
Apply Vue-3-style runtime best practices for wevu in mini-programs. Use when implementing pages/components/stores with wevu, defining lifecycle hooks, handling setData diff behavior, designing props/emit and bindModel flows, integrating with weapp-vite SFC JSON macros, or troubleshooting compatibility differences versus Vue 3.
Complete Development Guide for Tables, Search, and Pagination Features in React/Next.js Projects. Covers core technologies such as race condition handling, search system implementation, pagination systems, infinite scrolling, CRUD synchronization, Intersection Observer API, and state management selection. Key Features: - Handle race condition issues in asynchronous requests - Implement high-performance search and autocomplete features - Build professional-grade pagination systems and caching strategies - Develop smooth infinite scrolling experiences - Ensure data consistency for CRUD operations - Select the most suitable state management solution Applicable Scenarios: - React/Next.js applications requiring search and pagination features - List display and CRUD operations for large datasets - Need for high-performance infinite scrolling or virtualized lists - Facing complex data management issues such as race conditions and state synchronization - Projects needing to select an appropriate state management solution