القائمة
Build a code-verified mental model of one feature or subsystem. Use before owning, debugging, changing, reviewing, or redesigning a complex area that needs a technical trace from entry point to data, jobs, providers, failures, and tests.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create a researched, durable, approval-gated goal contract whose verification tools, repository-vault authentication, exact proof steps, rollout safety, and evidence lifecycle are ready before execution. Use when the user asks to set, create, refine, save, or verify a goal; asks whether an agent has everything needed to prove completion; wants a proof-driven alternative to a raw `/goal`; or explicitly invokes `$verify-goal`.
Relentlessly interview the user in dependency-aware batches to sharpen a plan, decision, design, idea, codebase change, or bug fix. Use when the user wants to get grilled, investigate a bug from a ticket or screenshots, pass unfinished grilling to a teammate, or pick it up from a PR. Begin each session by choosing native dialogs or one full text batch, then Sideshow or experimental Grill Visuals for live diagrams. In repositories, inspect current behavior, run a mandatory gap and blast-radius pass, and maintain durable decision docs as answers settle.
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked via Task after a parent gathers diff and file contents. Loads the rubric from the `thermo-nuclear-code-quality-review` skill in the cursor-team-kit plugin.
Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach upstream. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
| name | feature-deep-dive |
| description | Build a code-verified mental model of one feature or subsystem. Use before owning, debugging, changing, reviewing, or redesigning a complex area that needs a technical trace from entry point to data, jobs, providers, failures, and tests. |
Build debug-grade understanding of one feature or subsystem. Do not change code unless the user asks.
One responsibility: make a developer understand one area well enough to debug/change it without guessing.
Choose one vertical slice or subsystem only: invite claim, promotion scheduling, content generation callback flow, search ranking, billing checkout, etc.
If the user needs the whole-system map first, use rebuild-mental-model. If this trace changes the global model, update or hand off to rebuild-mental-model.
Follow repo conventions first. If none exist, create/update:
docs/feature-deep-dives/<feature-slug>.mdCONTEXT.md if domain language changes and it exists; otherwise docs/ubiquitous-language.mdNever include secrets or env values. Provider/env var names are fine.
Mark claims explicitly:
verified - confirmed from code/config/schema/tests.partial - traced but not end-to-end.not verified - plausible or doc-derived only.drift - docs and code disagree.Never present intended future behavior as current code.
End every feature doc with:
## Quick Recall
- What this feature does:
- Main trigger:
- Source of truth:
- Top files/boundaries:
- Top tables/models:
- Providers:
- First debug checks:
- Biggest trap:
- Global architecture impact:
Before finishing:
None.