Przejdź do treści
Biblioteka skilli
Programowanie · Pisanie

domain-modeling

/domain-modeling

Buduje i doszlifowuje model domeny projektu, gdy omawia się terminy z kodu, pisze CONTEXT.md lub zapisuje ADR.

Repozytorium
brain ↗
Licencja
MIT
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
3
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Buduje i doszlifowuje model domeny projektu, gdy omawia się terminy z kodu, pisze CONTEXT.md lub zapisuje ADR.

Oryginalny opis (EN)

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.

Jak działa

  1. File structure
  2. During the session
Sekcje z nagłówków SKILL.md, w oryginale · 85 linii, 717 słów
Podgląd SKILL.md
---
name: domain-modeling
description: 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.
---

# Domain Modeling

Actively build and sharpen the project's domain model as you design. This is the *active* discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely *reading* `CONTEXT.md` for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)

## File structure

This workspace is single-context, but the files live in `brain/`, never in a repo:

```
brain/knowledge-catalog/
├── glossary.md                 ← the CONTEXT.md role
└── decisions/
    ├── 0001-<slug>.md          ← ADRs, OKF `decision` files
    └── out-of-scope/           ← rejected requests (triage); see /triage
```

The host repository's own `CONTEXT.md`, `CLAUDE.md` or `docs/adr/`, where they exist, are the team's own. Read and respect them; write to them only when the user explicitly asks for a team-facing ADR. See `brain/knowledge-catalog/reference/agent-skills/domain.md`.
**Workspace copy.** Adapted for this workspace: the issue tracker is `brain/tasks/` (local OKF task files), domain docs live in `brain/knowledge-catalog/`, and nothing agent-related is written into the repos. Read `brain/knowledge-catalog/reference/agent-skills/tracker.md` before publishing anything.

## During the session

### Ask the record before proposing a term

```bash
brain/bin/relevant "<the concept>"
```

A term that contradicts a decision is not a vocabulary question, it is a
contradiction — surface it as one. This skill reads the glossary and the
decisions folder but never searched the record, so a concept already settled
under a different word looked like new ground.

### Challenge against the glossary

When the user uses a term that conflicts with the existing language in `brain/knowledge-catalog/glossary.md` (or the host repository's `CONTEXT.md`), call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y. Which is it?"

### Sharpen fuzzy language

When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account': do you mean the Customer or the User? Those are different things."

### Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.

### Cross-reference with code

When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible. Which is right?"

### Update the glossary inline

When a term is resolved, update `brain/knowledge-catalog/glossary.md` right there. Don't batch these up: capture them as they happen. Use the format in [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md).

The glossary should be totally devoid of implementation details. Do not treat it as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.

### Offer ADRs sparingly

Only offer to create an ADR when all three are true:

1. **Hard to reverse**: the cost of changing your mind later is meaningful
2. **Surprising without context**: a future reader will wonder "why did they do it this way?"
3. **The result of a real trade-off**: there were genuine alternatives and you picked one for specific reasons

If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](./ADR-FORMAT.md): an OKF `decision` file created with `brain/bin/new decision "<the claim>"`, which allocates the `D` id.

Give it `serves:` (the goal it pursues) and, where you can state one, an
`invariant:` — the single sentence a future change could violate — plus
`constrains:`, the paths it governs. Those two fields are what let
`brain/bin/constraints` surface this decision to someone touching that code
later; without them it can only ever be found by searching for the words it
happens to use.

### A principle is a decision with no alternatives

Occasionally what crystallises is not a choice between options but a standing
constraint: *we never put a judgement where a lookup would do.* That is a
`principle`, not a decision — `brain/bin/new principle "<the constraint>"`. It
shares the `D` sequence, because it carries the same authority.

The test is the Alternatives section. If you cannot write one honestly, you
are not choosing, you are asserting — and an assertion filed as a decision
with an invented rejected option is worse than either. Principles are **rare**:
a handful per project, constraining every decision under them. If you find
yourself writing a third this month, they are decisions.
Pliki w paczce (3)
  • ADR-FORMAT.md 3 KB
  • CONTEXT-FORMAT.md 2 KB
  • SKILL.md 5 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · hootener/brain100MIT
matteocodogno/wellforge100MIT
zenobi-us/dotfiles100MIT
JamalLyons/Agent-Skills100MIT
FrancoStino/opencode-skills-collection100MIT
yuan88964/RelayStudio100MIT
Aysnc-Labs/skills100MIT
askgina/plugins100Apache-2.0
j0hanz/j0hanz-marketplace100MIT

Migawka bazy z 13.11.2026 · wersja paczki 3985b43bb6fb (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 1 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 95workflow-domain-modeling
    Buduje i wyostrza model dziedziny projektu: pilnuje terminologii w GLOSSARY.md i zapisuje decyzje architektoniczne w ADR.
  • 100s-domain-modeling
    Buduje i doprecyzowuje model domeny projektu: słownik pojęć w GLOSSARY.md oraz zapisy ADR przy zmianach terminów i reguł.
  • 100domain-model
    Buduje i doszlifowuje model domeny projektu: język wszechobecny w CONTEXT.md, konteksty, agregaty, niezmienniki i model danych.
  • 100matt-domain-modeling
    Buduje i wyostrza glosariusz oraz model domeny projektu w pliku CLAUDE.md, a decyzje zapisuje jako ADR w docs/patterns.
  • 100ra-domain-modeling
    Buduje model domeny projektu: wspólny słownik, niezmienne reguły architektury i decyzje ADR, gdy terminy są niejednoznaczne.
  • 100docs-domain-modeling
    Buduje model domenowy projektu: glosariusz CONTEXT.md i język ubikwitarny, gdy trzeba ustalić terminologię lub agent używa niewłaściwych słów.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.