Przejdź do treści
Biblioteka skilli
Programowanie · Planowanie

model

/model

Tworzy słowniczek domeny i pułapki rozbieżności dla ograniczonego kontekstu, mapuje pojęcia na kod i zgłasza pytania do rozstrzygnięcia.

Repozytorium
claude-toolbox ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

90/ 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ść25 / 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
46
Skrypty
18
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co sprawdzić przed instalacją
  • 18 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: evals/brownfield-update/test-files/gym/grading.go, evals/brownfield-update/test-files/gym/route.go, evals/brownfield-update/test-files/gym/wall.go, evals/hidden-invariant/test-files/campground/booking.go, evals/hidden-invariant/test-files/campground/gate.go, evals/hidden-invariant/test-files/campground/occupancy.go, evals/hidden-invariant/test-files/campground/site.go, evals/kit-format/test-files/

Co robi i kiedy

Tworzy słowniczek domeny i pułapki rozbieżności dla ograniczonego kontekstu, mapuje pojęcia na kod i zgłasza pytania do rozstrzygnięcia.

Wyzwalacze z opisu

model the domainbuild a glossarydomain referencebounded contextwhat are the concepts here
Oryginalny opis (EN)

Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close before design. Runs upstream of feature /kk:design as the first producer of the architecture flow, and emits artifacts /kk:review-architecture verifies. Triggers: "model the domain", "build a glossary", "domain reference", "bounded context", "what are the concepts here". NOT for behavi

Jak działa

  1. Conventions
  2. Workflow
  3. Required Outputs
Sekcje z nagłówków SKILL.md, w oryginale · 38 linii, 610 słów
Podgląd SKILL.md
---
name: model
description: |
  Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close before design. Runs upstream of feature /kk:design as the first producer of the architecture flow, and emits artifacts /kk:review-architecture verifies. Triggers: "model the domain", "build a glossary", "domain reference", "bounded context", "what are the concepts here". NOT for behavioral code review or writing a feature design doc.
---

# Domain Modelling — the steady-state kit

**Goal: produce a provenance-clean domain-reference kit and, above all, a decision queue of precise, role-tagged questions a human can close.** The queue is the primary output — artifact count and model sophistication are explicitly not the metric.

`/kk:model` is the first **producer** of the architecture flow: it runs at information-architecture altitude (what the domain's concepts are, where they bind to code, and which questions about them only a human can close), upstream of feature `/kk:design` and never called by it. It writes files and interacts with you mid-flow — it is a main-session skill, not a read-only reviewer.

## Conventions

- **Capy knowledge base** — read [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md); searched at intake (`kk:arch-decisions`, `kk:project-conventions`), indexed at close.
- **Shared producer guards** — four workflow guards, each citing the field failure it prevents. Load all four before acting:
  - [shared-requirements-harvesting.md](shared-requirements-harvesting.md) — quote the real asks before modelling (F1).
  - [shared-open-question-pass.md](shared-open-question-pass.md) — verification asks new questions, not just re-confirms (F4).
  - [shared-fact-flip-propagation.md](shared-fact-flip-propagation.md) — a contradicted fact is fixed everywhere in-session (F2).
  - [shared-contact-ratio-guard.md](shared-contact-ratio-guard.md) — at N:0 artifacts-to-contacts, the next step is a conversation (F5).
- **Profiles are not consulted** — `/kk:model` is language-agnostic in M2; archaeology reads code directly. Profile enrichment is deferred (design §8).

## Workflow

**Mandatory order — instructions before subject matter.** The flow is strictly sequential. Do **not** read code to model it, draft any kit page, or engage the domain beyond a mode-detecting directory/keyword scan until every instruction file is loaded: this SKILL.md, the process file [model-process.md](model-process.md), the reading method [archaeology.md](archaeology.md), the output contract [kit-contract.md](kit-contract.md), all four shared guards above, and the shared capy protocol. This ordering is load-bearing: with domain code in context before the contracts load, the model emits plausible terms and skips the methodology that makes them trustworthy.

1. **Load instructions.** Read [model-process.md](model-process.md) (the detailed seven-phase workflow), [archaeology.md](archaeology.md), [kit-contract.md](kit-contract.md), all four shared guards — [shared-requirements-harvesting.md](shared-requirements-harvesting.md), [shared-open-question-pass.md](shared-open-question-pass.md), [shared-fact-flip-propagation.md](shared-fact-flip-propagation.md), [shared-contact-ratio-guard.md](shared-contact-ratio-guard.md) — and [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md). Minimal early scope — a directory listing or a keyword scan of the request — is permitted only to drive mode detection.
2. **Execute the seven phases** per [model-process.md](model-process.md):
   1. **Scope intake** — establish the bounded context, the **forcing question** (the feature/ticket that bounds what is worth modelling), and the **mode** (greenfield: no kit exists → produce the two pages; brownfield: an existing kit is read in full first and all changes are deltas, status markers never flipped unilaterally). Run the capy knowledge search.
   2. **Requirements-harvesting gate** *(guard, F1)* — read every linked ticket + one hop; quote the actual asks into working notes before any modelling.
   3. **Archaeology** — read code **state → time → invariants** per [archaeology.md](archaeology.md); two-clock discipline (code-clock facts verifiable, intent stays `proposed`).
   4. **Draft the kit** per [kit-contract.md](kit-contract.md) — glossary page + divergences/traps page (+ conventions index if the home has none).
   5. **Verify** — at least one confirm-pass **plus at least one open-question pass** *(guard, F4)*.
   6. **Self-check** — conventions-bind-author lint: the produced pages obey the kit's own declared conventions.
   7. **Surface & close** — present the **decision queue** (each RQ precise, decidable, role-tagged); apply the **contact-ratio guard** *(F5)*; in brownfield, **fact-flip propagation** *(F2)* on any contradicted recorded fact; index non-obvious rationale to `kk:arch-decisions`.

## Required Outputs

- [ ] The two durable kit pages (glossary + traps) for the context, provenance-clean, per [kit-contract.md](kit-contract.md) (+ conventions index if the home lacked one).
- [ ] The **decision queue** — precise, decidable, role-tagged questions — presented inline and appended to the active feature's `docs/feat/wip/<feature>/design.md` under an **Open Questions** heading when that directory exists.
- [ ] Contact-ratio guard applied; brownfield fact-flips propagated across the workspace.
- [ ] Non-obvious modelling rationale indexed to `kk:arch-decisions`.
Pliki w paczce (46)
  • SKILL.md 6 KB
  • archaeology.md 3 KB
  • kit-contract.md 12 KB
  • model-process.md 9 KB
  • shared-capy-knowledge-protocol.md 1 KB
  • shared-contact-ratio-guard.md 1 KB
  • shared-fact-flip-propagation.md 1 KB
  • shared-open-question-pass.md 1 KB
  • shared-requirements-harvesting.md 1 KB
  • evals/brownfield-update/eval.json 4 KB
  • evals/brownfield-update/oracle/gold-deltas.json 4 KB
  • evals/brownfield-update/test-files/docs/architecture/index.md 1 KB
  • evals/brownfield-update/test-files/docs/architecture/routesetting-traps.md 1 KB
  • evals/brownfield-update/test-files/docs/architecture/routesetting.md 3 KB
  • evals/brownfield-update/test-files/gym/go.mod 1 KB
  • evals/brownfield-update/test-files/gym/grading.go 1 KB
  • evals/brownfield-update/test-files/gym/route.go 1 KB
  • evals/brownfield-update/test-files/gym/wall.go 1 KB
  • evals/hidden-invariant/eval.json 4 KB
  • evals/hidden-invariant/oracle/gold-invariant.json 3 KB
  • evals/hidden-invariant/test-files/campground/booking.go 1 KB
  • evals/hidden-invariant/test-files/campground/gate.go 1 KB
  • evals/hidden-invariant/test-files/campground/go.mod 1 KB
  • evals/hidden-invariant/test-files/campground/occupancy.go 1 KB
  • evals/hidden-invariant/test-files/campground/site.go 1 KB
  • evals/kit-format/eval.json 6 KB
  • evals/kit-format/oracle/kit-conventions-checklist.json 5 KB
  • evals/kit-format/test-files/bikeshare/bike.go 1 KB
  • evals/kit-format/test-files/bikeshare/dock.go 1 KB
  • evals/kit-format/test-files/bikeshare/go.mod 1 KB
  • evals/kit-format/test-files/bikeshare/policy.go 1 KB
  • evals/kit-format/test-files/bikeshare/ride.go 1 KB
  • evals/requirements-gate/eval.json 4 KB
  • evals/requirements-gate/oracle/gold-harvest.json 3 KB
  • evals/requirements-gate/test-files/ferry/boarding.go 1 KB
  • evals/requirements-gate/test-files/ferry/go.mod 1 KB
  • evals/requirements-gate/test-files/ferry/reservation.go 1 KB
  • evals/requirements-gate/test-files/ferry/sailing.go 1 KB
  • evals/requirements-gate/test-files/ferry/tickets/FERRY-12.md 1 KB
  • evals/requirements-gate/test-files/ferry/tickets/FERRY-31.md 1 KB
  • evals/scope-pushback/eval.json 3 KB
  • evals/scope-pushback/test-files/apiary/colony.go 1 KB
  • evals/scope-pushback/test-files/apiary/go.mod 1 KB
  • evals/scope-pushback/test-files/apiary/harvest.go 1 KB
  • evals/scope-pushback/test-files/apiary/hive.go 1 KB
  • evals/scope-pushback/test-files/apiary/inspection.go 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · serpro69/claude-toolbox90Apache-2.0
vecten/vecten-open100Apache-2.0
ilanbm/kpopper91MIT
serpro69/claude-toolbox90Apache-2.0
hdkhosravian/dynamic-harness90MIT
Alejo2075/claude-code-aws90MIT
florianbuetow/claude-code90MIT
laaielichter/Godotwright86MIT
laaielichter/Threesmith86MIT

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

Pobrania w ostatnich 30 dniach: 0 · ranking

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

Podobne skille

  • 100domain-model
    Tworzy lub recenzuje model domeny: bounded contexts, encje, value objects, agregaty, zdarzenia domenowe i relacje.
  • 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-modeling
    Buduje i doszlifowuje model domeny projektu, gdy omawia się terminy z kodu, pisze GLOSSARY.md lub zapisuje ADR.
  • 100domain-modeling
    Buduje model domeny projektu, gdy zmienia się terminologia, albo przy GLOSSARY.md i zapisie decyzji ADR.
  • 100domain-modeling
    Buduje i doprecyzowuje model domeny projektu, omawia terminologię kodu, pisze i edytuje GLOSSARY.md oraz zapisuje lub poprawia ADR.
  • 100domain-modeling
    Buduje i doszlifowuje model domeny projektu, gdy omawia się terminologię, pisze GLOSSARY.md lub zapisuje decyzje ADR.

Uwagi i zgłoszenia

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