docs: frame content-type naming as a positive decision in USER.md
Reword the naming guidance from a "not X" anti-pattern to the decision we actually made: name content/file-type recognition "detection" or "discovery". Keeps the plain-language intent without prescribing what to avoid. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
aac79274bc
commit
8f2ba022bf
1 changed files with 2 additions and 1 deletions
3
USER.md
3
USER.md
|
|
@ -41,7 +41,8 @@ TTS voice preference: sl-SI-RokNeural (Slovenian)
|
||||||
says `Run as: sh script.sh`, not also `NOT as: python3 script.sh`.
|
says `Run as: sh script.sh`, not also `NOT as: python3 script.sh`.
|
||||||
- **Plain language over jargon.** Branch/PR names a non-technical operator can read
|
- **Plain language over jargon.** Branch/PR names a non-technical operator can read
|
||||||
(`all-checks-green`, not `chore/rustfmt-clean`); avoid `fmt`/`lint`/`CI` in names.
|
(`all-checks-green`, not `chore/rustfmt-clean`); avoid `fmt`/`lint`/`CI` in names.
|
||||||
Say "detection"/"discovery", not "sniffing". Commit *bodies* can still be precise.
|
We name content/file-type recognition "detection" or "discovery" (a settled
|
||||||
|
naming decision). Commit *bodies* can still be precise.
|
||||||
- **Lean, current docs.** When a decision/design ships as working code, slim its doc to
|
- **Lean, current docs.** When a decision/design ships as working code, slim its doc to
|
||||||
a short "how it works now" and point at the real files (code is source of truth); flip
|
a short "how it works now" and point at the real files (code is source of truth); flip
|
||||||
`Proposed` → `Accepted — implemented`, drop migration/to-do sections. No history
|
`Proposed` → `Accepted — implemented`, drop migration/to-do sections. No history
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue