Cases
Case pages place skills inside real workflows: triggers, outputs, and exit criteria—so you can chain skills into repeatable pipelines. Below we use the same framing as the Agents & skills page to explain what case pages solve vs the skill index and category browse.
What a case page is
Each case describes a typical moment: who triggers it, what deliverable you expect, and what “done” means. Best for workflow narratives and alignment with review, ship, or incident context.
Cases vs the skill library
The skill index lists skills by entry and category; the more cases list uses workflow language for when to trigger and when you’re finished. They’re usually combined: pick skills, then map cases—or start from a case and attach skills.
Browse by category
When you already know the stage or function (code, docs, observability, collaboration, incidents), use Browse by scenario below to jump into the right bucket and shared checklists.
Start from more cases
To browse every case by category, compare across buckets, or share a single URL, use more cases. In multi-team or high-compliance settings, code quality and incident triage are good first stops.
Related entry points: agent vs skill trade-offs and composition on the Agents & skills page; the full skill list in the skill index; all cases via more cases.
Browse by scenario
Five scenario hubs first; the more cases entry is last. Each hub lists multiple case pages you can cross-link with skill entries.
Code quality
Review checklists, refactors, security, and testing skills that gate merges.
Docs & knowledge
Long-form structure, Cursor Rules, RFCs, and knowledge-base patterns.
Observability
Ship/rollback, log triage, and runbooks agents can execute repeatedly.
Collaboration
PR/issue templates, design tokens, and cross-role alignment from idea to release.
Incident triage
On-call tiers, evidence trails, and status comms under pressure.
More cases
Browse all cases by category—pair with the skill library; each has its own page.
Featured cases
Skills in real workflows: triggers, outputs, and exit criteria—easy to chain with multiple SKILL entries.
Code review & pre-merge checks
Review lists, risk signals, and merge gates—pairs with review-oriented skills.
Dependency & OSS license scan
Dependency trees, license conflicts, and compliance reports—ties to SBOM skills.
CI/CD & release notes
Change summaries and release records—connects to changelog and ship workflows.
Unit tests & coverage gaps
Backfill tests, edge cases, coverage targets, and gap lists.
API contract & doc sync
OpenAPI/contract changes and consistency between docs and implementation.
DB migrations & rollback plans
DDL/DML, locking risk, rollback SQL, and verification steps.
Incident RCA & impact triage
Timelines, dependencies, user impact, and hypotheses—pairs with runbooks and on-call skills.
Dependency vulns & CVE priority
CVSS, reachability, patches, and mitigations—with SBOM and security-scan skills.