caseops

Use this skill for any CaseOps bug triage, verification, reopen analysis, or review of another agent's bug-fix claim. Enforces fail-closed bug handling: reproduce, root cause, adjacent-path audit, regression coverage, strongest verification, and honest verdicts.

Use this skill for any CaseOps feature planning, implementation, product-gap analysis, module review, UX redesign, or PRD update. Forces every task to map to the unified PRD, current repo truth, source-data rules, user stories, and test IDs before work begins.

Use this skill whenever the user asks to ingest, embed, populate, backfill, or improve quality of the CaseOps authority corpus (Supreme Court / High Court judgments) in Postgres/pgvector on GCP. Also use when the user asks for a retrieval quality probe or a 0-5 rating on the embedded vectors. Enforces the correct per-bucket pipeline (ingest → Layer-2 metadata → title-chunk embed → quality probe) that prevents the "placeholder title poisons embeddings" failure mode.

Use this skill for any CaseOps enterprise-readiness audit, scale-hardening review, architecture or security gap review, or any scan of docs/WORK_TO_BE_DONE.md. Enforces fail-closed gap classification, code-vs-doc proof, and durable ledger updates.

Use this skill for whole-repo quality audits, release-readiness reviews, exhaustive test-matrix planning, security reviews, or requests to make CaseOps quality gates stricter. Forces evidence-backed inventory, route/page/test matrices, verification results, and durable audit docs.

Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system.