TAGS.md is the reference file for case metadata — it lists valid values for categories,
technologies, failure modes, patterns, and levels. Every case uses it when filling in case.yaml.
The problem is that case.yaml has an audience: field too, and TAGS.md has no section
for it. Right now, if you're adding a new case and want to fill in audience:, there's nothing
to look at. You'd have to guess or go read someone else's case.yaml and hope you picked
the right value.
What needs to change
Add an ## Audience section to TAGS.md, after ## Patterns. Go through all 11 case.yaml
files in the cases/ directory, collect every unique value from the audience: field, and
list them with a short one-line description each. The ## Levels section is a good style
reference — one sentence per entry, plain language, no fluff.
Don't add values that aren't in any existing case. Don't rename or consolidate anything
(for example, interview-prep and backend-interview-prep both exist — list them both as-is).
Don't touch any case.yaml files, CONTRIBUTING.md, CASE_FORMAT.md, or anything else.
Acceptance criteria
TAGS.md has a new ## Audience section after ## Patterns- Every unique
audience: value from all 11 case.yaml files appears in the section
- Each value has a one-line description consistent with the style of
## Levels
- Nothing else in the repo is changed
Before you submit
No commands needed — just open each case.yaml and double-check that every value you
found is in your new section. Leave a comment in your PR listing the values you collected;
it makes the review a lot faster.
You don't need Docker or Python for this. It's a one-file documentation change.
TAGS.mdis the reference file for case metadata — it lists valid values for categories,technologies, failure modes, patterns, and levels. Every case uses it when filling in
case.yaml.The problem is that
case.yamlhas anaudience:field too, andTAGS.mdhas no sectionfor it. Right now, if you're adding a new case and want to fill in
audience:, there's nothingto look at. You'd have to guess or go read someone else's
case.yamland hope you pickedthe right value.
What needs to change
Add an
## Audiencesection toTAGS.md, after## Patterns. Go through all 11case.yamlfiles in the
cases/directory, collect every unique value from theaudience:field, andlist them with a short one-line description each. The
## Levelssection is a good stylereference — one sentence per entry, plain language, no fluff.
Don't add values that aren't in any existing case. Don't rename or consolidate anything
(for example,
interview-prepandbackend-interview-prepboth exist — list them both as-is).Don't touch any
case.yamlfiles,CONTRIBUTING.md,CASE_FORMAT.md, or anything else.Acceptance criteria
TAGS.mdhas a new## Audiencesection after## Patternsaudience:value from all 11case.yamlfiles appears in the section## LevelsBefore you submit
No commands needed — just open each
case.yamland double-check that every value youfound is in your new section. Leave a comment in your PR listing the values you collected;
it makes the review a lot faster.
You don't need Docker or Python for this. It's a one-file documentation change.