use-case — a verified-only use-case catalog skill for Claude Code

A project-agnostic agent skill that answers "what can this product actually do?" — with proof.

It walks your codebase to find candidate capabilities, then walks your live app in a real browser to verify what a user can actually reach, and renders the result as:

1. An in-app panel (/use-cases) — every capability grouped by persona, written in user language, one click from the live feature. Generated in your project's own stack and styled by your existing design tokens.
2. A demo deck — one self-contained HTML file (screenshots embedded, zero external requests) you can hand to a stakeholder without granting app access.
3. An unreachable report — features that exist in code but that no user can reach: dead components, broken paths, data-gated flows. On its first run against a real product, this skill found an entire six-component UI subtree with zero importers and a live API bug.

The three rigid rules

1. Verified-only. A use case enters the catalog only after the agent has walked its path in the running app and seen the feature render with real data. Aspirational features do not exist. Unreachable candidates become engineering findings, not catalog padding.
2. One theme. The panel extends the project's existing token system — never a second design system bolted onto your app.
3. Mount-point gate. Before writing panel code, the agent must prove the mount point has a live consumer (nav → layout → route). Features shipped into dead code are this skill's reason to exist; it refuses to add one.

The contract

A typed use-cases.json committed to your repo is the single source of truth. Three consumers read it: the panel, the deck generator, and the regression re-walk. Re-runs diff instead of rebuilding: every cataloged deep-link is re-walked first (a broken walk is a loudly-reported regression), then new candidates are swept, then dead entries pruned.

{
  "generatedAt": "…",
  "personas": [{ "id": "ops", "label": "Operations manager" }],
  "useCases": [{
    "id": "overdue-invoices",
    "persona": "ops",
    "title": "See which customers are overdue and how much is at stake",
    "scenario": "Month-end is tomorrow and cash is tight; you need every overdue invoice, oldest first, with a total.",
    "walkPath": "/invoices?filter=overdue",
    "walkSteps": ["Open Invoices", "Filter to Overdue", "Read the aging summary"],
    "verifiedAt": "2026-08-01",
    "evidence": "docs/use-cases/evidence/overdue-invoices.png"
  }]
}

Install

npx skills add succtorlin/use-case

(installs for Claude Code, Codex, Cursor, Gemini CLI and other agents via the skills CLI) — or manually:

git clone https://github.com/succtorlin/use-case.git ~/.claude/skills/use-case

Then in Claude Code, ask: "what can this product do?", "generate the use-case panel", "refresh the use cases", or "build a demo deck".

Files

• SKILL.md — the pipeline (inventory → synthesis → browser verification → catalog → panel), rigid rules, re-run mode
• references/catalog-schema.md — the contract and copy rules
• references/verification.md — the browser-walk procedure and honesty rules
• references/panel-generation.md — stack detection, theming, the mount gate

License

MIT