How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/clhbid/agent-context --skill domain-docsBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Domain docs
Read domain documentation before exploring a codebase or proposing a domain change. Adapted from Matt Pocock's `domain.md`.
Read before exploring
- Read this repo's
GLOSSARY.mdanddocs/adr/, when present. - Read the corresponding files in
clhbid/CLHbid-LiveAuction. Use gh api to fetch repos/clhbid/CLHbid-LiveAuction/contents/GLOSSARY.md and list repos/clhbid/CLHbid-LiveAuction/contents/docs/adr/, then fetch each ADR with the same contents endpoint and decode its .content from base64. In LiveAuction itself, the local files are these same files, so read them once.
If a glossary or ADR directory is absent locally or in LiveAuction, continue silently.
Apply the domain model
- LiveAuction's glossary and ADRs are the org's source of truth. Flag a local term or ADR that
conflicts with them; surface the conflict rather than choosing one silently.
- Use glossary terms in issue titles, proposals and test names. A missing term is either invented
language to reconsider or a gap to note for /domain-modeling.
- Flag output that contradicts an ADR rather than overriding it silently.
- Write recorded domain knowledge to LiveAuction unless it applies only to this repo.