frontend-architecture-patterns
Frontend architecture patterns for React apps (React Router 7, TanStack Query). Use when planning features, defining routes, data strategies, and component gaps.
发现 databases architecture patterns 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Frontend architecture patterns for React apps (React Router 7, TanStack Query). Use when planning features, defining routes, data strategies, and component gaps.
Best practices for frontend architecture. Use when planning new features, defining routes, or designing data strategies.
User story writing patterns with comprehensive acceptance criteria categories and quality standards. Use when creating user stories, defining acceptance criteria, or reviewing story completeness for multi-tenan...
Automated feedback collection and learning documentation. Captures learnings from issues, generates ADRs for architecture decisions, and prompts for retrospective insights.
Use when context is growing large, switching tasks, or needing previous session context - covers thresholds, session tools, and workflow patterns
Multi-agent task coordination using Beads Village plugin tools. Use when work spans multiple sessions, has dependencies, needs file locking, or requires agent coordination. Covers claim/reserve/done cycle, depe...
Use this skill when working on rpg-api codebase - provides layered architecture patterns, outside-in development, and integration with rpg-toolkit
Swift 6 strict concurrency model, async/await, actors, @MainActor, Sendable, and thread safety. Use when user asks about concurrency, async/await, actors, MainActor, thread safety, data races, or migrating from...
Rust製非同期Docker APIクライアント「Bollard」の使い方と実装パターン
Analyzes CI/CD pipelines to identify common antipatterns (like slow feedback loops or sequential steps) and recommends best practice patterns (like build images, parallelization, and build-once-deploy-anywhere)...
Container and infrastructure patterns for Go applications. Use when working with Dockerfiles, external binaries, or deployment configuration. Triggers: containerization, external binary integration, dependency...
Go library development patterns. Use when designing library APIs, implementing extensibility, or working on packages in pkg/ directories. Triggers: format extensibility, provider separation, capability composit...
Implement CQRS (Command Query Responsibility Segregation) pattern for Electron services. Use when creating service methods, separating read/write operations, or implementing reactive data streams with Observabl...
Advanced patterns for Hono-based Electron IPC including CQRS, Zod validation, error handling, and reactive data with RxJS. Use when implementing complex IPC patterns or needing guidance on architecture decision...
Rapidly build and launch micro-SaaS applications with best practices, monetization, and deployment
Use when writing async/await code, enabling strict concurrency, fixing Sendable errors, migrating from completion handlers, managing shared state with actors, or using Task/TaskGroup for concurrency.
Reference and adhere to the project's technical stack including frameworks, languages, tools, and dependencies. Use this skill when choosing libraries, frameworks, or tools for implementing features. Use this s...
Implement robust error handling strategies with user-friendly messages and graceful failure patterns. Use this skill when catching and handling exceptions or errors in any code. Use this skill when validating i...
Follow general development conventions for project organization, documentation, version control, and team collaboration. Use this skill when organizing project files and directory structures. Use this skill whe...
Workflow-first design through collaborative dialogue. Use before creating features, building components, or modifying behavior.
Expert assistant for Kumo's Query Module (src/features/query). Use when working with SQL Editor, Monaco editor integration, query execution, result grids, tabs management, AI features, or any query-related comp...
Reference catalog of recurring SAE feature patterns - check when labeling new features, add new patterns as discovered
Use ALWAYS. Core development rules for production-ready code - guard clauses, no shortcuts, no mocking.
Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decis...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。