Desenvolvimento

NestJS TypeScript backend development with enterprise patterns, dependency injection, modular architecture, and comprehensive testing support. Use when: (1) Project has @nestjs/core in package.json or nest-cli.json exists, (2) Creating modules, controllers, services, guards, pipes, interceptors, or filters, (3) Implementing JWT authentication or role-based authorization (RBAC/ABAC), (4) Integratin

Use this skill whenever the user installs, configures, or debugs Google Analytics 4, or mentions gtag.js, GTM, conversion tracking, e-commerce events, or a cookie/consent banner tied to analytics. Covers installation, event tracking, user properties, e-commerce, Consent Mode v2 for EU/UK visitors, SPA pageview tracking, and BigQuery export. Skip for other analytics products (Plausible, Mixpanel, P

Performance optimization strategies and techniques

Sonnet-first quality playbook: through context engineering, sub-agent delegation, and forced self-review loops, get Sonnet 4.6 to produce code/doc quality on par with Opus 4.7. Escalate to Opus only when quantitative gates trigger. Triggers: "sonnet", "Sonnet", "Sonnet mode", "sonnet-pilot". Do NOT use for: pure cost optimization, file-count cognitive heuristic, agent dispatch table, CLAUDE.md / r

Export the current Strudel code with header comments

Post-challenge debrief — generates writeup with structured failure analysis. Outputs to writeup/ directory and updates MEMORY.md with key lessons.

Assists in the creation of a headless Claude Code batch script that runs an isolated micro-session per item (file, line, task) for ad-hoc automation such as bulk migrations, lint-fix loops, or doc generation.

Part of the quantum-loop autonomous development pipeline (brainstorm \u2192 spec \u2192 plan \u2192 execute \u2192 review \u2192 verify). Two-stage code review. Spec compliance first, then code quality. Use after implementation or before merge. Triggers on: review code, code review, check implementation, ql-review.

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when the user needs to: (1) Simplify complex code, (2) Improve code readability, (3) Refactor for maintainability, (4) Apply coding standards, (5) Review and optimize code structure. Triggers on phrases like \"简化代码\", \"优化代码\", \"重构代码\", \"提升可读性\", \"代码审查\", \"simplify code\", \"refact

Create an initial Claude Code setup for a brownfield project with a single-application topology (no sub-projects or monorepo structure).

Post-review AI-slop cleanup pass. After quality review approves a story/feature, scans only the changed files for: duplicate code, dead code, needless abstraction, boundary violations, missing tests. Proposes deletions with regression-test gate — rolls back on regression. Mandatory unless explicitly skipped via --no-deslop. Borrowed from OMC Ralph 7.5 + 7.6.

系統化的問題分析專家技能，自動協調五個專門代理進行深度問題分析。 適用於： - 使用者或 PM 報告的線上問題 - 開發團隊反映的技術問題 - 測試發現的 bug - 生產環境告警和異常