pi-apexlang 0.1.0

package/skills/apexlang/templates/template-components/actions/README.md

@@ -0,0 +1,23 @@
+# Actions Templates
+
+## Purpose
+Canonical Actions template component pack for the Theme 42 `actions` helper, using MD-first scenario templates with one canonical APX fragment.
+
+## Usage
+- Load `actions._index.md` first.
+- Load `actions._common.md` next to align variable contracts, guardrails, and required inputs.
+- Load `actions._template_options.md` when the request changes helper settings such as `gap`, `size`, or `wrapActions`.
+- Load one scenario variant matching the requested helper pattern.
+
+## Template Catalog
+- `actions._common.md`
+- `actions._index.md`
+- `actions._template_options.md`
+- `actions.inline-button.md`
+- `actions.menu-trigger.md`
+- `actions.nested-group.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in this directory.
+- Update catalogs and usage notes whenever templates are added, removed, or renamed.
+- Keep family guidance aligned with page-level standards in memory-bank rules and with scenario coverage in this folder.

package/skills/apexlang/templates/template-components/actions/actions._common.md

@@ -0,0 +1,66 @@
+---
+templateId: actions.common
+componentType: templateComponent
+version: 1.0
+description: Shared canonical contract for the Actions helper template component.
+---
+
+# Purpose
+
+Define the shared variable contract, guardrails, and output skeleton for Theme 42 `actions` helper fragments.
+
+---
+
+# Generation Rules (MANDATORY)
+
+1. Use `actions { ... }` as an inline helper fragment, not a standalone region.
+2. Keep this helper scoped to action clusters rather than single page-level buttons.
+3. Use only supported child blocks: `button`, `menu`, or nested `actions`.
+4. Render `wrapActions` only when the prompt explicitly calls for wrapping.
+5. Keep `gap` and `size` within the documented enums from `actions._template_options.md`.
+
+---
+
+# Variable Contract
+
+| Name | Required | Type | Notes |
+|------|----------|------|-------|
+| size | optional | enum | `tiny`, `small`, `medium`, `large`, `extraLarge`. |
+| gap | optional | enum | `none`, `small`, `medium`, `large`. |
+| wrapActions | optional | boolean | Wrap actions when the container is narrow. |
+| child button | optional | block | Inline button helper entry. |
+| child menu | optional | block | Inline menu-trigger helper entry. |
+| child actions | optional | block | Nested action group when a secondary cluster is needed. |
+
+---
+
+# Output Template - Full
+
+```apx
+actions {
+    size: {{size}}
+    gap: {{gap}}
+    wrapActions: {{wrapActions}}
+
+    button {{buttonStaticId}} (
+        label: {{button.label}}
+        behavior {
+            target: {{button.behavior.target}}
+        }
+    )
+}
+```
+
+---
+
+# Conditional Rendering Rules
+
+- Omit `wrapActions` unless the prompt explicitly calls for wrapping behavior.
+- Use nested `actions` only when the parent pattern needs multiple grouped clusters.
+- Prefer a `menu` child instead of many sibling buttons when the action count is high.
+
+# Validation Checklist
+
+- The fragment starts with `actions {`.
+- Child blocks are limited to `button`, `menu`, or nested `actions`.
+- `gap` and `size` stay within the documented enums.

package/skills/apexlang/templates/template-components/actions/actions._index.md

@@ -0,0 +1,19 @@
+---
+templateId: actions.index
+componentType: template
+imports:
+  - actions._common.md
+version: 1.0
+description: Routing entrypoint for Actions helper templates.
+---
+
+# Purpose
+
+Primary routing entrypoint for `actions` helper templates.
+
+# Load Order
+
+1. Load this file.
+2. Load `actions._common.md`.
+3. Load one scenario template in this folder.
+4. Load the relevant scenario Markdown when concrete fragment syntax is needed.

package/skills/apexlang/templates/template-components/actions/actions._template_options.md

@@ -0,0 +1,16 @@
+# Actions Template Options
+
+These entries come from `create_plugin_attribute` and `create_plugin_attr_value`, not from `wwv_flow_template_options`.
+
+Apply these values through `settings`.
+Example: `settings { gap: medium size: large }`
+Emit only exact accepted values from this inventory. Do not concatenate adjacent values into one token and do not substitute labels or implementation details.
+
+When a row includes `values=`, pass the left-hand side of each `name=>return_value` pair.
+
+## Actions (`actions`)
+Supported: `PARTIAL`
+
+- `gap` | prompt=`Spacing` | type=`SELECT LIST` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--` | values=`large=>gapLarge, medium=>gapMedium, none=>gapNone, small=>gapSmall`
+- `size` | prompt=`Size` | type=`SELECT LIST` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--` | values=`extraLarge=>xlarge, large=>large, medium=>medium, small=>small, tiny=>tiny`
+- `wrapActions` | prompt=`Wrap Actions` | type=`CHECKBOX` | scope=`COMPONENT` | required=`false` | default=`N` | group=`--` | depends=`--`

package/skills/apexlang/templates/template-components/actions/actions.inline-button.md

@@ -0,0 +1,31 @@
+---
+templateId: actions.inline-button
+componentType: templateComponent
+imports:
+  - actions.common
+version: 1.0
+description: Inline Actions helper example with sibling buttons.
+---
+
+# Purpose
+Render a compact inline action cluster with one or more sibling buttons.
+
+# Output Template
+```apx
+actions {
+    size: {{size}}
+    gap: {{gap}}
+
+    button {{buttonStaticId}} (
+        label: {{button.label}}
+    )
+}
+```
+
+# Conditional Rendering Rules
+- Use sibling `button` blocks when the action count is small and all actions deserve equal emphasis.
+- Omit nested groups and menu triggers in this scenario.
+
+# Validation Checklist
+- The fragment contains at least one `button`.
+- `size` and `gap` use supported values.

package/skills/apexlang/templates/template-components/actions/actions.menu-trigger.md

@@ -0,0 +1,33 @@
+---
+templateId: actions.menu-trigger
+componentType: templateComponent
+imports:
+  - actions.common
+version: 1.0
+description: Actions helper example with a menu trigger.
+---
+
+# Purpose
+Render an action cluster that combines a primary button with a menu-trigger helper for secondary actions.
+
+# Output Template
+```apx
+actions {
+    button {{primaryButtonId}} (
+        label: {{primaryButton.label}}
+    )
+
+    button {{menuTriggerId}} (
+        label: {{menuTrigger.label}}
+        menuId: {{menuTrigger.menuId}}
+    )
+}
+```
+
+# Conditional Rendering Rules
+- Use a menu trigger when the action set is larger than the visible inline space.
+- Keep only one trigger button per action cluster unless the parent pattern explicitly needs more.
+
+# Validation Checklist
+- The menu-trigger button includes `menuId`.
+- The cluster still contains a clear primary action when required.

package/skills/apexlang/templates/template-components/actions/actions.nested-group.md

@@ -0,0 +1,35 @@
+---
+templateId: actions.nested-group
+componentType: templateComponent
+imports:
+  - actions.common
+version: 1.0
+description: Actions helper example with nested action groups.
+---
+
+# Purpose
+Render a parent action cluster that contains a secondary nested action group.
+
+# Output Template
+```apx
+actions {
+    button {{primaryButtonId}} (
+        label: {{primaryButton.label}}
+    )
+
+    actions {
+        size: {{nested.size}}
+        button {{secondaryButtonId}} (
+            label: {{secondaryButton.label}}
+        )
+    }
+}
+```
+
+# Conditional Rendering Rules
+- Use nested `actions` only when the parent component truly needs grouped secondary actions.
+- Keep nesting shallow; do not create deeply recursive action trees.
+
+# Validation Checklist
+- The nested structure remains one level deep.
+- Parent and child groups both use supported helper blocks.

package/skills/apexlang/templates/template-components/avatar._template_options.md

@@ -0,0 +1,23 @@
+# Avatar Template Component Options
+
+These entries come from `create_plugin_attribute` and `create_plugin_attr_value`, not from `wwv_flow_template_options`.
+
+Apply these values through the owning component's avatar settings block.
+Emit only exact accepted values from this inventory. Do not concatenate adjacent values into one token and do not substitute labels or implementation details.
+
+When a row includes `values=`, pass the left-hand side of each `name=>return_value` pair.
+
+## Avatar (`avatar`)
+Supported: `PARTIAL:REPORT`
+
+- `cssClasses` | prompt=`CSS Classes` | type=`TEXT` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `description` | prompt=`Description` | type=`TEXT` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `icon` | prompt=`Icon` | type=`ICON` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`type EQUALS ICON`
+- `image` | prompt=`Image` | type=`MEDIA` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`type EQUALS IMAGE`
+- `initials` | prompt=`Initials` | type=`SESSION STATE VALUE` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`type EQUALS INITIALS`
+- `shape` | prompt=`Shape` | type=`SELECT LIST` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--` | values=`circular=>t-Avatar--circle, noShape=>t-Avatar--noShape, rounded=>t-Avatar--rounded, square=>t-Avatar--square`
+- `size` | prompt=`Size` | type=`SELECT LIST` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--` | values=`extraExtraLarge=>t-Avatar--xxl, extraExtraSmall=>t-Avatar--xxs, extraLarge=>t-Avatar--xl, extraSmall=>t-Avatar--xs, large=>t-Avatar--lg, medium=>t-Avatar--md, small=>t-Avatar--sm`
+- `type` | prompt=`Type` | type=`SELECT LIST` | scope=`COMPONENT` | required=`false` | default=`IMAGE` | group=`--` | depends=`--` | values=`icon=>ICON, image=>IMAGE, initials=>INITIALS`
+- `spacing` | prompt=`Spacing` | type=`SELECT LIST` | scope=`REPORT` | required=`false` | default=`--` | group=`--` | depends=`--` | values=`auto=>t-Avatars--spacingAuto, large=>t-Avatars--spacingLg, medium=>t-Avatars--spacingMd, none=>t-Avatars--spacingNone, small=>t-Avatars--spacingSm, stack=>t-Avatars--spacingStack`
+- `groupIcon` | prompt=`Icon` | type=`ICON` | scope=`REPORT_GROUP` | required=`false` | default=`--` | group=`Grouping` | depends=`groupTitle NOT_NULL`
+- `groupTitle` | prompt=`Title` | type=`HTML` | scope=`REPORT_GROUP` | required=`false` | default=`--` | group=`Grouping` | depends=`--`

package/skills/apexlang/templates/template-components/badge._template_options.md

@@ -0,0 +1,20 @@
+# Badge Template Component Options
+
+These entries come from `create_plugin_attribute` and `create_plugin_attr_value`, not from `wwv_flow_template_options`.
+
+Apply these values through the owning component's badge settings block.
+Emit only exact accepted values from this inventory. Do not concatenate adjacent values into one token and do not substitute labels or implementation details.
+
+When a row includes `values=`, pass the left-hand side of each `name=>return_value` pair.
+
+## Badge (`badge`)
+Supported: `PARTIAL:REPORT`
+
+- `displayLabel` | prompt=`Display Label` | type=`CHECKBOX` | scope=`COMPONENT` | required=`false` | default=`N` | group=`--` | depends=`--`
+- `icon` | prompt=`Icon` | type=`ICON` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `label` | prompt=`Label` | type=`TEXT` | scope=`COMPONENT` | required=`true` | default=`--` | group=`--` | depends=`--`
+- `shape` | prompt=`Shape` | type=`SELECT LIST` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--` | values=`circular=>t-Badge--circle, rounded=>t-Badge--rounded, square=>t-Badge--square`
+- `size` | prompt=`Size` | type=`SELECT LIST` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--` | values=`large=>t-Badge--lg, medium=>t-Badge--md, small=>t-Badge--sm`
+- `state` | prompt=`State` | type=`SESSION STATE VALUE` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `style` | prompt=`Style` | type=`SELECT LIST` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--` | values=`outline=>t-Badge--outline, subtle=>t-Badge--subtle`
+- `value` | prompt=`Value` | type=`SESSION STATE VALUE` | scope=`COMPONENT` | required=`true` | default=`--` | group=`--` | depends=`--`

package/skills/apexlang/templates/template-components/button/README.md

@@ -0,0 +1,24 @@
+# Button Templates
+
+## Purpose
+Canonical Button helper pack for the Theme 42 `button` template component, using Markdown-first scenario templates.
+
+## Usage
+- Load `button._index.md` first.
+- Load `button._common.md` next to align variable contracts, guardrails, and required inputs.
+- Load `button._template_options.md` when the request changes helper-button attributes.
+- Load one scenario variant matching the requested helper behavior.
+- For helper buttons with `iconClasses` plus visible label text, put `t-Button--iconLeft` in `cssClasses` by default; use `t-Button--iconRight` only by explicit request, and omit both when `isIconOnly: true`.
+
+## Template Catalog
+- `button._common.md`
+- `button._index.md`
+- `button._template_options.md`
+- `button.navigation.md`
+- `button.hot-icon.md`
+- `button.menu-trigger.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in this directory.
+- Update catalogs and usage notes whenever templates are added, removed, or renamed.
+- Keep family guidance aligned with page-level standards in memory-bank rules and with scenario coverage in this folder.

package/skills/apexlang/templates/template-components/button/button._common.md

@@ -0,0 +1,76 @@
+---
+templateId: button.common
+componentType: templateComponent
+version: 1.0
+description: Shared canonical contract for the Button helper template component.
+---
+
+# Purpose
+
+Define the shared variable contract, guardrails, and output skeleton for Theme 42 `button` helper fragments.
+
+---
+
+# Generation Rules (MANDATORY)
+
+1. Use `button <staticId> ( ... )` as a helper fragment, not as page-level button metadata.
+2. Keep this helper inside action-bearing template components or action groups.
+3. Use `menuId` only when the parent pattern expects a menu-trigger button.
+4. Keep `isHot`, `isDisabled`, and `isIconOnly` opt-in.
+5. Use `iconClasses` only when the prompt requests visible icon treatment.
+6. When `iconClasses` is present with a visible `label` and `isIconOnly` is not true, include exactly one icon-position class in `cssClasses`: default to `t-Button--iconLeft`, or use `t-Button--iconRight` only when explicitly requested.
+7. Do not add `t-Button--iconLeft` or `t-Button--iconRight` when `isIconOnly: true`.
+8. Keep helper-button attributes aligned with `button._template_options.md`.
+
+---
+
+# Variable Contract
+
+| Name | Required | Type | Notes |
+|------|----------|------|-------|
+| buttonStaticId | yes | string | Helper block identifier. |
+| label | optional | string | Visible button label. |
+| behavior.target | optional | string | Navigation target. |
+| menuId | optional | string | Menu identifier when acting as a trigger. |
+| cssClasses | optional | string | Additional button classes. For icon-plus-text helpers, carries exactly one icon-position class, defaulting to `t-Button--iconLeft`. |
+| iconClasses | optional | string | Icon classes rendered by the helper. |
+| isDisabled | optional | boolean | Disable the helper. |
+| isHot | optional | boolean | Render hot styling. |
+| isIconOnly | optional | boolean | Render icon-only styling. |
+
+---
+
+# Output Template - Full
+
+```apx
+button {{buttonStaticId}} (
+    label: {{label}}
+    cssClasses: {{cssClasses}}
+    iconClasses: {{iconClasses}}
+    menuId: {{menuId}}
+    isDisabled: {{isDisabled}}
+    isHot: {{isHot}}
+    isIconOnly: {{isIconOnly}}
+    behavior {
+        target: {{behavior.target}}
+    }
+)
+```
+
+---
+
+# Conditional Rendering Rules
+
+- Render `behavior` only when the helper should navigate.
+- Render `menuId` only for menu-trigger behavior.
+- When rendering `iconClasses` with visible label text, render `cssClasses` with exactly one of `t-Button--iconLeft` or `t-Button--iconRight`; use left unless right-side placement is explicit.
+- Omit left/right icon-position classes for icon-only helpers.
+- Avoid combining `isIconOnly: true` with a visible text label unless the parent pattern explicitly requires both.
+
+# Validation Checklist
+
+- The fragment starts with `button <staticId> (`.
+- `menuId` is used only for menu-trigger behavior.
+- Icon-plus-text helpers include a single explicit icon-position class in `cssClasses`.
+- Icon-only helpers omit left/right icon-position classes.
+- Optional styling flags are included intentionally.

package/skills/apexlang/templates/template-components/button/button._index.md

@@ -0,0 +1,19 @@
+---
+templateId: button.index
+componentType: template
+imports:
+  - button._common.md
+version: 1.0
+description: Routing entrypoint for Button helper templates.
+---
+
+# Purpose
+
+Primary routing entrypoint for `button` helper templates.
+
+# Load Order
+
+1. Load this file.
+2. Load `button._common.md`.
+3. Load one scenario template in this folder.
+4. Load the relevant scenario Markdown when concrete fragment syntax is needed.

package/skills/apexlang/templates/template-components/button/button._template_options.md

@@ -0,0 +1,26 @@
+# Button Template Component Options
+
+These entries come from `create_plugin_attribute` and `create_plugin_attr_value`, not from `wwv_flow_template_options`.
+
+Apply these values directly through the helper attributes.
+Emit only exact accepted values from this inventory. Do not concatenate adjacent values into one token and do not substitute labels or implementation details.
+
+## Button (`button`)
+Supported: `child-helper`
+
+- `cssClasses` | prompt=`CSS Classes` | type=`TEXT` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `iconClasses` | prompt=`Icon Classes` | type=`ICON` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `isDisabled` | prompt=`Is Disabled` | type=`CHECKBOX` | scope=`COMPONENT` | required=`false` | default=`N` | group=`--` | depends=`--`
+- `isHot` | prompt=`Is Hot` | type=`CHECKBOX` | scope=`COMPONENT` | required=`false` | default=`N` | group=`--` | depends=`--`
+- `isIconOnly` | prompt=`Is Icon Only` | type=`CHECKBOX` | scope=`COMPONENT` | required=`false` | default=`N` | group=`--` | depends=`--`
+- `label` | prompt=`Label` | type=`TEXT` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `linkAttribute` | prompt=`Link Attribute` | type=`TEXT` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `linkUrl` | prompt=`Link URL` | type=`LINK` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `menuId` | prompt=`Menu ID` | type=`TEXT` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+
+## Icon Placement
+
+- For icon-plus-text helpers, put exactly one emitted Universal Theme icon-position class in `cssClasses`.
+- Default: `t-Button--iconLeft`.
+- Explicit right-side override: `t-Button--iconRight`.
+- Do not add either class when `isIconOnly: true`.

package/skills/apexlang/templates/template-components/button/button.hot-icon.md

@@ -0,0 +1,32 @@
+---
+templateId: button.hot-icon
+componentType: templateComponent
+imports:
+  - button.common
+version: 1.0
+description: Hot Button helper example with icon styling.
+---
+
+# Purpose
+Render a Button helper with hot emphasis and a leading icon.
+
+# Output Template
+```apx
+button {{buttonStaticId}} (
+    label: {{label}}
+    cssClasses: t-Button--iconLeft
+    iconClasses: {{iconClasses}}
+    isHot: true
+)
+```
+
+# Conditional Rendering Rules
+- Use `isHot: true` only when the button deserves primary emphasis.
+- Render `iconClasses` only when visible icon treatment is requested.
+- Use `cssClasses: t-Button--iconLeft` by default for icon-plus-text helpers; replace with `t-Button--iconRight` only when right-side icon placement is explicitly requested.
+- Do not render a left/right icon-position class when the helper is icon-only.
+
+# Validation Checklist
+- The icon classes are present.
+- The helper includes exactly one icon-position class for icon-plus-text output.
+- Hot styling is used intentionally for primary emphasis.

package/skills/apexlang/templates/template-components/button/button.menu-trigger.md

@@ -0,0 +1,27 @@
+---
+templateId: button.menu-trigger
+componentType: templateComponent
+imports:
+  - button.common
+version: 1.0
+description: Menu-trigger Button helper example.
+---
+
+# Purpose
+Render a Button helper that opens a menu instead of navigating directly.
+
+# Output Template
+```apx
+button {{buttonStaticId}} (
+    label: {{label}}
+    menuId: {{menuId}}
+)
+```
+
+# Conditional Rendering Rules
+- Use `menuId` only when the parent component expects a menu trigger.
+- Omit navigation behavior when the menu is the primary interaction.
+
+# Validation Checklist
+- `menuId` is present.
+- The helper does not mix incompatible navigation and menu-trigger behavior.

package/skills/apexlang/templates/template-components/button/button.navigation.md

@@ -0,0 +1,29 @@
+---
+templateId: button.navigation
+componentType: templateComponent
+imports:
+  - button.common
+version: 1.0
+description: Standard navigation Button helper example.
+---
+
+# Purpose
+Render a Button helper that navigates to another target.
+
+# Output Template
+```apx
+button {{buttonStaticId}} (
+    label: {{label}}
+    behavior {
+        target: {{behavior.target}}
+    }
+)
+```
+
+# Conditional Rendering Rules
+- Render `behavior` for navigation.
+- Omit hot, icon-only, and menu-trigger settings in the basic navigation case.
+
+# Validation Checklist
+- The helper includes a valid target.
+- The helper uses a stable static id.

package/skills/apexlang/templates/template-components/comments._template_options.md

@@ -0,0 +1,24 @@
+# Comments Template Options
+
+These entries come from `create_plugin_attribute` and `create_plugin_attr_value`, not from `wwv_flow_template_options`.
+
+Apply these values through the owning component's settings plus the shared avatar owner file when avatar rendering is enabled.
+Load `avatar._template_options.md` for the shared avatar substructure used by Comments.
+Emit only exact accepted values from this inventory. Do not concatenate adjacent values into one token and do not substitute labels or implementation details.
+
+When a row includes `values=`, pass the left-hand side of each `name=>return_value` pair.
+
+## Comments (`comments`)
+Supported: `PARTIAL:REPORT`
+
+- `attributes` | prompt=`Attributes` | type=`HTML` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `commentClass` | prompt=`Comment Class` | type=`TEXT` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `commentText` | prompt=`Comment Text` | type=`SESSION STATE VALUE` | scope=`COMPONENT` | required=`true` | default=`--` | group=`--` | depends=`--`
+- `date` | prompt=`Date` | type=`SESSION STATE VALUE` | scope=`COMPONENT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `displayAvatar` | prompt=`Display Avatar` | type=`CHECKBOX` | scope=`COMPONENT` | required=`false` | default=`Y` | group=`--` | depends=`--`
+- `userName` | prompt=`User Name` | type=`SESSION STATE VALUE` | scope=`COMPONENT` | required=`true` | default=`--` | group=`--` | depends=`--`
+- `alignment` | prompt=`Alignment` | type=`TEXT` | scope=`REPORT` | required=`false` | default=`--` | group=`--` | depends=`--`
+- `applyThemeColors` | prompt=`Apply Theme Colors` | type=`CHECKBOX` | scope=`REPORT` | required=`false` | default=`Y` | group=`--` | depends=`--`
+- `style` | prompt=`Style` | type=`SELECT LIST` | scope=`REPORT` | required=`true` | default=`t-Comments--basic` | group=`--` | depends=`--` | values=`basic=>t-Comments--basic, chatSpeechBubbles=>t-Comments--chat`
+- `groupIcon` | prompt=`Icon` | type=`ICON` | scope=`REPORT_GROUP` | required=`false` | default=`--` | group=`Grouping` | depends=`groupTitle NOT_NULL`
+- `groupTitle` | prompt=`Title` | type=`HTML` | scope=`REPORT_GROUP` | required=`false` | default=`--` | group=`Grouping` | depends=`--`

package/skills/apexlang/templates/template-components/content-row/README.md

@@ -0,0 +1,36 @@
+# Content Row Templates
+
+## Purpose
+Canonical Content Row template pack for `themeTemplateComponent/contentRow`, using Markdown-first scenario templates.
+
+## Usage
+- Load `content-row._common.md` first for variable contract and generation guardrails.
+- Use `content-row._index.md` to pick the correct scenario template.
+- Load `content-row._template_options.md` for Content Row-specific settings, appearance, and grouping values.
+- Load `../avatar._template_options.md` and `../badge._template_options.md` for the shared avatar and badge substructures.
+- Avatar-capable Content Row scenarios use `settings.displayAvatar` plus `plugin-avatar` fields for type, initials/description, shape, size, and CSS classes.
+- Badge-capable Content Row scenarios use `settings.displayBadge` plus `plugin-badge` fields for label, value, state, style, shape, size, icon, position, and width.
+- SQL-backed template component regions must emit top-level `orderBy {}` and must not embed `ORDER BY` inside `source.sqlQuery`.
+- When Content Row grouping is used on child columns, the top-level `orderBy` must sort by all grouped columns first before any remaining tie-breakers.
+- Report-mode Content Row requires explicit child `column (...)` metadata.
+- By default, those child columns should match the delivered region source projection in order, not just the minimum subset needed to satisfy the compiler.
+- When Content Row uses any `rowSelection` mode, one child column must carry `source.primaryKey: true`.
+
+## Template Catalog
+- `content-row._common.md`
+- `content-row._index.md`
+- `content-row._template_options.md`
+- `content-row.partial-minimal.md`
+- `content-row.partial-rich-content.md`
+- `content-row.report-minimal.md`
+- `content-row.report-explicit-defaults.md`
+- `content-row.report-avatar-badge.md`
+- `content-row.report-link-positions.md`
+- `content-row.report-primary-actions-menu.md`
+- `content-row.report-grouping-selection.md`
+- `content-row.report-appearance-variants.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in this directory.
+- Keep `manifest.json` in sync with scenario files and feature tags.
+- New or updated scenario docs should include: `# Purpose`, `# Output Template`, `# Conditional Rendering Rules`, `# Validation Checklist`.