← ClaudeAtlas

use-caselisted

Use when asked what a product can do, to generate or refresh a use-case panel, to build a demo deck, or to find features that exist in code but are unreachable in the app. Walks the codebase AND the live app in a browser; only browser-verified use cases are cataloged.
succtorlin/use-case · ★ 1 · AI & Automation · score 54
Install: claude install-skill succtorlin/use-case
# Use-Case Catalog ## Overview Complicated products hide their own capabilities. This skill discovers what a product can do (code walk), proves what a user can actually reach (browser walk), and renders the result as an in-app panel plus an optional demo deck. Works on ANY project with a runnable user interface — a SaaS app, an admin panel, an internal tool, a docs site — in any stack and any domain; nothing in the pipeline assumes what the product is about. Phase 5 detects the stack and follows the target project's own conventions. Core contract: a typed catalog file committed to the target repo is the single source of truth. Nothing renders that is not in it, and nothing enters it without being walked in the live app. ## When to use - "What can this product do?" / "Generate the use-case panel" - "Refresh the use cases" (re-run mode) / "Build a demo deck" - "Are there features users can't reach?" (the unreachable report) ## Rigid rules (non-negotiable) 1. **Verified-only.** A use case enters the catalog only after you walked its path in the running app and saw the feature render with real data. Unreachable candidates go to the unreachable report — a first-class output, not an apology. 2. **One theme.** The panel extends the project's existing token system. Never install a second design system (fantastic-ui Step 0, gate 2). 3. **Mount-point gate.** Before writing panel code, prove the mount point has a live consumer (trace nav/config → layout → route).