Skip to content

fix(maintain-context): keep context definitions glossary-only #30

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
adamwhp merged 1 commit into from
Jul 18, 2026
Merged

fix(maintain-context): keep context definitions glossary-only #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion skills/maintain-context/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Create the root file lazily from the [context template](assets/context-template.

### 2. Keep the glossary rigorous

Define domain meaning rather than implementation, specifications, or general programming concepts. Give each meaning one authoritative entry, keep its definition to one or two sentences, and add `_Avoid_` only for aliases or ambiguous alternatives that actually occur.
Keep `CONTEXT.md` as a glossary of project-specific domain language: define each term's meaning in one or two sentences, leaving implementation and specifications to their authoritative sources. Give each meaning one authoritative entry, and add `_Avoid_` only for aliases or ambiguous alternatives that actually occur.

Use **Conceptual Contours** to group related terms under descriptive subheadings when meaningful domain clusters emerge; keep one flat language list when the terms form a cohesive area. If context-dependent meanings conflict with the single-context structure, surface that ambiguity instead of inventing another context file.

Expand Down