Skip to content

fix: update CONTEXT.md reference in domain.md #1744

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
LucasSantana-Dev merged 2 commits into from
Jul 9, 2026
Merged

fix: update CONTEXT.md reference in domain.md #1744

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8f0730c
docs: update CONTEXT.md reference — now exists and documents domain v…
LucasSantana-Dev Jul 9, 2026
e306ab4
Merge branch 'main' into fix/1644-domain-md-stale-ref
LucasSantana-Dev Jul 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions docs/agents/domain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Single-context repo. ADRs live in **`decisions/`** (not the conventional `docs/a

```
/
├── CONTEXT.md ← not yet created; proceed silently if absent
├── CONTEXT.md ← canonical domain glossary; defines vocabulary for all domain concepts
├── decisions/ ← ADRs live here (tracked, repo root)
│ └── YYYY-MM-DD-<slug>.md
├── docs/ ← human-facing project documentation only
Expand All @@ -21,11 +21,9 @@ Single-context repo. ADRs live in **`decisions/`** (not the conventional `docs/a

## Before exploring, read these

- **`CONTEXT.md`** at the repo root (if it exists).
- **`CONTEXT.md`** at the repo root — canonical domain glossary. Defines vocabulary for all domain concepts: tenancy (Guild, Member, User), music runtime (Track, Source, Queue, Player, Session), autoplay and recommendations, guild automation, moderation, engagement (XP, Level, Starboard), role granting, integrations, and support. Use these exact terms in issue titles, refactor proposals, and test names to stay aligned with the codebase's language.
- **`decisions/`** — read ADRs that touch the area you're about to work in. Filter by date and slug.

If `CONTEXT.md` doesn't exist, **proceed silently**. Don't flag its absence; don't suggest creating it upfront. The producer skill (`/grill-with-docs`) creates it lazily when terms or decisions actually get resolved.

## Use the glossary's vocabulary

When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in `CONTEXT.md`. Don't drift to synonyms the glossary explicitly avoids.
Expand Down
Loading