Proves
Proves unitàries, d’integració i automatitzades
chargebee-integration
chargebee
Comprehensive integration guide for Chargebee billing platform. Provides API integration patterns, webhook handling, SDK usage, and schema references for billing operations. Use when working with Chargebee for (1) API integration and REST endpoint calls, (2) Processing webhook events, (3) Customer management operations, (4) Subscription lifecycle handling, (5) Payment and invoice processing, (6) Any other billing-related integration tasks with Chargebee platform.
barrel-export
forge-town
支持自动生成/优化/修复/检查 index 文件，确保所有 index 文件（index.ts / index.js）都遵循桶导出规范。核心原则：所有 index 文件都必须遵循桶导出规范。
refactoring
cosmix
Restructures existing code to improve readability, maintainability, and performance without changing external behavior. USE WHEN: Restructuring code without changing behavior, extracting methods/classes, removing duplication, applying design patterns, improving code organization, reducing technical debt. DO NOT USE: For bug fixes (use /debugging), for adding tests (use /testing), for new features (implement directly). TRIGGERS: refactor, restructure, rewrite, clean up, simplify, extract, inline, rename, move, split, merge, decompose, modularize, decouple, technical debt, code smell, DRY, SOLID, improve code, modernize, reorganize.
istio
cosmix
Service mesh implementation with Istio for microservices traffic management, security, and observability. Use when implementing service mesh, mTLS, traffic routing, load balancing, circuit breakers, retries, timeouts, canary deployments, A/B testing, or service-to-service communication. Triggers: istio, service mesh, envoy, sidecar, virtualservice, destinationrule, gateway, mtls, peerauthentication, authorizationpolicy, serviceentry, traffic management, traffic splitting, canary, blue-green, circuit breaker, retry, timeout, load balancing, ingress, egress, observability, tracing, telemetry.
project-conventions
ReinaMacCredy
Discovers host project conventions from CLAUDE.md, package.json, linter configs, and other configuration files. Use when agents need to understand the target project's coding standards.
tdd
xopcai
Test-driven development using a red-green-refactor loop for features, bug fixes, and integration tests.
diagnose
xopcai
Disciplined reproduce → minimise → hypothesise → instrument → fix loop for hard bugs and performance regressions.
auth0-nextjs
auth0
Use when adding authentication to Next.js applications with both server and client-side auth - supports App Router and Pages Router with @auth0/nextjs-auth0 SDK
auth0-vue
auth0
Use when adding authentication to Vue.js 3 applications (login, logout, user sessions, protected routes) - integrates @auth0/auth0-vue SDK for SPAs with Vite or Vue CLI
auth0-angular
auth0
Use when adding authentication to Angular applications with route guards and HTTP interceptors - integrates @auth0/auth0-angular SDK for SPAs
auth0-react
auth0
Use when adding authentication to React applications (login, logout, user sessions, protected routes) - integrates @auth0/auth0-react SDK for SPAs with Vite or Create React App
testing-e2e
alexei-led
E2E testing with Playwright MCP for browser automation, test generation, and UI testing. Use when discussing E2E tests, Playwright, browser testing, UI automation, visual testing, or accessibility testing. Supports TypeScript tests and Go/HTMX web applications.
feature-dev
sd0xdev
"Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate."
chat-x-custom-component
TencentBlueKing
帮助开发者创建 @blueking/chat-x 自定义 message 组件。当用户需要开发自定义消息类型时使用。
feasibility-study
sd0xdev
"Feasibility analysis from first principles. Use when: evaluating solutions before tech-spec, comparing approaches, risk assessment. Not for: implementation (use feature-dev), architecture advice (use codex-architect). Output: quantitative comparison + recommendation."
chat-x-unit-test
TencentBlueKing
帮助开发者为 Vue 3 组件编写单元测试。当用户需要添加单元测试时使用。
request-tracking
sd0xdev
"Request tracking knowledge base. Use when: querying request status, managing document references, tracking progress. Not for: creating requests (use create-request), tech specs (use tech-spec). Output: status report + progress tracking."
doc-review
sd0xdev
"Document review via Codex MCP. Use when: reviewing .md docs, tech spec audit, document quality check. Not for: code review (use codex-code-review), test review (use test-review). Output: 5-dimension rating table + gate."
repo-intake
sd0xdev
"Project initialization inventory (one-time). Use when: first onboarding a project, rebuilding cache after structural changes. Not for: day-to-day development (read cache directly), finding specific files (use code-explore). Output: project map with entrypoints + test map + next steps."
portfolio
sd0xdev
"Portfolio system knowledge base. Use when: position queries, routing strategy questions, provider integration. Not for: general code exploration (use code-explore), code review (use codex-code-review). Output: domain-specific analysis + recommendations."
bug-fix
sd0xdev
"Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate."
create-request
sd0xdev
"Create or update request documents. Use when: planning features, tracking requests, updating progress. Not for: tech specs (use tech-spec), code implementation (use feature-dev). Output: request document with status tracking."
codex-implement
sd0xdev
"Implement features via Codex MCP. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop."
Vue 3 组件单元测试指南 (Vitest)
TencentBlueKing
使用 Vitest 和 Vue Test Utils 的标准模版与断言技巧