发现 devops architecture patterns 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
This skill should be used when the user asks to "organize MCP tools", "structure multi-tool MCP", "design MCP architecture", "group MCP tools", "organize 10+ tools", or discusses how to architect complex MCP se...
Transform ambiguous requirements into precise specifications. Use before any non-trivial implementation.
Design system architecture with components, data flow, and boundaries. Use for non-trivial features.
Performance guidelines and patterns for this system.
Map module dependencies and relationships. Use for complex codebases with non-trivial coupling.
Repo-wide rules, task workflow, and quality gates for this portfolio project. Use at the start of any task or when making cross-cutting decisions.
Authoritative guide on Next.js 16+ App Router structure. Use this skill to determine where files should be created, how to name them for routing, and how to organize project architecture.
Apply data-oriented architecture patterns when designing systems with polymorphic entities. This skill should be used PROACTIVELY when encountering switch statements or if/else chains that dispatch based on ent...
This skill should be used PROACTIVELY when writing, reviewing, or refactoring code. It provides SOLID principles, composition patterns, module organization, and side-effect boundary guidelines. Use when impleme...
Compound Engineering workflow for AI-assisted development. Use when planning features, executing work, reviewing code, or codifying learnings. Follows the Plan → Work → Review → Compound loop where each unit of...
This skill should be used when the user asks about Jira work items, sprints, boards, or projects. Activates when detecting: ticket IDs (PROJ-123), questions about "current sprint", "my tickets", "Jira issues",...
This skill should be used when the user mentions Confluence, references Confluence page URLs, asks to search for documentation, or needs to view Confluence content. Activates on keywords like "Confluence", "wik...
Analyzes and maps frontend API calls to backend endpoints. Detects missing endpoints, unused endpoints, and integration gaps. Optional: trace complete data flows to database and design tokens. Related: api-cont...
Docker orchestration and CI/CD for IntelliFill. Use when configuring containers, writing workflows, or setting up environments.
Integrate Sanity headless CMS for content management. Use when building content-driven sites with structured content, requiring an editor UI, or needing real-time previews.
Inline orchestration workflow for dependency audit and updates with Beads integration. Provides step-by-step phases for dependency-auditor detection, priority-based updates with dependency-updater, and verifica...
Inline orchestration workflow for code duplication detection and consolidation with Beads integration. Provides step-by-step phases for reuse-hunter detection, priority-based consolidation with reuse-fixer, and...
Inline orchestration workflow for dead code detection and removal with Beads integration. Provides step-by-step phases for dead-code-hunter detection, priority-based cleanup with dead-code-remover, and verifica...
Expert guidance on QuanuX frontend development, enforcing Backend-Driven UI architecture and high-performance React patterns.
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
REST/GraphQL API design patterns - resource naming, HTTP methods, error handling, pagination, versioning. Use when: design API, REST endpoints, GraphQL schema, error responses, pagination, rate limiting, API do...
Turn ideas into fully formed designs through collaborative dialogue. Use BEFORE any creative work - creating features, building components, adding functionality, or modifying behavior.
Guide til Event Sourcing arkitekturen. Bruk ved arbeid med events, state-projeksjoner, eller forretningsregler.
Authentication and authorization patterns using Clerk and RBAC
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。