strata-capturelisted
Install: claude install-skill zbmowrey/strata
# Capturing knowledge
## When
Capture **immediately** when you learn something non-obvious and reusable:
a gotcha (symptom → cause → fix), a decision and its reason, how something really works,
a fact you had to dig for, a correction from the user. Do **not** capture what the code or
git history already says, transient state, or secrets (record _where_ a secret lives).
```
strata capture "pytest hangs at exit: session-scoped db fixture never closes its pool; add teardown" \
--type gotcha --tags pytest,database --source file:tests/conftest.py --project ci-flake
strata capture "user: deploys happen Tuesdays only, never Fridays" --type correction \
--shard deploy-schedule --source "user:said in session"
```
Captures land in `knowledge/_inbox/` and are searchable at once; the gardener files them.
`--type correction --shard <id>` also bumps that shard's `occurrences`.
## Fix the record in place
A shard is wrong → correct it now: fix the claim, add the evidence to `sources`, bump
`updated` (and `verified_at` if you confirmed it). Never overwrite `trust: user-stated` —
tell the user. Precedence: user-stated > verified > observed > inferred.
## Shard anatomy
`strata new shard <domain>/<topic>/<id> --type <type> --title "…" --summary "…"`, then edit.
- One idea per shard; filename stem == `id` (kebab-case, globally unique).
- Required: `id, title (≤ 80), summary (≤ 160, one line), type, tags (≥ 1), status, trust,
created, updated`; `sources` (kind ∈ user/url/file/commit/s