@jahia/agentic 0.3.0 → 0.4.0

package/dist/windsurf/.windsurf/skills/jahia-dev-define-content-type/SKILL.md

@@ -1,536 +1,93 @@
 ---
 name: jahia-dev-define-content-type
 description: Creates a Jahia CND content type definition from a natural language description. Use when asked to model content, create a new content type, or define node types.
-allowed-tools: Bash, Read, Write, Edit
+allowed-tools: Bash, Read
 ---
 
 ## Overview
 
-All Jahia development starts with content modeling. Content types are defined in **CND files** (Compact Node Definition). Each component follows the **Single Directory Component (SDC)** pattern: one folder per component, containing a `definition.cnd`, a view, and optional CSS.
+Orchestrates CND authoring by delegating to the `@jahia-cnd-author` sub-agent, which handles all CND syntax in an isolated context window. Your job here is to capture the spec and assemble the delegation call.
 
 ---
 
-## Step 0 — Write a spec before coding
+## Step 0 — Capture the spec
 
-Before writing any CND, capture the content type spec. Ask the user to confirm:
+Confirm with the user (or infer from context):
 
 | Field | Answer |
 |---|---|
-| **Name** | e.g. `BlogPost` |
+| **Component name** | e.g. `HeroSection` |
 | **Description** | What is this type for? |
 | **Fields** | name / type / i18n? / mandatory? |
-| **Views** | default only, or also: small / card / fullPage |
-| **Used where** | Inside an Area? Nested in another type? |
+| **Repeatable children?** | CTA buttons, feature items, testimonials? |
+| **Views** | default only, or also: card / fullPage |
+| **Used where** | In a page area? Child of another component? |
 
-Only proceed to the CND once this spec is agreed.
+For modeling decisions (semantic vs generic, children vs weakreference, mixin extraction), LOAD references/modeling-decisions.md.
 
 ---
 
-## Step 0b — Modeling decisions
+## Step 1 — Resolve module context
 
-### Semantic vs generic types
-
-| Use **semantic types** for… | Use **generic types** for… |
-|---|---|
-| Business entities: articles, team members, events | Visual composition: banners, feature rows |
-| Items that appear in listings | One-off sections, layout containers |
-| Anything reused across pages | Unique per-page UI blocks |
-
-### Children vs weakreference
-
-| Use **child nodes** when… | Use **weakreference** when… |
-|---|---|
-| Parent is the visual container (e.g. CTA buttons inside a hero) | Linking to content managed elsewhere |
-| Children have no life outside the parent | Many-to-many relationships |
-| You always create the children together | Content editors need to reuse the referenced item |
-
-### Mixins are the primary reuse mechanism
-
-**Mixins are how you share fields across multiple content types.** Whenever a set of properties appears on more than one type — a CTA block, a link, a badge, a price field — extract them into a mixin. This avoids duplication and keeps CND definitions focused.
-
-The module-level `settings/definitions.cnd` defines all mixins and base types. Component-level `definition.cnd` files define the content types that extend them.
-
-**Example: reusable CTA mixin**
-
-```cnd
-// settings/definitions.cnd
-[nsmix:cta] mixin
- - ctaLabel (string) i18n
- - ctaType (string, choicelist[linkTypeInitializer]) = 'none' autocreated mandatory
- // j:linknode and j:url are injected automatically — do NOT declare them
-```
-
-Any content type that needs a call-to-action simply extends `nsmix:cta`:
-
-```cnd
-// src/components/Hero/definition.cnd
-[ns:hero] > jnt:content, nsmix:component, nsmix:cta
- - title (string) i18n mandatory primary
- - subtitle (string, textarea) i18n
- - backgroundImage (weakreference, picker[type='image']) < jmix:image
-```
-
-The `ctaLabel`, `ctaType`, `j:linknode`, `j:url` fields are inherited and ready to use in the view without duplicating a single line of CND. Build your mixin library from day one — once two types need the same field, it belongs in a mixin.
-
-**Common reusable mixin patterns:**
-
-| Mixin | Properties it adds | When to use |
-|---|---|---|
-| `nsmix:cta` | `ctaLabel`, `ctaType` (+ injected `j:linknode`/`j:url`) | Any type with a button or link |
-| `nsmix:badge` | `badgeText`, `badgeColor` | Cards, teasers, any labelled content |
-| `nsmix:seo` | `metaTitle`, `metaDescription`, `seoKeywords` | Any `jmix:mainResource` type |
-| `nsmix:media` | `image` (weakreference), `imageAltText`, `imageCaption` | Any type with a visual asset |
-| `nsmix:trackable` | `analyticsId`, `trackingLabel` | Any CTA or interactive element |
-
-**Generic container — accept any droppable child:**
+```bash
+# Get namespace prefix
+grep -h "^<" settings/definitions.cnd | head -1
 
-```cnd
-[ns:gridRow] > jnt:content, nsmix:component
- - columns (long) = '3' autocreated mandatory < '1', '2', '3', '4'
- + * (jmix:droppableContent)   // ← accepts ANY droppable component as a child
+# Check for two-tier mixin (pageComponent)
+grep "pageComponent" settings/definitions.cnd
 ```
 
-Use `+ * (jmix:droppableContent)` for layout containers that should not restrict which components editors can place inside them.
-
 ---
 
-### Never use `jmix:droppableContent` directly
+## Step 2 — REQUIRED: Delegate to `@jahia-cnd-author`
 
-Always define a custom component mixin for your module and extend it:
+**Do not write CND directly.** Writing CND from memory always produces incorrect Jahia-specific patterns. The sub-agent reads reference files containing the exact syntax — you cannot reproduce this from training data.
 
-```cnd
-// In settings/definitions.cnd
-[namespacemix:component] > jmix:droppableContent, jmix:accessControllableContent mixin
-```
-
-Then all component types extend `namespacemix:component` — **never** `jmix:droppableContent` directly. This is what controls which types appear in the content picker.
-
-> Add `jmix:accessControllableContent` to the base mixin — it enables per-component access control in jcontent, allowing editors to restrict who can see or edit individual components.
-
-### Two-tier mixin system: `component` vs `pageComponent`
-
-If the module uses a custom area type with `pageComponent` (see `jahia-dev-create-page-template`), there are two tiers:
+Invoke the sub-agent with the complete structured spec:
 
-```cnd
-[namespacemix:component]     > jmix:droppableContent mixin   // general droppable
-[namespacemix:pageComponent] > namespacemix:component mixin  // for page areas only
 ```
+@jahia-cnd-author
 
-**When creating a new content type, choose the right mixin:**
-
-| Component will be… | Extend |
-|---|---|
-| Dropped in page areas (hero, sections, cards on a page) | `namespacemix:pageComponent` |
-| Used only as a child of another component (e.g. CTA inside a hero) | `namespacemix:component` |
-| A `jmix:mainResource` type stored in a content folder and listed programmatically | `namespacemix:component` |
-
-> ⚠️ A component that extends only `namespacemix:component` **cannot be dropped in page areas** that use a `namespacemix:pageComponent` area type. This is the most common cause of editors not being able to contribute content to a new page.
-
----
-
-## Step 1 — Identify the component location
-
-CND files can live in two places:
-
-- **Component-level** (preferred): `src/components/<Category>/<Name>/definition.cnd`
-- **Module-level**: `settings/definitions.cnd` (for mixins and shared base types)
-
-For a new standalone component, always create a component-level `definition.cnd`.
-
----
-
-## Step 2 — Determine the namespace
-
-Check `settings/definitions.cnd` for the module's namespace declaration. It looks like:
-
-```
-<ns = 'http://www.mymodule.com/...'>
+Component: <PascalCase name>
+Namespace prefix: <ns>
+Module path: <absolute path to module root>
+Fields:
+  - <fieldName>: <type description> [mandatory] [i18n] [multiple]
+  - ... (one line per field)
+Children: <describe any repeatable sub-items, e.g. "CTA buttons with label + link">
+Usage: <where this component appears, e.g. "dropped in page areas">
 ```
 
-The short prefix (e.g. `ns`) is the namespace to use for all node types in this module.
+Wait for the agent to report back before proceeding.
 
 ---
 
-## Step 3 — Write the CND definition
+## Step 2b — Validate the CND
 
-### Basic template
+After `@jahia-cnd-author` reports back, invoke `/jahia-dev-review-cnd` on the written file:
 
-```cnd
-[namespace:typeName] > jnt:content, namespacemix:component
- - propertyName (type) [hints] [attributes] [< constraint]
- + childName (namespace:childType)
 ```
-
-### Property types
-
-| Type | Usage |
-|---|---|
-| `string` | Single-line text |
-| `string, textarea` | Multi-line text |
-| `string, richtext` | Rich text editor |
-| `weakreference, picker[type='image']` | Image picker |
-| `weakreference multiple` | List of references (e.g. links to multiple pages) |
-| `string, choicelist[linkTypeInitializer]` | Link type discriminator (internal page / external URL / none) — **special initializer, not a value list** |
-| `string, choicelist` with `< 'val1', 'val2'` constraints | Dropdown with fixed choices (see below) |
-| `date` | Date picker |
-| `boolean` | Checkbox |
-| `double` | Decimal number (e.g. latitude/longitude) |
-| `long` | Integer number |
-| `string multiple` | List of strings |
-
-### Fixed-choice dropdowns (constrained string)
-
-Use `(string, choicelist)` combined with value constraints (`< 'val1', 'val2'`) to render a dropdown in the editor. **Do NOT use `choicelist[val1,val2]`** — that syntax is invalid:
-
-```cnd
-[namespace:article] > jnt:content
- - difficulty (string, choicelist) i18n < 'beginner', 'intermediate', 'advanced'
- - product (string, choicelist) i18n < 'jahia', 'jexperience', 'cloud'
-```
-
-### Choicelist initializer variants
-
-`choicelist[...]` takes an **initializer keyword**, not a value list. Valid initializers:
-
-| Initializer | What editor sees |
-|---|---|
-| `choicelist[linkTypeInitializer]` | Internal page / External URL / None link picker |
-| `choicelist[nodes=/path/to/folder;type=jnt:content]` | Picker populated from JCR nodes under a path |
-| `choicelist[componentTypes=jnt:page]` | Picker showing all registered views of a node type |
-| `choicelist[country]` | Country selector (ISO codes with localized labels) |
-| `choicelist[menus]` | Picker for existing menus defined on the site |
-| `choicelist[resourceBundle]` | Labels come from `.properties` file keys matching `ns_type.field.value` |
-
-```cnd
-// Country picker — stores ISO code, shows localized country name in editor
-- country (string, choicelist[country]) i18n
-
-// Node picker — editor selects from nodes under a specific folder
-- template (string, choicelist[nodes=/sites/mySite/templates;type=jnt:content])
-
-// Component type picker — shows all views of jnt:page registered in the module
-- pageLayout (string, choicelist[componentTypes=jnt:page])
-
-// Resource bundle labels — values come from .properties keys
-- status (string, choicelist[resourceBundle]) i18n < 'draft', 'review', 'published'
-// In .properties: namespace_typeName.status.draft=Draft
-//                 namespace_typeName.status.review=In Review
-//                 namespace_typeName.status.published=Published
+/jahia-dev-review-cnd <module-path>/src/components/<Category>/<Name>/definition.cnd
 ```
 
-> ⚠️ `choicelist[linkTypeInitializer]` is a **special initializer keyword** (not a value list) — see the link pattern section below. For fixed lists without dynamic labels, always use `(string, choicelist)` + `< 'val1', 'val2'`.
-
-Use `< "[-90,90]"` to restrict a numeric property to a range:
-
-```cnd
-- latitude (double) mandatory < "[-90,90]"
-- longitude (double) mandatory < "[-180,180]"
-```
-
-### `weakreference multiple` vs child nodes
-
-| Use `weakreference multiple` when… | Use child nodes when… |
-|---|---|
-| Each item is just a reference (a page link, an image) | Each item has multiple properties (label + URL) |
-| The list is simpler to author and implement | Items need a rich editing interface |
-
-```cnd
-// Simpler: list of page links (weakreference multiple)
-[namespace:footer] > jnt:content, namespacemix:component
- - links (weakreference) multiple < jnt:page
-
-// More flexible: each CTA has label + link (child nodes)
-[namespace:heroSection] > jnt:content, namespacemix:component
- + * (namespace:heroCallToAction)
-```
-
-Render a `weakreference multiple` list in the view:
-
-```tsx
-// links is JCRNodeWrapper[] | undefined
-{links?.filter(link => link !== null).map(link => (
-  <a key={link.getPath()} href={buildNodeUrl(link)}>
-    {link.getDisplayableName()}
-  </a>
-))}
-```
-
-### Common attributes
-
-| Attribute | Meaning |
-|---|---|
-| `i18n` | Translatable per language |
-| `mandatory` | Required field |
-| `multiple` | Allows a list of values |
-| `autocreated` | Auto-creates the property on node creation — always combine with a default: `= 'value'` |
-| `primary` | Marks the most important field — Jahia's editor UI highlights it. One per type only. |
-| `orderable` | Allows reordering child nodes |
-
-```cnd
-[ns:blogPost] > jnt:content, nsmix:component
- - title (string) i18n mandatory primary               // ← highlighted in the editor
- - country (string, choicelist[country]) = 'US' autocreated mandatory  // ← pre-populated on create
-```
-
-### `linkTypeInitializer` — the full link pattern
-
-`choicelist[linkTypeInitializer]` creates a link picker where the editor selects *internal page*, *external URL*, or *none*. Declare **only the `j:linkType` field** in the CND — the companion fields `j:linknode` and `j:url` are **added automatically by Jahia's mixins** at runtime. Do NOT add them to your CND.
-
-```cnd
-[namespace:callToAction] > jnt:content, namespacemix:component
- - label (string) i18n mandatory
- - j:linkType (string, choicelist[linkTypeInitializer]) mandatory
- // ✅ Stop here — j:linknode and j:url are injected by Jahia, not declared by you
-```
-
-In `types.ts`, use a **discriminated union** — the mixin fields ARE available at runtime as props:
-
-```ts
-import type { JCRNodeWrapper } from "org.jahia.services.content";
-
-export type Props =
-  | { label?: string; "j:linkType": "none" }
-  | { label?: string; "j:linkType": "internal"; "j:linknode"?: JCRNodeWrapper }
-  | { label?: string; "j:linkType": "external"; "j:url"?: string; "j:linkTitle"?: string };
-```
-
-In the view, use a `switch` on `props["j:linkType"]` (see `jahia-dev-create-view` skill).
-
-### i18n rule
-
-**Default to `i18n` on every user-facing field** — titles, subtitles, body text, button labels, alt text, captions, people names. Even on monolingual sites, adding `i18n` from the start avoids costly CND migrations later.
-
-> ⚠️ **Child nodes do not support `i18n`.** The content tree is shared across all languages. If you need locale-specific child content, use per-language **visibility conditions** in the Jahia editor (Advanced Editing → Visibility → Languages) instead.
-
-> Under the hood: non-i18n fields are stored directly on the node; i18n fields are stored as properties of auto-created `jnt:translation_<language>` child nodes. You don't manage these directly, but knowing this helps when debugging missing translated values.
-
-### Common mixins to extend
-
-| Mixin | Adds |
-|---|---|
-| `jnt:content` | Base type for all user content (always include) |
-| `namespacemix:component` | Makes this type available as a droppable component in Page Builder |
-| `mix:title` | Adds a `jcr:title` field |
-| `jmix:mainResource` | Makes the node accessible at its own URL — use only for content that needs **both a listing card AND a full detail page** (e.g. blog posts). Do not add to navigation-only or visual composition types. |
-| `jmix:hiddenType` | Hides a type from the Page Builder component picker (use for structural/container nodes editors should not add manually). Prefer over `jmix:studioOnly` which can cause silent rendering issues. |
-| `jmix:accessControllableContent` | Enables per-component access control in jcontent — add to the base module mixin |
-| `jmix:image` | Constraint: only image nodes |
-| `jmix:link` | Built-in link type |
-
-### Constraints
-
-- `< jmix:image` — restricts a weakreference to image nodes only
-- `< namespace:typeName` — restricts child nodes to a specific type
-
-**Regex constraints** — validate a `string` field against a pattern:
-
-```cnd
-// Email address (or empty — regex starts with ^$ to allow clearing the field)
-- contactEmail (string) < '^$|[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}'
-
-// URL-safe slug — lowercase letters, digits, hyphens only
-- slug (string) < '^[a-z0-9-]+$'
-
-// Must start with http:// or https://
-- externalUrl (string) < '^https?://'
-```
-
-**Date-range constraints** — bound a `date` field to a window. Use `(` / `)` for exclusive bounds, `[` / `]` for inclusive. Leave either side empty for open-ended:
-
-```cnd
-// Any date after 2020-01-01 (exclusive lower bound, no upper bound)
-- eventDate (date, datepicker) < '(2020-01-01T00:00:00.000,)'
-
-// From 2020 onwards inclusive (events can't be backdated before the platform launched)
-- startDate (date, datepicker) < '[2020-01-01T00:00:00.000,]'
-
-// Bounded window — exclusive on both sides
-- campaignDate (date, datepicker) < '(2020-01-01T00:00:00.000,2030-12-31T00:00:00.000)'
-```
-
-### Example — Hero Section with CTA (link pattern)
-
-```cnd
-[ns:heroSection] > jnt:content, nsmix:component
- - title (string) i18n mandatory
- - subtitle (string, textarea) i18n mandatory
- - background (weakreference, picker[type='image']) mandatory < jmix:image
- + * (ns:heroCallToAction)
-
-[ns:heroCallToAction] > jnt:content, nsmix:component
- - title (string) i18n mandatory
- - j:linkType (string, choicelist[linkTypeInitializer]) mandatory
- // j:linknode and j:url are injected by Jahia — do not declare them
-```
-
-### Example — Blog Post
-
-```cnd
-[ns:blogPost] > jnt:content, mix:title, jmix:mainResource, nsmix:component
- - subtitle (string) i18n mandatory
- - authors (string) multiple
- - cover (weakreference, picker[type='image']) mandatory < jmix:image
- - body (string, richtext) i18n mandatory
- - publicationDate (date)
-```
-
----
-
-## Step 4 — Create a `types.ts` file
-
-For each new content type, create a `types.ts` alongside the `definition.cnd` to define the TypeScript props interface. This will be imported by views.
-
-> ⚠️ **All props must use `?:` (optional)** — even mandatory CND fields. Jahia does not guarantee a value is present at render time (e.g. content created before a field was added, or incomplete saves). If a view uses a prop without guarding it, it will crash at runtime.
-
-```ts
-import type { JCRNodeWrapper } from "org.jahia.services.content";
-
-export interface Props {
-  title?: string;
-  subtitle?: string;
-  background?: JCRNodeWrapper;
-}
-```
-
-Map CND types to TypeScript:
-
-| CND type | TypeScript type |
-|---|---|
-| `string` | `string` |
-| `string` multiple | `string[]` |
-| `weakreference` | `JCRNodeWrapper` |
-| `weakreference` multiple | `JCRNodeWrapper[]` |
-| `date` | `string` (ISO 8601) |
-| `boolean` | `boolean` |
-| `double` | `number` |
-| `long` | `number` |
-
-All fields use `?:` regardless of whether they are mandatory in the CND.
+If the review reports errors, send them back to `@jahia-cnd-author` to fix. Do not proceed until the review is clean.
 
 ---
 
-## Step 5 — Add UI translations and icon
-
-Editors see raw technical names without translations. Always add labels for every new content type.
-
-### Translations
-
-Open `settings/resources/<module-name>.properties` (English) and `<module-name>_fr.properties` (French) and add:
-
-```properties
-# Node type label (shown in the content picker and editor)
-namespace_typeName=Human-readable name
-
-# Field labels
-namespace_typeName.fieldName=Field label
-namespace_typeName.fieldName.ui.tooltip=Optional tooltip shown next to the field in the editor.
-
-# choicelist[resourceBundle] option labels
-namespace_typeName.fieldName.optionKey=Option label
-```
-
-All `ui.tooltip` values support basic HTML. Escape `<` and `>` as `&lt;` and `&gt;`.
-
-> For `choicelist[resourceBundle]` fields, the constraint values (e.g. `< 'house', 'apartment'`) must match the property keys (e.g. `namespace_type.field.house=House`).
+## Step 3 — Continue with deployment
 
-### Content editor forms (fieldsets)
-
-For fine-grained control over how fields appear in Jahia's content editor UI — changing a `string` to a radio button, reordering fields, grouping fields into sections — add a JSON fieldset definition:
-
-```
-settings/content-editor-forms/fieldsets/<cnd-namespace>_<typeName>.json
-```
-
-Example — override `ctaTarget` to render as a radio group and `ctaVariant` as a select:
-
-```json
-{
-  "nodeType": "ns:card",
-  "priority": 1,
-  "sections": [{
-    "name": "content",
-    "fieldSets": [{
-      "name": "ns:card",
-      "fields": [
-        {
-          "name": "ctaTarget",
-          "selectorType": "RadioChoiceList"
-        },
-        {
-          "name": "ctaVariant",
-          "selectorType": "Choicelist",
-          "selectorOptions": [{ "name": "context", "value": "true" }]
-        }
-      ]
-    }]
-  }]
-}
-```
-
-`selectorType` overrides the default editor widget for the field. Common overrides:
-
-| `selectorType` | Use for |
-|---|---|
-| `RadioChoiceList` | Short fixed-value lists (2–4 options) |
-| `Choicelist` | Longer dropdowns, dynamic lists |
-| `RichText` | Force rich text editor on a `string, richtext` property |
-| `DateTimePicker` | Date + time (vs date only) |
-| `Tag` | Free-form tag input |
-
-Fieldset files are optional — only create them when the default editor rendering is insufficient.
-
-### Icon
-
-Create a 32×32 PNG icon at:
-
-```
-settings/content-types-icons/<cnd-namespace>_<typeName>.png
-```
-
-The prefix is the **CND namespace** (e.g. `ns`, `nsmix`), **not** the module name. For example:
-- `ns_heroSection.png` ✅
-- `my-module_heroSection.png` ❌ (module name with hyphen — wrong)
-
-You can source free icons from [flaticon.com](https://www.flaticon.com/) (download at 32px). If no icon is available, copy an existing one as a placeholder — editors will see a blank space otherwise.
-
----
-
-## Step 6 — Deploy to Jahia
-
-After creating or modifying a `definition.cnd`, build and deploy the module:
-
-```bash
-# Always use this — never use yarn dev from an agent (it's interactive-only)
-yarn build && yarn jahia-deploy
-```
-
-If Jahia rejects the type definition (e.g. breaking change), use the **Installed definitions browser** to remove the old definition first:
-> http://localhost:8080/modules/tools/definitionsBrowser.jsp
+After the CND review is PASS, proceed with:
+- Add UI translations (`/jahia-dev-build-component` handles this if invoked from there)
+- `yarn build && yarn jahia-deploy`
+- Verify the type appears in Jahia's content editor
 
 ---
 
 ## Validation checklist
-- [ ] Spec confirmed before writing CND (name, fields, views, usage)
-- [ ] Namespace matches the module (check `settings/definitions.cnd`)
-- [ ] Extends `jnt:content` and appropriate mixins
-- [ ] Uses `namespacemix:component` or `namespacemix:pageComponent` — **never** `jmix:droppableContent` directly
-- [ ] All required properties have the `mandatory` attribute
-- [ ] All user-facing string/text fields have `i18n` (default to always)
-- [ ] Structural/container types have `jmix:hiddenType` (not shown in picker) — do NOT use `jmix:studioOnly`
-- [ ] `jmix:mainResource` only used for listing + detail content (not visual composition)
-- [ ] `types.ts` created with correct TypeScript types
-- [ ] Views handle null/missing values gracefully (mandatory does not guarantee a value)
-- [ ] Translation keys added to `.properties` files (EN + FR minimum)
-- [ ] Icon created at `settings/content-types-icons/<namespace>_<typeName>.png`
-- [ ] `yarn build && yarn jahia-deploy` run and type appears in Jahia content editor with correct label and icon
-
-## Troubleshooting
-> https://academy.jahia.com/tutorials-get-started/front-end-developer/making-a-hero-section
-
-## References
-
-- Native Jahia mixins & node types: https://github.com/Jahia/jahia/tree/master/war/src/main/webapp/WEB-INF/etc/repository/nodetypes
-- Developer training: https://github.com/Jahia/developer-training/blob/main/js-training/slides.md
-- JavaScript modules monorepo: https://github.com/Jahia/javascript-modules
 
-> For CND questions about native mixins (e.g. does `jmix:nolive` exist?), fetch the nodetypes directory above to verify before using.
+- [ ] Spec confirmed before delegation
+- [ ] `@jahia-cnd-author` reported PASS (no errors)
+- [ ] Translation keys added to `.properties` files
+- [ ] Icon created at `settings/content-types-icons/<ns>_<typeName>.png`
+- [ ] `yarn build && yarn jahia-deploy` succeeded
+- [ ] Type appears in Jahia content editor with correct label and icon

package/dist/windsurf/.windsurf/skills/jahia-dev-define-content-type/references/modeling-decisions.md

@@ -0,0 +1,52 @@
+# CND Modeling Decisions
+
+## Semantic vs generic types
+
+| Use **semantic types** for… | Use **generic types** for… |
+|---|---|
+| Business entities: articles, team members, events | Visual composition: banners, feature rows |
+| Items that appear in listings | One-off sections, layout containers |
+| Anything reused across pages | Unique per-page UI blocks |
+
+## Children vs weakreference
+
+| Use **child nodes** when… | Use **weakreference** when… |
+|---|---|
+| Parent is the visual container (e.g. CTA buttons inside a hero) | Linking to content managed elsewhere |
+| Children have no life outside the parent | Many-to-many relationships |
+| You always create the children together | Content editors need to reuse the referenced item |
+| Each item has multiple properties (label + link) | Each item is just a reference (a page, an image) |
+
+## Mixins are the primary reuse mechanism
+
+Whenever a set of properties appears on more than one type, extract them into a mixin in `settings/definitions.cnd`.
+
+Common reusable mixin patterns:
+
+| Mixin | Properties it adds | When to use |
+|---|---|---|
+| `nsmix:cta` | `ctaLabel`, `j:linkType` | Any type with a button or link |
+| `nsmix:badge` | `badgeText`, `badgeColor` | Cards, teasers, labelled content |
+| `nsmix:seo` | `metaTitle`, `metaDescription` | Any `jmix:mainResource` type |
+| `nsmix:media` | `image` (weakreference) | Any type with a visual asset — alt text comes from the image node's `jcr:title`, never add a separate imageAlt property |
+
+Example reusable CTA mixin:
+
+```cnd
+[nsmix:cta] mixin
+ - ctaLabel (string) i18n
+ - j:linkType (string, choicelist[linkTypeInitializer]) = 'none' autocreated mandatory
+ // j:linknode and j:url are injected automatically
+```
+
+Any component that needs a CTA extends `nsmix:cta` — no property duplication.
+
+## `jmix:mainResource` — when NOT to use it
+
+Only for content that needs **both** a listing card AND a full detail page (e.g. blog posts, events).
+Do NOT add to: navigation-only types, visual composition components, containers.
+
+## Component location
+
+- **Component-level** (preferred): `src/components/<Category>/<Name>/definition.cnd`
+- **Module-level**: `settings/definitions.cnd` (for mixins and shared base types only)