nbl-superpowers

Use when executing implementation plans with independent tasks in the current session

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when you have a spec or requirements for a multi-step task, before touching code

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when deploying guozhi-series services to dev environments. Triggers on "部署", "发布", "deploy", "发布到dev", "上线". Automates git commit/push, parallel jkd+jku, BFF passthrough check, and BFF deployment.

Java Web 死代码清理和重构专家。安全识别并移除死代码，每一步都进行测试验证。 触发条件：用户请求清理死代码、重构优化、移除未使用代码。

一键安装自定义状态行脚本到 ~/.claude，显示模型、Git状态、上下文使用率、成本和worktree信息

Use when executing implementation plans with parallelizable tasks - analyzes dependencies, groups by level, executes independent tasks concurrently

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when writing Java Spring Boot integration tests that perform real database CRUD operations with MockMvc and MyBatis-Plus

管理 rules/common/ 目录下规则文件的编辑，确保版本追踪和依赖一致性。 触发条件：用户请求修改规则、修改编码规范。

Use after any code review, error correction, or convention violation to capture the lesson as a persistent rule. Triggers when the user invokes /evolve, or when they express intent like "we should remember this", "make sure this doesn't happen again", "add a rule for this", or "let's note this down". Also use when a recurring mistake pattern emerges across the conversation.

从 GitHub 仓库安装最新规则文件到本地 ~/.claude/rules/ 目录。 触发条件：用户请求安装规则、从远程更新本地规则。

测试覆盖率分析，识别缺口，生成缺失的测试以达到80%+覆盖率。 触发条件：用户请求测试覆盖率分析、提升测试覆盖率、编写测试。

Use when implementing any feature or bugfix, before writing implementation code

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.

根据需求描述生成技术设计文档。包含需求背景、架构设计、技术设计、API设计、模型设计等章节。 触发条件：用户请求技术方案、技术设计文档、API设计、数据库设计等。