Loading...
Loading...
Found 2,225 Skills
Phase 3 of the feature workflow – Complete the acceptance closed loop. Two tasks: First, check layer by layer against {slug}-design.md to verify if the implementation deviates from the plan; if deviations are found, fix them immediately instead of just "noting them down" in the report. Second, integrate this feature into the project's overall architecture documentation. Finally, produce a {slug}-acceptance.md as the closed-loop proof for the entire workflow. Predecessor dependency easysdd-feature-implement must be completed. Trigger scenarios: User says "The feature is done, let's accept it", "Do the final check", "Prepare for merge", "Generate the acceptance report".
Grafana Mimir scalable long-term metrics storage. Covers architecture (distributor/ingester/compactor/querier/ query-frontend/store-gateway/ruler), deployment modes (monolithic/microservices), configuration, Prometheus remote write, PromQL querying, multi-tenancy, compaction, and operations. Use when working with Mimir for metrics storage, scaling Prometheus, configuring Mimir clusters, writing PromQL, or debugging Mimir.
Audit a codebase for maintenance and modernization. Challenges scope, reviews architecture/quality/tests/performance/dependencies, files deferred work via bd. Language-specific addendums for iOS/Swift, Go, and Web/JS/CSS activate automatically based on what's in the repo. Supports monorepos with mixed stacks.
Decision Coaching for Vue Component/Composable Refactoring — Users paste a piece of code or point to an SFC, and the skill first performs a diagnosis ("Fat Trunk" / "UI & IO Entanglement" / "Reactivity & Business Logic Entanglement"), then selects one from three recipes, and provides a specific sequence of extraction steps (which variable to move first, what errors the compiler will throw, how to fix them one by one, when rollback is possible). The entire process ensures behavioral equivalence through compiler green lights + step-by-step rollback, without relying on test safeguards. Trigger scenarios: Users say "This Vue component is too fat / I want to extract the logic / Split this SFC / This composable is too messy / Extract a composable / Split into humble / Pure functionalize", or point to an obviously overlong .vue / composable file and request "Refactor / Optimize / Split". Only handles Vue (Vue 2 Options, Vue 2/3 `<script setup>`, composable, pinia store). Does not handle: Adding new features (follow feature process), fixing bugs (follow issue process), cross-module architecture restructuring, backend code.
ReactLynx best practices covering dual-thread architecture and React patterns. Provides rules reference for writing, static analysis for reviewing, and auto-fix for refactoring.
Find composition and state-lifting refactor opportunities in a React codebase. Audits for boolean-prop bloat, monolith components with variant explosion, sibling clusters that should share lego-brick subcomponents, render-prop slots that can't reach outside the box, and state synced between siblings via useEffect. Use when the user wants to improve react code, audit react components, find react refactor opportunities, run a react composition review, or asks "improve react", "audit react", "react architecture review".
Research GitHub, GitLab, and Bitbucket repositories using DeepWiki MCP server. Use when exploring unfamiliar codebases, understanding project architecture, or asking questions about how a specific open-source project works. Provides AI-powered repo analysis and RAG-based Q&A about source code. NOT for fetching library API docs (use fetching-library-docs instead) or local files.
Connects an AWS Lambda function to DynamoDB with IAM roles, stream event source mapping, and read/write permissions. Use when setting up Lambda-DynamoDB integration, processing DynamoDB stream events, or deploying serverless event-driven architectures.
Generate a SYSTEM_OVERVIEW.md that orients a senior engineer new to an unfamiliar codebase, with a Mermaid architecture diagram, a sequence diagram for data flow, and a legacy-pattern assessment. Use when user says 'give me a system overview', 'onboard me on this repo', 'walk me into this legacy codebase', 'document the high-level architecture', or 'create a SYSTEM_OVERVIEW.md'. Do NOT use for code walkthroughs (use explain), persistent architecture chapters (use arc42), or ADRs (use document-decision).
Create diagrams and visualizations in Markdown using Mermaid, Graphviz, Vega-Lite, PlantUML, infographics, JSON Canvas, architecture diagrams, and info cards. Use when asked to create any diagram, chart, visualization, or visual documentation.
High availability and disaster-recovery best practices for Azure DocumentDB — enabling in-region HA (99.99% SLA) and adding active-passive cross-region replica clusters (99.995% SLA). Use when designing production topology, planning failover, provisioning DR, or reviewing cluster architecture.
Publish Rust binaries to npm using the optionalDependencies platform package pattern. Covers the full publish pipeline, version sync, workspace:* protocol, and platform package architecture. Use when: (1) publishing Rust binaries to npm, (2) setting up the platform package pattern (main + per-OS packages), (3) debugging publish failures, (4) managing version sync across pnpm + Cargo workspaces, (5) working with workspace:* protocol. Triggers on "publish", "platform packages", "optionalDependencies", "bin.js", "version sync", "workspace protocol", "npm tag", or "prepare-publish".