domainkit

Record domain glossary terms and architectural decision records in CONTEXT.md and docs/adr/.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/mimukit/skills --skill domainkit-mimukit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domainkit
Source: https://github.com/mimukit/skills/tree/main/skills/domainkit
Command: npx skills add https://github.com/mimukit/skills --skill domainkit-mimukit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose track of what domain terms mean and why hard-to-reverse decisions were made, because nobody remembers to write them down while design work is happening. This Skill detects those moments mid-workflow and records the settled vocabulary and reasoning as durable project artifacts. ## Core Features & Use Cases - Ubiquitous language glossary: Maintains a repo-root CONTEXT.md (or CONTEXT-MAP.md for multi-context projects) defining domain-specific terms, with rejected synonyms listed under Avoid. - Architecture decision records: Creates sequentially numbered ADRs in docs/adr/ using the adr-NNNN-<slug>-YYYY-MM-DD.md convention, gated by a three-part bar (hard to reverse, surprising without context, genuine trade-off). - Consent-gated writes: Detects the moment, proposes the entry, and writes only after the user approves, so it never creates spurious files. - Use Case: While grilling a design decision, the team settles on using Postgres over an event log. The Skill offers an ADR capturing the context, decision, and rejected alternative, then writes docs/adr/adr-0007-use-postgres-2026-07-23.md on approval. ## Quick Start Ask the agent to record the decision we just made about the database choice as an ADR and add the term we settled on to the project glossary.

Frequently Asked Questions about domainkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an architecture decision record for my project?

Create a Markdown file in docs/adr/ named adr-NNNN-<slug>-YYYY-MM-DD.md with the next sequential number. Include a title, a short paragraph covering context, decision, and why, plus optional Status, Considered Options, and Consequences sections.

How do I maintain a ubiquitous language glossary in a repo?

Keep a CONTEXT.md file at the repo root defining only domain-specific terms in one or two sentences each. Pick one canonical term per concept and list rejected synonyms under an _Avoid_ line; exclude general programming concepts.

When should a decision get an ADR versus staying undocumented?

Write an ADR only when all three hold: the decision is hard to reverse, surprising without context, and involved a genuine trade-off between real alternatives. Routine or easily changed choices should not be recorded.

Can ADR files be edited after they are written?

ADR content is immutable once shipped; the only mutable field is Status. A later ADR can mark an older one deprecated or superseded by ADR-NNNN, and parallel-branch numbering conflicts are resolved by renumbering during merge.

What happens if a domain term is still unresolved?

The Skill does not record unsettled terms or decisions. It defers to an interrogation skill such as grillkit when installed, or asks the user to settle the question directly, then records the result once resolved.