# Domain Docs

This repo uses a single-context domain-doc layout for engineering skills.

## Before Exploring

Read these files when they are relevant to the task:

- `CONTEXT.md` at the repo root.
- `docs/adr/` for architectural decisions that touch the area being changed.

If these files do not exist, proceed silently. Do not create them just because they are absent; producer skills such as `/grill-with-docs` should create them when terms or decisions are actually resolved.

## Vocabulary

When an output names a domain concept, prefer the term used in `CONTEXT.md` if the file exists. If the needed concept is missing, either avoid inventing new vocabulary or record the gap for a dedicated terminology pass.

## ADR Conflicts

If a proposal contradicts an existing ADR, surface that conflict explicitly instead of silently overriding the decision.