research-groundedlisted

# Research-grounded Catch design decisions that were made without checking current best practice — *before* they become code. A planning doc that says "we'll use X" with no provenance is a bet on training-cutoff recall; the convention `# research(YYYY-MM): <tradeoff> <source>` records that the bet was checked against reality. This skill finds the bets that weren't. ## Repo context `/techne:research-grounded` audits docs in the CWD repo by default, or a path you name (which may live in another repo). Resolve the repo root from the argument: ```bash git -C "$(dirname "<target-doc>")" rev-parse --show-toplevel # no path arg → CWD repo root ``` The target's `.claude/skill-context.md` isn't required, but its `## repo` section helps you tell a genuine technology choice from incidental prose. ## What needs provenance A **committed design decision** — a choice with real alternatives, where picking wrong is expensive to undo: - **Library / framework / tool** — "MapLibre + PMTiles", "Playwright over Cypress", "switched from JWT to server sessions". - **Pattern / technique** — "event delegation over per-node listeners", "stale-while-revalidate", "container queries for card internals". - **Architecture / protocol** — "A2A `Message.metadata` instead of text tags", "OPFS for tile storage". - **Version / API-surface bets stated as fact** — "ElevenLabs v3 supports SSML break tags" (the miss that cost 5 revertable PRs: a capability asserted, never verified against the target's docs)