gongyijie85

Use after completing any non-trivial task.

Use when the user asks to make something faster, try many variants, run recursive optimization, benchmark latency/throughput/cost, or…

Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs.

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins.

Use after benchmark-methodology has produced scored competitor profile cards.

Garbage collection for your Claude Code configuration.

Use when multiple consumers and providers must evolve an API or event schema without field drift, integration surprises, or one side…

Add one optional external Codex critique after the existing council has produced a decision draft.

Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state…

Use when large data ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, or table synchronization needs to become much…

Stop hook that blocks Claude from finishing until quality checks pass.

Simulate a collaborative dev team session where multiple role-based personas (PM, Architect, Developer, QA) respond to the same problem…