Terminology discussion alone can trigger repository writes without per-change confirmation
Source references: 3The Skill applies to ordinary codebase terminology discussions, but also directs the agent to update CONTEXT.md immediately once a term is resolved and to create the file if absent. It does not require showing a patch or obtaining explicit confirmation before each write.
A repository document may be created or changed when the user only intended to discuss or explore the model. Language that the user has not finally approved could then become an authoritative glossary used by developers or later AI agents.
The source supports this risk. The Skill may activate when the user is merely discussing codebase terminology, yet it directs the agent to modify `CONTEXT.md` immediately when a term is resolved and to create the file if absent. It does not require per-write consent. A normal discussion could therefore produce persistent repository changes. Users can ask the author for a read-only discussion mode and require an explicit request plus patch preview before applying changes.
name: domain-modelingdescription: Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.---Show 2 other places
Create files lazily: only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs/adr/` exists, create it when the first ADR is needed.### Update CONTEXT.md inlineWhen a term is resolved, update `CONTEXT.md` right there. Don't batch these up: capture them as they happen. Use the format in [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md).