tag-check

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.

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.

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.

Repo-specific Python/FastAPI conventions for law-prep-ai-service. Load when working with Python services, FastAPI routers, Pydantic models, or Poetry dependencies.

Repo-specific NestJS conventions. Load when working with NestJS controllers, providers, modules, or DTOs in the monorepo.

⚠️ MERGED into nx-workspace. Load `nx-workspace` instead for both exploration and task execution.

Explore Nx workspaces and run tasks. USE WHEN answering questions about the workspace, projects, or targets; running build, test, lint, serve, or any Nx task; debugging Nx command failures. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'run tests for project X', 'Cannot find configuration for task'.

Repo-specific Java/Spring Boot conventions for law-prep-engine. Load when working with Java services, controllers, DTOs, repositories, or Spring configuration.

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Turns review findings into the smallest safe remediation plan. Use when plan, test, or implementation review returns actionable comments and you need to respond without widening scope.

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

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.

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 because it integrates with Nx Cloud self-healing which those tools cannot access.

Reframes solution-framed requests into product-aware planning inputs. Use when the user presents a feature idea, the real problem is fuzzy, or scope/ambition needs to be deliberately held, expanded, or reduced before drafting the spec.

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 repos can route through proofshot; non-browser repos should use smoke checks, tests, and structured findings.

Prepares an implementation for handoff or release without pushing code. Use when you need docs freshness, a clear verification story, release notes, and explicit residual risk before the work is considered ready.

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

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. ALWAYS USE THIS SKILL instead of native CI provider tools (gh, glab, etc.) for CI monitoring.

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.