WodenWang820118

Pre-flight checklist that every primary agent runs before opening the pre-implementation gate. Confirms task size, primary AI family, cross-family reviewer routing, grill-me requirement, and the exact `pnpm review:approve-pre-implementation` flags to use.

Discovers and invokes the repo-local skill set. Use when starting work or when you need to choose the right workflow for the current task.

Repo-specific Angular conventions and patterns for law-prep-web. Load when working with Angular components, services, DI, signals, routing, or tests.

Repo-local overlay of the cross-family grill-me skill. Stress-test a plan or design through one-question-at-a-time interviews, with a 6-item completion checklist required before Plan Review for medium+ or sensitive tasks.

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Capture browser-based proof artifacts for ng-frontend. Use when the user asks for proofshot, visual proof, screenshots, video proof, browser proof, or when a UI change would benefit from human-reviewable artifacts.

Discovers and invokes the repo-local skill set. Use when starting work or when you need to choose the right workflow for the current task.

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

Runs a conditional behavior-preserving refactor checkpoint. Use after a verifiable implementation slice creates large-file pressure, semantic duplication, mixed responsibility, hard-to-test logic, or current-change orphan code. Use before feature implementation only when an approved plan says a preparatory refactor is needed.

Verifies implemented behavior with evidence. Use after implementation to gather proof, reproduce user flows, and decide whether the session is report-only or fix-enabled. Browser-visible work uses interactive verification paths; backend and Tauri-runtime work use smoke checks, task commands, and structured findings.

Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI monitoring — it integrates with Nx Cloud self-healing which those tools cannot access.