@documentation-robotics/cli 0.2.0 → 0.3.0

package/dist/integrations/claude_code/skills/dr_08_data_model_layer/SKILL.md

@@ -58,10 +58,10 @@ This layer uses **JSON Schema Draft 7** (industry standard) with custom extensio
 | **SchemaProperty**    | Individual property definition                             |
 | **Reference**         | $ref to other schemas                                      |
 
-> **Note:** Data governance (`x-data-governance`) and database mapping (`x-database`) are
-> cross-layer extension **attributes**, not node types. Set them directly on the schema element
-> they describe — on an `objectschema` for table-level mapping, or on a `schemaproperty` for
-> field-level governance (e.g., marking an individual `email` property as PII).
+> **Note:** Data governance and database mapping are not node types or `x-...` attributes. Record
+> them as relationships from the schema element they describe: `schemaproperty satisfies
+security.dataclassification` for field-level governance (e.g., marking an `email` property as PII),
+> and `objectschema maps-to data-store.collection` for the physical table or collection.
 
 ---
 
@@ -83,14 +83,16 @@ Use this decision tree **before assigning a type** to any code pattern.
 
 ## Common Misclassifications
 
-| Misclassification                                                       | Correct Classification                                                                          | Why                                                                                                                                                                                     |
-| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Modeling `x-data-governance` or `x-database` as their own elements      | Set as extension attributes on the relevant schema element (`objectschema` or `schemaproperty`) | These are cross-layer extension attributes, not spec node types                                                                                                                         |
-| Using `objectschema` for a reusable definition in a `definitions` block | `schemadefinition`                                                                              | `definitions` entries are named, reusable definitions; `objectschema` is for structural instances                                                                                       |
-| Using `schemadefinition` for a top-level schema document                | `jsonschema`                                                                                    | A root document with `$schema` and `$id` is `jsonschema`, not a definition                                                                                                              |
-| Using `schemaproperty` for a standalone string/numeric/array type       | `stringschema` / `numericschema` / `arrayschema`                                                | Use the specific schema type when the constraint set is rich enough to stand alone; use `schemaproperty` only for inline field declarations within an `objectschema`                    |
-| Using `objectschema` for a schema that uses `allOf` to extend another   | `schemacomposition`                                                                             | When the primary purpose is combining or extending schemas, classify as `schemacomposition` — even if the schema also declares `properties`                                             |
-| Using `schemaproperty` for a bare `$ref` with no other constraints      | `reference`                                                                                     | A standalone `$ref` with nothing else is a `reference`; use `schemaproperty` only when the field also carries its own constraints (`title`, `description`, `readOnly`, `default`, etc.) |
+| Misclassification                                                                                                        | Correct Classification                                                                                          | Why                                                                                                                                                                                                                        |
+| ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Modeling data governance or database mapping as their own elements (or as `x-data-governance` / `x-database` attributes) | Relationships from the schema element: `satisfies security.dataclassification`, `maps-to data-store.collection` | These are cross-layer links, not data-model node types                                                                                                                                                                     |
+| Using `objectschema` for a reusable definition in a `definitions` block                                                  | `schemadefinition`                                                                                              | `definitions` entries are named, reusable definitions; `objectschema` is for structural instances                                                                                                                          |
+| Using `schemadefinition` for a top-level schema document                                                                 | `jsonschema`                                                                                                    | A root document with `$schema` and `$id` is `jsonschema`, not a definition                                                                                                                                                 |
+| Using `schemaproperty` for a standalone string/numeric/array type                                                        | `stringschema` / `numericschema` / `arrayschema`                                                                | Use the specific schema type when the constraint set is rich enough to stand alone; use `schemaproperty` only for inline field declarations within an `objectschema`                                                       |
+| Using `objectschema` for a schema that uses `allOf` to extend another                                                    | `schemacomposition`                                                                                             | When the primary purpose is combining or extending schemas, classify as `schemacomposition` — even if the schema also declares `properties`                                                                                |
+| Using `schemaproperty` for a bare `$ref` with no other constraints                                                       | `reference`                                                                                                     | A standalone `$ref` with nothing else is a `reference`; use `schemaproperty` only when the field also carries its own constraints (`title`, `description`, `readOnly`, `default`, etc.)                                    |
+| Filing an in-code structure that is neither persisted nor published as a schema under `objectschema`                     | `application.dataobject`                                                                                        | Entities, ORM models and types whose shape is published as a schema are object schemas; a structure that only carries data between parts of the program is an application data object, which the object schema may realize |
+| A schema `serves` the code that uses it                                                                                  | `application.applicationfunction` (or component, event) `accesses` the schema                                   | Schemas are passive structure: behaviour accesses data; schemas never serve, trigger or perform                                                                                                                            |
 
 ---
 
@@ -106,20 +108,101 @@ Activate when the user:
 
 ---
 
-## Cross-Layer Relationships
+## Intra-Layer Relationships
+
+A subschema written in place is part of what declares it (`composes`); a type declared elsewhere and
+reached by `$ref` or by name is `references`. Subtyping is `specializes`.
+
+| Source Type       | Predicate   | Target Type       | Example                                                            |
+| ----------------- | ----------- | ----------------- | ------------------------------------------------------------------ |
+| JSONSchema        | composes    | ObjectSchema      | "Order API Schemas" document composes its root "Order" schema      |
+| JSONSchema        | composes    | SchemaDefinition  | "Order API Schemas" composes the "Address" definition it declares  |
+| JSONSchema        | composes    | SchemaComposition | "Order API Schemas" composes its root "PaymentMethod" (`oneOf`)    |
+| ObjectSchema      | composes    | SchemaProperty    | "Order" composes the "status" property                             |
+| ObjectSchema      | specializes | ObjectSchema      | "AdminUser" specializes "User"                                     |
+| SchemaProperty    | composes    | StringSchema      | "email" property composes its inline `format: email` constraint    |
+| SchemaProperty    | composes    | NumericSchema     | "total" property composes its inline `minimum: 0` constraint       |
+| SchemaProperty    | composes    | ArraySchema       | "lineItems" property composes its inline array constraints         |
+| SchemaProperty    | references  | ObjectSchema      | "shippingAddress" property references "Address"                    |
+| SchemaProperty    | references  | SchemaDefinition  | "currency" property references the "CurrencyCode" definition       |
+| ArraySchema       | composes    | ObjectSchema      | "LineItemList" composes its inline `items` object schema           |
+| ArraySchema       | composes    | StringSchema      | "TagList" composes its inline `items` string schema                |
+| ArraySchema       | composes    | Reference         | "OrderList" composes its `items: $ref: #/definitions/Order`        |
+| ArraySchema       | references  | SchemaDefinition  | "OrderList" references the "Order" definition its items take       |
+| Reference         | references  | SchemaDefinition  | `$ref: #/definitions/Address` references the "Address" definition  |
+| Reference         | references  | ObjectSchema      | `$ref` to the "Customer" object schema                             |
+| Reference         | references  | JSONSchema        | `$ref: common.schema.json` references that document                |
+| SchemaComposition | composes    | ObjectSchema      | "PaymentMethod" (`oneOf`) composes its inline "CardPayment" branch |
+| SchemaComposition | composes    | Reference         | "CustomerWithAudit" (`allOf`) composes its `$ref` branch           |
+| SchemaComposition | references  | SchemaDefinition  | "CustomerWithAudit" (`allOf`) references "AuditFields"             |
+| SchemaDefinition  | composes    | SchemaDefinition  | "Customer" composes "ContactInfo" declared inside it               |
+| SchemaDefinition  | specializes | SchemaDefinition  | "PremiumCustomer" specializes "Customer"                           |
+| SchemaDefinition  | references  | SchemaDefinition  | "Invoice" references "Customer"                                    |
+
+----------------- | ----------- | ----------------- | ----------------------------------------------------------------- |
+| JSONSchema | aggregates | ObjectSchema | "Order API Schemas" document aggregates "Order" |
+| JSONSchema | aggregates | SchemaDefinition | "Order API Schemas" aggregates the "Address" definition |
+| JSONSchema | aggregates | SchemaComposition | "Order API Schemas" aggregates "PaymentMethod" (`oneOf`) |
+| ObjectSchema | aggregates | SchemaProperty | "Order" aggregates the "status" property |
+| ObjectSchema | extends | ObjectSchema | "AdminUser" extends "User" |
+| SchemaProperty | references | StringSchema | "email" property references "EmailString" (`format: email`) |
+| SchemaProperty | references | NumericSchema | "total" property references "MoneyAmount" (`minimum: 0`) |
+| SchemaProperty | references | ArraySchema | "lineItems" property references "LineItemList" |
+| SchemaProperty | references | ObjectSchema | "shippingAddress" property references "Address" |
+| SchemaProperty | references | SchemaDefinition | "currency" property references the "CurrencyCode" definition |
+| ArraySchema | aggregates | ObjectSchema | "LineItemList" aggregates "LineItem" (its `items` schema) |
+| ArraySchema | aggregates | StringSchema | "TagList" aggregates "Tag" |
+| ArraySchema | aggregates | Reference | "OrderList" aggregates `$ref: #/definitions/Order` |
+| Reference | references | SchemaDefinition | `$ref: #/definitions/Address` references the "Address" definition |
+| SchemaComposition | composes | ObjectSchema | "PaymentMethod" (`oneOf`) composes "CardPayment" |
+| SchemaComposition | composes | SchemaDefinition | "CustomerWithAudit" (`allOf`) composes "AuditFields" |
+| SchemaDefinition | composes | SchemaDefinition | "Customer" composes "ContactInfo" |
+| SchemaDefinition | specializes | SchemaDefinition | "PremiumCustomer" specializes "Customer" |
+| SchemaDefinition | references | SchemaDefinition | "Invoice" references "Customer" |
 
-**Outgoing (Data Model → Other Layers):**
-
-- `x-business-object-ref` → Business Layer (what business concept does this represent?)
-- `x-database` → Data Store Layer (how is this stored physically?)
-- `x-data-governance` → Security Layer (classification, PII, retention)
-- `x-apm-data-quality-metrics` → APM Layer (data quality monitoring)
-
-**Incoming (Other Layers → Data Model):**
+---
 
-- API Layer → Data Model (request/response schemas via $ref)
-- UX Layer → Data Model (form validation rules)
-- Testing Layer → Data Model (input constraints for test partitioning)
+## Cross-Layer References
+
+Cross-layer links are recorded as relationships (`dr relationship add`), not as `x-...` extension attributes.
+
+### Outgoing References (Data Model → Other Layers)
+
+| Source Type      | Predicate  | Target Type                   | Example                                                          |
+| ---------------- | ---------- | ----------------------------- | ---------------------------------------------------------------- |
+| ObjectSchema     | realizes   | `business.businessobject`     | "Order" schema realizes the "Customer Order" business object     |
+| SchemaDefinition | realizes   | `application.dataobject`      | "Customer" definition realizes the "Customer Record" data object |
+| ObjectSchema     | maps-to    | `data-store.collection`       | "User" schema maps to the `users` table                          |
+| SchemaDefinition | maps-to    | `data-store.collection`       | "AuditEntry" definition maps to the `audit_log` collection       |
+| ObjectSchema     | maps-to    | `api.requestbody`             | "CreateOrderRequest" maps to the `POST /orders` request body     |
+| ObjectSchema     | maps-to    | `api.response`                | "Order" maps to the `GET /orders/{id}` 200 response              |
+| SchemaDefinition | maps-to    | `api.schema`                  | "Address" definition maps to the OpenAPI `Address` component     |
+| JSONSchema       | maps-to    | `api.schema`                  | "Order API Schemas" document maps to the API's schema set        |
+| SchemaProperty   | maps-to    | `api.parameter`               | "orderId" property maps to the `{orderId}` path parameter        |
+| SchemaProperty   | references | `security.dataclassification` | "email" property references the "PII" classification             |
+| SchemaProperty   | satisfies  | `security.fieldaccesscontrol` | "ssn" property satisfies the "SSN Masking" field control         |
+| SchemaProperty   | satisfies  | `security.validationrule`     | "password" property satisfies the "Password Strength" rule       |
+| SchemaDefinition | requires   | `security.retentionpolicy`    | "AuditEntry" requires the "7-Year Audit Retention" policy        |
+| ObjectSchema     | satisfies  | `motivation.requirement`      | "Order" satisfies "Orders must record tax breakdown"             |
+
+### Incoming References (Other Layers → Data Model)
+
+| Source Type                        | Predicate  | Target Type      | Example                                                          |
+| ---------------------------------- | ---------- | ---------------- | ---------------------------------------------------------------- |
+| `application.applicationfunction`  | accesses   | ObjectSchema     | "saveOrder" function accesses the "Order" entity                 |
+| `application.applicationcomponent` | accesses   | ObjectSchema     | "OrderRepository" component accesses "Order"                     |
+| `application.applicationevent`     | accesses   | SchemaDefinition | "OrderPlaced" event accesses its "OrderPlacedPayload" definition |
+| `ux.dataconfig`                    | maps-to    | ObjectSchema     | "Order Form Data" binding maps to the "Order" schema             |
+| `ux.dataconfig`                    | maps-to    | ObjectSchema     | "Customer Data" maps to "Customer"                               |
+| `ux.tablecolumn`                   | maps-to    | SchemaProperty   | "Status" column maps to the "status" property                    |
+| `navigation.route`                 | references | SchemaDefinition | `/orders/:id` route references "Order"                           |
+| `navigation.contextvariable`       | maps-to    | SchemaProperty   | "selectedOrderId" context variable maps to "orderId"             |
+| `testing.targetinputfield`         | references | SchemaProperty   | "Quantity" input field references "quantity"                     |
+| `testing.testcasesketch`           | tests      | SchemaDefinition | "Reject invalid currency" test sketch tests "CurrencyCode"       |
+| `apm.metricinstrument`             | monitors   | SchemaDefinition | "schema_validation_failures" counter monitors "Customer"         |
+
+> API operations do not point at data-model schemas; the direction is the other way — the schema
+> `maps-to` the API request body, response, or parameter it shapes.
 
 ---
 
@@ -159,9 +242,6 @@ properties:
       type: string
       format: email
       description: "User email address"
-      x-data-governance:
-        classification: confidential
-        pii: true
     username:
       type: string
       minLength: 3
@@ -175,10 +255,14 @@ properties:
       items:
         type: string
       description: "User role assignments"
-  x-business-object-ref: business.actor.user
-  x-database:
-    table: users
-    schema: public
+```
+
+Link the schema to the business concept, its physical storage, and its data classification with relationships:
+
+```bash
+dr relationship add data-model.objectschema.user business.businessobject.user --predicate realizes
+dr relationship add data-model.objectschema.user data-store.collection.users --predicate maps-to
+dr relationship add data-model.schemaproperty.user-email security.dataclassification.pii --predicate references
 ```
 
 ---
@@ -205,6 +289,6 @@ If any type has ZERO elements, explicitly decide: "This type doesn't apply to th
 
 - Always specify `type` on schema elements — validation fails without it
 - Break complex schemas into reusable `schemadefinition` entries and reference them via `$ref`
-- Mark PII and sensitive fields with `x-data-governance` on the relevant `schemaproperty` or `objectschema`
-- Add `x-business-object-ref` to link to the Business Layer and `x-database` to link to the Data Store Layer
+- Mark PII and sensitive fields with a `satisfies` relationship from the `schemaproperty` to a `security.dataclassification`
+- Link schemas to the Business Layer with `realizes business.businessobject` and to the Data Store Layer with `maps-to data-store.collection`
 - Use `format` for semantic string types (`email`, `uuid`, `date-time`, `uri`) rather than custom `pattern` where a standard format exists

package/dist/integrations/claude_code/skills/dr_09_dataset_layer/SKILL.md

@@ -137,32 +137,81 @@ Activate when the user:
 
 ---
 
-## Cross-Layer Relationships
+## Intra-Layer Relationships
+
+Containment is one level at a time (database → namespace → collection → fields, indexes, validation
+rules, event handlers). Stored data is passive: collections, views, fields and databases are accessed,
+referenced and mapped, and never serve or trigger. Behaviour in the store is stored logic, event
+handlers and access patterns.
+
+| Source Type     | Predicate    | Target Type    | Example                                                                |
+| --------------- | ------------ | -------------- | ---------------------------------------------------------------------- |
+| Database        | composes     | Namespace      | "orders-db" composes the `public` schema                               |
+| Database        | composes     | Collection     | "sessions-redis" composes the `session:*` key collection               |
+| Database        | replicates   | Database       | "orders-db-primary" replicates to "orders-db-replica"                  |
+| Database        | federates    | Database       | "analytics-trino" federates "orders-db"                                |
+| Namespace       | composes     | Collection     | `public` schema composes the `orders` table                            |
+| Namespace       | composes     | View           | `reporting` schema composes `monthly_revenue_mv`                       |
+| Namespace       | composes     | StoredLogic    | `public` schema composes `calculate_discount()`                        |
+| Collection      | composes     | Field          | `orders` composes `orders.customer_id`                                 |
+| Collection      | composes     | Index          | `orders` composes `idx_orders_customer_id`                             |
+| Collection      | composes     | ValidationRule | `orders` composes the `chk_orders_total_positive` check constraint     |
+| Collection      | composes     | EventHandler   | `orders` composes the `orders_audit_trigger`                           |
+| Collection      | references   | Collection     | `orders` references `customers` (foreign key)                          |
+| Field           | composes     | Field          | `address` sub-document composes `address.city`                         |
+| Index           | aggregates   | Field          | `idx_orders_customer_date` aggregates `customer_id` and `created_at`   |
+| AccessPattern   | accesses     | Collection     | "list-orders-by-customer" accesses `orders`                            |
+| AccessPattern   | uses         | Index          | "list-orders-by-customer" uses `idx_orders_customer_date`              |
+| AccessPattern   | references   | Field          | "list-orders-by-customer" references `orders.customer_id`              |
+| View            | derives-from | Collection     | `active_users_view` derives from `users`                               |
+| View            | derives-from | View           | `quarterly_revenue_mv` derives from `monthly_revenue_mv`               |
+| StoredLogic     | accesses     | Collection     | `get_user_stats()` accesses `orders`                                   |
+| StoredLogic     | migrates     | Collection     | `migrate_2024_10_split_address()` migrates `customers`                 |
+| EventHandler    | references   | Field          | `orders_status_trigger` references `orders.status` (AFTER UPDATE OF)   |
+| EventHandler    | triggers     | StoredLogic    | `orders_audit_trigger` triggers `write_audit_row()`                    |
+| ValidationRule  | references   | Field          | `uq_users_email` references `users.email`                              |
+| ValidationRule  | cascades-to  | Collection     | `fk_order_items_order` (`ON DELETE CASCADE`) cascades to `order_items` |
+| RetentionPolicy | governs      | Collection     | "Audit Log Retention" governs `audit_log`                              |
+| RetentionPolicy | archives-to  | Collection     | "Audit Log Retention" archives to `audit_log_archive`                  |
 
-Cross-layer links are created via `dr relate`, not inline YAML attributes. Key relationships from the spec:
-
-**Outgoing (Data Store → Other Layers):**
-
-| Relationship                                         | Example                                       |
-| ---------------------------------------------------- | --------------------------------------------- |
-| `collection.realizes.api.schema`                     | Users collection → API response schema        |
-| `collection.maps-to.api.requestbody`                 | Orders collection → POST /orders body         |
-| `collection.serves.api.operation`                    | Products collection → GET /products operation |
-| `collection.implements.security.secureresource`      | PII collection → SecureResource policy        |
-| `collection.satisfies.security.dataclassification`   | Payments collection → PCI data class          |
-| `field.satisfies.security.dataclassification`        | email field → PII data classification         |
-| `field.requires.security.fieldaccesscontrol`         | SSN field → FieldAccessControl rule           |
-| `field.maps-to.api.parameter`                        | user_id field → API path parameter            |
-| `database.satisfies.security.securitypolicy`         | DB → encryption-at-rest policy                |
-| `database.depends-on.technology.systemsoftware`      | PostgreSQL DB → pg systemsoftware             |
-| `retentionpolicy.satisfies.security.retentionpolicy` | Retention rule → security retention policy    |
-
-**Incoming (Other Layers → Data Store):**
+---
 
-| Relationship                                           | Example                          |
-| ------------------------------------------------------ | -------------------------------- |
-| `application.applicationcomponent.serves → collection` | UserService → users collection   |
-| `technology.systemsoftware.depends-on → database`      | PostgreSQL technology → database |
+## Cross-Layer References
+
+Cross-layer links are created with `dr relationship add`, not inline YAML attributes.
+
+### Outgoing References (Data Store → Other Layers)
+
+| Source Type     | Predicate  | Target Type                       | Example                                                           |
+| --------------- | ---------- | --------------------------------- | ----------------------------------------------------------------- |
+| Collection      | realizes   | `business.businessobject`         | `orders` table realizes the "Customer Order" business object      |
+| Collection      | realizes   | `security.secureresource`         | `patients` collection realizes the "Patient Records" resource     |
+| Collection      | references | `security.dataclassification`     | `payments` collection references the "PCI" classification         |
+| Field           | references | `security.dataclassification`     | `users.email` references the "PII" classification                 |
+| Field           | requires   | `security.fieldaccesscontrol`     | `customers.ssn` requires the "SSN Masking" field control          |
+| Field           | maps-to    | `api.parameter`                   | `orders.id` maps to the `{orderId}` path parameter                |
+| Database        | depends-on | `technology.systemsoftware`       | "orders-db" depends on "PostgreSQL 16"                            |
+| Database        | depends-on | `technology.node`                 | "orders-db" depends on the "db-primary-01" node                   |
+| Database        | satisfies  | `security.securitypolicy`         | "orders-db" satisfies the "Encryption at Rest" policy             |
+| StoredLogic     | realizes   | `application.applicationfunction` | `calculate_discount()` realizes "Apply Promotions"                |
+| EventHandler    | triggers   | `application.applicationevent`    | "orders CDC stream" triggers "Order Placed"                       |
+| AccessPattern   | serves     | `application.applicationfunction` | "get-user-by-email" serves "Authenticate User"                    |
+| View            | maps-to    | `api.response`                    | `order_summary_view` maps to the `GET /orders/summary` response   |
+| RetentionPolicy | satisfies  | `security.retentionpolicy`        | "Audit Log Retention" satisfies the "SOC2 Audit Retention" policy |
+
+### Incoming References (Other Layers → Data Store)
+
+| Source Type                        | Predicate | Target Type    | Example                                                          |
+| ---------------------------------- | --------- | -------------- | ---------------------------------------------------------------- |
+| `application.applicationcomponent` | accesses  | Collection     | "OrderRepository" accesses `orders`                              |
+| `application.applicationfunction`  | accesses  | Collection     | "findOrdersByCustomer" accesses `orders`                         |
+| `application.applicationservice`   | accesses  | View           | "Reporting Service" accesses `monthly_revenue_mv`                |
+| `data-model.objectschema`          | maps-to   | Collection     | "User" schema maps to the `users` table                          |
+| `data-model.schemadefinition`      | maps-to   | Collection     | "AuditEntry" definition maps to `audit_log`                      |
+| `testing.testcoveragetarget`       | covers    | StoredLogic    | "Discount rules" coverage target covers `calculate_discount()`   |
+| `testing.testcasesketch`           | tests     | ValidationRule | "Reject negative total" sketch tests `chk_orders_total_positive` |
+| `apm.metricinstrument`             | monitors  | Database       | "db.client.connections.usage" monitors "orders-db"               |
+| `apm.span`                         | monitors  | Collection     | "SELECT orders" span monitors `orders`                           |
 
 ---
 
@@ -289,7 +338,7 @@ properties:
 - ❌ Using SQL-only concepts (Table, Column, Constraint) — use paradigm-neutral `collection`, `field`, `validationrule`
 - ❌ Skipping `AccessPattern` for NoSQL stores (DynamoDB, Cassandra) — define access patterns first
 - ❌ Nesting fields inline inside a collection element — `field` entities are always separate elements linked via `collection.composes.field`
-- ❌ Using invented `x-pii`, `x-json-schema`, or `x-apm-performance-metrics` attributes — these are not in the spec; use relationships (`field.satisfies.security.dataclassification`, `collection.realizes.api.schema`) instead
+- ❌ Using invented `x-pii`, `x-json-schema`, or `x-apm-performance-metrics` attributes — these are not in the spec; use relationships (`field satisfies security.dataclassification`, `data-model.objectschema maps-to collection`) instead
 - ❌ Using `ttlDays` / `archiveAfterDays` in retentionpolicy — use `retentionDuration` (ISO 8601, e.g. `"P365D"`) and `action` (enum: DELETE | ARCHIVE | ...)
 - ❌ Forgetting `RetentionPolicy` for regulated data
 - ❌ Not documenting `EventHandler` for CDC or change-triggered workflows

package/dist/integrations/claude_code/skills/dr_10_ux_layer/SKILL.md

@@ -139,20 +139,89 @@ EXPERIENCE TIER — specific to a view or experience
 
 ---
 
-## Cross-Layer Relationships
+## Intra-Layer Relationships
+
+Placement is `composes`: a view composes its sub-views, instances and action components, and an
+instance composes its nested instances, slots, chart series and table columns. Instances and placed
+sub-views `realizes` their library definition. Elements `applies` their layout, `binds-to` their data
+config and `uses` their error config. A state composes its outgoing transitions, which `flows-to`
+the next state. UX reaches other layers only through the interfaces and features a view realizes,
+the operations an action triggers and the data a data config maps to.
+
+| Source Type        | Predicate    | Target Type         | Example                                                       |
+| ------------------ | ------------ | ------------------- | ------------------------------------------------------------- |
+| UXApplication      | aggregates   | UXSpec              | "Storefront Web" aggregates the "Checkout Experience" spec    |
+| UXSpec             | aggregates   | View                | "Checkout Experience" aggregates the "Cart" view              |
+| UXSpec             | aggregates   | ExperienceState     | "Checkout Experience" aggregates the "Payment Pending" state  |
+| UXSpec             | uses         | UXLibrary           | "Checkout Experience" uses the "Design System" library        |
+| UXLibrary          | aggregates   | LibraryComponent    | "Design System" aggregates "Data Table"                       |
+| UXLibrary          | aggregates   | LibrarySubView      | "Design System" aggregates "Address Form Group"               |
+| View               | composes     | SubView             | "Cart" view composes the "Order Summary" panel                |
+| View               | composes     | ComponentInstance   | "Cart" view composes "Cart Items Table"                       |
+| View               | composes     | ActionComponent     | "Cart" view composes the "Checkout" button                    |
+| View               | applies      | LayoutConfig        | "Cart" view applies the "Two-Column Grid" layout              |
+| View               | binds-to     | DataConfig          | "Cart" view binds to "Cart Data"                              |
+| View               | uses         | ErrorConfig         | "Cart" view uses "Cart Load Error"                            |
+| SubView            | realizes     | LibrarySubView      | "Shipping Address" section realizes "Address Form Group"      |
+| SubView            | composes     | ComponentInstance   | "Order Summary" panel composes "Totals Card"                  |
+| ComponentInstance  | realizes     | LibraryComponent    | "Cart Items Table" realizes "Data Table"                      |
+| ComponentInstance  | binds-to     | DataConfig          | "Cart Items Table" binds to "Cart Data"                       |
+| ComponentInstance  | composes     | TableColumn         | "Cart Items Table" composes the "Quantity" column             |
+| ComponentInstance  | composes     | ChartSeries         | "Revenue Chart" composes the "Monthly Revenue" series         |
+| ComponentReference | references   | LibraryComponent    | "Primary Button Slot" references "Button" (variant `primary`) |
+| LibraryComponent   | composes     | LibraryComponent    | "Data Table" composes "Pagination Bar"                        |
+| LibraryComponent   | specializes  | LibraryComponent    | "Currency Input" specializes "Text Input"                     |
+| LibraryComponent   | uses         | StatePattern        | "Data Table" uses the "Loading / Loaded / Error" pattern      |
+| ActionPattern      | governs      | ActionComponent     | The "Submit" action pattern governs the "Checkout" button     |
+| ActionComponent    | triggers     | StateTransition     | "Checkout" button triggers "Begin Payment"                    |
+| ActionComponent    | navigates-to | View                | "Continue Shopping" link navigates to the "Catalog" view      |
+| ExperienceState    | composes     | StateTransition     | "Cart Ready" composes "Begin Payment"                         |
+| StateTransition    | flows-to     | ExperienceState     | "Begin Payment" flows to "Payment Pending"                    |
+| StateTransition    | triggers     | StateAction         | "Begin Payment" triggers "Disable Checkout Button"            |
+| StateAction        | realizes     | StateActionTemplate | "Show Spinner" realizes the "Show Loading Indicator" template |
+| StatePattern       | aggregates   | ExperienceState     | "Loading / Loaded / Error" aggregates "Loading"               |
+| StateTransition    | uses         | TransitionTemplate  | "Open Cart" uses the "Slide-In Drawer" template               |
+| DataConfig         | uses         | ErrorConfig         | "Cart Data" uses the "Cart Load Error" config                 |
 
-**Outgoing (UX → Other Layers):**
-
-- `motivation.*` → Motivation Layer (UX supports goals)
-- `business.*` → Business Layer (UX realizes business processes)
-- `api.*` → API Layer (API calls from components)
-- `data-model.*` → Data Model Layer (schema references for data-bound components)
-- `navigation.*` → Navigation Layer (routing to views)
-
-**Incoming (Other Layers → UX):**
+---
 
-- Navigation Layer → UX (routes point to views)
-- Business Layer → UX (business processes trigger UX flows)
+## Cross-Layer References
+
+### Outgoing References (UX → Other Layers)
+
+| Source Type      | Predicate  | Target Type                        | Example                                                         |
+| ---------------- | ---------- | ---------------------------------- | --------------------------------------------------------------- |
+| View             | realizes   | `product.feature`                  | "Cart" view realizes the "Shopping Cart" feature                |
+| View             | references | `business.businessobject`          | "Order Detail" view references the "Order" business object      |
+| View             | realizes   | `application.applicationinterface` | "Cart" view realizes the "Storefront Web UI" interface          |
+| View             | satisfies  | `motivation.requirement`           | "Checkout" view satisfies "Guest checkout must be supported"    |
+| View             | requires   | `security.permission`              | "Admin Orders" view requires the `orders:read` permission       |
+| View             | serves     | `business.businessrole`            | "Admin Orders" view serves the "Fulfillment Clerk" role         |
+| ActionComponent  | triggers   | `api.operation`                    | "Place Order" button triggers `POST /orders`                    |
+| ActionComponent  | requires   | `security.permission`              | "Refund" button requires the `orders:refund` permission         |
+| StateAction      | triggers   | `api.operation`                    | "Load Cart" on-enter action triggers `GET /cart`                |
+| DataConfig       | maps-to    | `api.response`                     | "Cart Data" maps to the `GET /cart` 200 response                |
+| DataConfig       | maps-to    | `api.requestbody`                  | "Checkout Form Data" maps to the `POST /orders` request body    |
+| DataConfig       | maps-to    | `data-model.objectschema`          | "Cart Data" maps to the "Cart" schema                           |
+| TableColumn      | maps-to    | `data-model.schemaproperty`        | "Quantity" column maps to the "quantity" property               |
+| TableColumn      | references | `security.fieldaccesscontrol`      | "Card Number" column references the "PAN Masking" control       |
+| ErrorConfig      | references | `api.response`                     | "Payment Declined" references the `POST /payments` 402 response |
+| LibraryComponent | depends-on | `technology.systemsoftware`        | "Data Table" depends on "React 18"                              |
+
+### Incoming References (Other Layers → UX)
+
+| Source Type                       | Predicate | Target Type     | Example                                                         |
+| --------------------------------- | --------- | --------------- | --------------------------------------------------------------- |
+| `navigation.route`                | maps-to   | View            | `/cart` route maps to the "Cart" view                           |
+| `navigation.navigationtransition` | triggers  | StateTransition | "Cart → Checkout" transition triggers "Begin Payment"           |
+| `navigation.navigationguard`      | triggers  | ExperienceState | "Require Login" guard triggers the "Signed Out" state           |
+| `testing.testcasesketch`          | tests     | View            | "Empty cart renders placeholder" tests the "Cart" view          |
+| `testing.testcasesketch`          | tests     | ActionComponent | "Checkout disabled when cart empty" tests the "Checkout" button |
+| `apm.span`                        | monitors  | View            | "page.load /cart" span monitors the "Cart" view                 |
+| `apm.metricinstrument`            | monitors  | ActionComponent | "checkout_click_count" monitors the "Checkout" button           |
+
+> Routing is modelled from the Navigation Layer: a `navigation.route` `maps-to` the view it shows,
+> rather than the view pointing at the route.
 
 ---
 
@@ -274,6 +343,13 @@ dr add ux dataconfig "Login Data" --attributes '{"source":"api","target":"ux.com
 
 # Add error config for failed login
 dr add ux errorconfig "Login Error" --description "Show inline error on auth failure"
+
+# Wire the elements together
+dr relationship add ux.view.login ux.componentinstance.login-form-instance --predicate composes
+dr relationship add ux.componentinstance.login-form-instance ux.librarycomponent.login-form --predicate realizes
+dr relationship add ux.statetransition.submit-clicked ux.experiencestate.submitting --predicate flows-to
+dr relationship add ux.componentinstance.login-form-instance ux.dataconfig.login-data --predicate binds-to
+dr relationship add ux.view.login ux.errorconfig.login-error --predicate uses
 ```
 
 ---

package/dist/integrations/claude_code/skills/dr_11_navigation_layer/SKILL.md

@@ -120,19 +120,75 @@ Activate when the user:
 
 ---
 
-## Cross-Layer Relationships
+## Intra-Layer Relationships
+
+A guard `evaluates` its condition, `triggers` its action on denial and `protects` what it guards. A
+transition leaves its source route (`flows-to`) and `navigates-to` its destination. Context variables
+are passive state that steps, guards, conditions, actions and transitions `accesses`. Navigation
+never reaches the data store directly, and reaches the business through the product workflows that
+flows and steps realize.
+
+| Source Type          | Predicate    | Target Type          | Example                                                       |
+| -------------------- | ------------ | -------------------- | ------------------------------------------------------------- |
+| NavigationGraph      | composes     | Route                | "Web App Navigation" composes "User Profile Route"            |
+| NavigationGraph      | composes     | NavigationTransition | "Web App Navigation" composes "Cart To Shipping"              |
+| NavigationGraph      | aggregates   | NavigationFlow       | "Web App Navigation" aggregates "Checkout Flow"               |
+| NavigationGraph      | aggregates   | NavigationGuard      | "Web App Navigation" aggregates "Auth Guard"                  |
+| NavigationGraph      | aggregates   | BreadcrumbConfig     | "Web App Navigation" aggregates "Profile Breadcrumb"          |
+| Route                | composes     | RouteMeta            | "User Profile Route" composes "Profile Route Meta"            |
+| Route                | aggregates   | Route                | "Settings Route" aggregates "Settings Security Route"         |
+| Route                | navigates-to | Route                | "Legacy Account Route" navigates-to "Account Settings Route"  |
+| Route                | flows-to     | NavigationTransition | "Cart Route" flows-to "Cart To Shipping" (its source route)   |
+| BreadcrumbConfig     | references   | RouteMeta            | "Profile Breadcrumb" references "Profile Route Meta" (labels) |
+| BreadcrumbConfig     | references   | Route                | "Profile Breadcrumb" references "Dashboard Route"             |
+| NavigationGuard      | protects     | Route                | "Auth Guard" protects "User Profile Route"                    |
+| NavigationGuard      | evaluates    | GuardCondition       | "Auth Guard" evaluates "Is Authenticated"                     |
+| NavigationGuard      | triggers     | GuardAction          | "Auth Guard" triggers "Redirect To Login"                     |
+| GuardCondition       | accesses     | ContextVariable      | "Is Authenticated" accesses "Session Token"                   |
+| GuardAction          | navigates-to | Route                | "Redirect To Login" navigates-to "Login Route"                |
+| NavigationFlow       | composes     | FlowStep             | "Checkout Flow" composes "Cart Review Step"                   |
+| NavigationFlow       | aggregates   | ContextVariable      | "Checkout Flow" aggregates "Cart ID"                          |
+| NavigationGuard      | protects     | NavigationFlow       | "Cart Not Empty Guard" protects "Checkout Flow"               |
+| FlowStep             | navigates-to | Route                | "Cart Review Step" navigates-to "Cart Route"                  |
+| FlowStep             | accesses     | ContextVariable      | "Payment Step" accesses "Cart ID"                             |
+| NavigationTransition | navigates-to | Route                | "Cart To Shipping" navigates-to "Shipping Route"              |
+| NavigationGuard      | protects     | NavigationTransition | "Valid Address Guard" protects "Shipping To Payment"          |
 
-**Outgoing (Navigation → Other Layers):**
-
-- `view-ref` → UX Layer (which view does this route show?)
-- `business.realizes-process` → Business Layer (what process does this flow realize?)
-- `security.required-roles` → Security Layer (authorization requirements)
-- `apm.flow-metrics` → APM Layer (navigation analytics)
-
-**Incoming (Other Layers → Navigation):**
+---
 
-- UX Layer → Navigation (views reference routes)
-- Business Layer → Navigation (processes trigger flows)
+## Cross-Layer References
+
+### Outgoing References (Navigation → Other Layers)
+
+| Source Type          | Predicate  | Target Type                        | Example                                                          |
+| -------------------- | ---------- | ---------------------------------- | ---------------------------------------------------------------- |
+| Route                | maps-to    | `ux.view`                          | "User Profile Route" maps-to "User Profile View"                 |
+| RouteMeta            | uses       | `ux.layoutconfig`                  | "Profile Route Meta" uses "Authenticated Shell Layout"           |
+| NavigationTransition | triggers   | `ux.statetransition`               | "Cart To Shipping" triggers "Cart Submitted Transition"          |
+| Route                | requires   | `security.permission`              | "Admin Users Route" requires "users:read"                        |
+| NavigationGuard      | requires   | `security.role`                    | "Auth Guard" requires "Authenticated User"                       |
+| NavigationGuard      | realizes   | `security.securitypolicy`          | "Admin Guard" realizes "Admin Access Policy"                     |
+| ContextVariable      | maps-to    | `api.parameter`                    | "User ID" maps-to "userId path parameter"                        |
+| Route                | lazy-loads | `application.applicationcomponent` | "Reports Route" lazy-loads "Reports Module"                      |
+| Route                | uses       | `application.applicationservice`   | "Order Detail Route" uses "Order Service" (resolver)             |
+| NavigationFlow       | realizes   | `product.userworkflow`             | "Onboarding Flow" realizes "New User Onboarding"                 |
+| FlowStep             | realizes   | `product.workflowstep`             | "Payment Step" realizes "Enter Payment Details"                  |
+| Route                | satisfies  | `motivation.requirement`           | "Order History Route" satisfies "Customers Can View Past Orders" |
+
+### Incoming References (Other Layers → Navigation)
+
+| Source Type                  | Predicate | Target Type          | Example                                                             |
+| ---------------------------- | --------- | -------------------- | ------------------------------------------------------------------- |
+| `api.operation`              | serves    | Route                | "GET /users/{id}" serves "User Profile Route" (its loader calls it) |
+| `api.operation`              | serves    | NavigationGuard      | "GET /auth/session" serves "Auth Guard"                             |
+| `apm.span`                   | monitors  | Route                | "Route Change Span" monitors "User Profile Route"                   |
+| `apm.span`                   | monitors  | NavigationFlow       | "Checkout Journey Span" monitors "Checkout Flow"                    |
+| `apm.metricinstrument`       | monitors  | Route                | "route_load_time" monitors "User Profile Route"                     |
+| `apm.metricinstrument`       | monitors  | NavigationTransition | "checkout_step_dropoff" monitors "Shipping To Payment"              |
+| `testing.testcasesketch`     | tests     | Route                | "Deep Link To Profile" tests "User Profile Route"                   |
+| `testing.testcasesketch`     | tests     | NavigationGuard      | "Anonymous User Redirected" tests "Auth Guard"                      |
+| `testing.testcasesketch`     | tests     | NavigationFlow       | "Complete Checkout" tests "Checkout Flow"                           |
+| `testing.testcoveragetarget` | covers    | Route                | "User Profile" target covers "User Profile Route"                   |
 
 ---
 
@@ -205,7 +261,6 @@ name: "User Profile Route"
 type: route
 properties:
   path: /profile/:userId
-  view-ref: ux.view.user-profile
   guards:
     - navigation.navigationguard.authentication
     - navigation.navigationguard.profile-ownership
@@ -226,15 +281,15 @@ properties:
   dataMapping:
     - source: route.params.userId
       target: view.data.userId
-  security:
-    required-roles:
-      - security.role.authenticated-user
-  business:
-    realizes-process: business.process.profile-management
-  apm:
-    flow-metrics:
-      - apm.metric.profile-view-count
-      - apm.metric.profile-load-time
+```
+
+Record the cross-layer links as relationships, not as properties:
+
+```bash
+dr relationship add navigation.route.user-profile ux.view.user-profile --predicate maps-to
+dr relationship add navigation.navigationguard.authentication security.role.authenticated-user --predicate requires
+dr relationship add api.operation.get-user navigation.route.user-profile --predicate serves
+dr relationship add apm.metricinstrument.profile-load-time navigation.route.user-profile --predicate monitors
 ```
 
 ---
@@ -280,8 +335,12 @@ properties:
     - cartId
     - selectedAddress
     - paymentMethod
-  business:
-    realizes-process: business.process.checkout
+```
+
+```bash
+dr relationship add navigation.navigationflow.checkout product.userworkflow.checkout --predicate realizes
+dr relationship add navigation.navigationflow.checkout navigation.flowstep.cart-review --predicate composes
+dr relationship add navigation.flowstep.cart-review navigation.route.cart --predicate navigates-to
 ```
 
 ---
@@ -314,5 +373,5 @@ If any type has ZERO elements, explicitly decide:
 - ❌ Not decomposing guards into conditions (`guardcondition`) and actions (`guardaction`) — model these as separate elements
 - ❌ Complex flows without explicit `flowstep` elements — each step in a flow should be a distinct `flowstep`
 - ❌ Missing `routemeta` for protected routes — auth requirements belong in `routemeta`, not embedded in route properties
-- ❌ Missing cross-layer links to UX views (`view-ref`) and business processes (`realizes-process`)
+- ❌ Missing cross-layer links — each route should `maps-to` a `ux.view`, and flows should `realizes` a `business.businessprocess` or `product.userworkflow`
 - ❌ No error/fallback routes defined — model these as `route` with `type: redirect`