pi-apexlang 0.1.0

package/skills/apexlang/templates/page-layout-templates/README.md

@@ -0,0 +1,123 @@
+# Page Layout Templates
+
+## Purpose
+Catalog of markdown-first Theme 42 page layout contracts and family variants used by APEXlang routers and template workflows.
+
+## What is in this directory
+
+- `_shared/`
+  - Shared page-template contracts reused across multiple families.
+- Family folders such as `blank/`, `standard/`, `drawer/`, `login/`, and `wizard-modal-dialog/`
+  - Each folder contains the family-specific contract, routing entrypoint, and baseline or scenario variants.
+
+Current layout families:
+- `blank/`
+- `drawer/`
+- `left-and-right-side-columns/`
+- `left-side-column/`
+- `login/`
+- `marquee/`
+- `minimal-no-navigation/`
+- `modal-dialog/`
+- `right-side-column/`
+- `standard/`
+- `wizard-modal-dialog/`
+
+## How to use this directory
+
+- Load the relevant shared contract before a family-specific layout:
+  - `_shared/page.common.md` for non-dialog families
+  - `_shared/page.modal-dialog.common.md` for modal dialog families
+  - `_shared/page.drawer.common.md` for drawer families
+- Load the family `_index.md`, then the family `_common.md`, then a variant or scenario markdown file.
+- Pair the chosen layout family with compatible page archetypes and region templates for deterministic page composition.
+- Resolve allowed `appearance.templateOptions` values from the inventory below; pass the documented `static_id`, not the emitted CSS class string.
+- Keep `#DEFAULT#` standalone when present and keep documented composite values atomic.
+- Preserve markdown-only path references when updating workflow or registry links.
+- Use `page-layout-template-family-registry.json` when tooling needs a machine-readable catalog for this family.
+
+## Theme 42 Page Template Options
+
+Use the listed `static_id` as the exact value to pass in `appearance.templateOptions`.
+Example: `appearance { templateOptions: [sticky-header-on-mobile] }`
+
+`Preset` shows the checked-in baseline already emitted by the template itself.
+
+### Blank (`blank`)
+Preset: none
+
+- Contain Body Content | `static_id=contain-body-content` | `css=t-PageBody--contain` | `group=--`
+
+### Drawer (`drawer`)
+Preset: `js-dialog-class-t-Drawer--pullOutEnd`
+
+- Remove Body Padding | `static_id=remove-body-padding` | `css=t-Dialog--noPadding` | `group=--`
+- Extra Large | `static_id=extra-large` | `css=js-dialog-class-t-Drawer--xl` | `group=Size`
+- Large | `static_id=large` | `css=js-dialog-class-t-Drawer--lg` | `group=Size`
+- Medium | `static_id=medium` | `css=js-dialog-class-t-Drawer--md` | `group=Size`
+- Small | `static_id=small` | `css=js-dialog-class-t-Drawer--sm` | `group=Size`
+- Bottom | `value=js-dialog-class-t-Drawer--pullOutBottom` | `css=js-dialog-class-t-Drawer--pullOutBottom` | `group=Position`
+- End | `value=js-dialog-class-t-Drawer--pullOutEnd` | `css=js-dialog-class-t-Drawer--pullOutEnd` | `group=Position`
+- Start | `value=js-dialog-class-t-Drawer--pullOutStart` | `css=js-dialog-class-t-Drawer--pullOutStart` | `group=Position`
+- Top | `value=js-dialog-class-t-Drawer--pullOutTop` | `css=js-dialog-class-t-Drawer--pullOutTop` | `group=Position`
+
+### Left and Right Side Columns (`left-and-right-side-columns`)
+Preset: none
+
+- Sticky Header on Mobile | `static_id=sticky-header-on-mobile` | `css=js-pageStickyMobileHeader` | `group=--`
+
+### Left Side Column (`left-side-column`)
+Preset: none
+
+- Sticky Header on Mobile | `static_id=sticky-header-on-mobile` | `css=js-pageStickyMobileHeader` | `group=--`
+
+### Login (`login`)
+Preset: none
+
+- Background 1 | `static_id=background-1` | `css=t-LoginPage--bg1` | `group=Page Background`
+- Background 2 | `static_id=background-2` | `css=t-LoginPage--bg2` | `group=Page Background`
+- Background 3 | `static_id=background-3` | `css=t-LoginPage--bg3` | `group=Page Background`
+- Split | `static_id=split` | `css=t-LoginPage--split` | `group=Page Layout`
+
+### Marquee (`marquee`)
+Preset: none
+
+- Sticky Header on Mobile | `static_id=sticky-header-on-mobile` | `css=js-pageStickyMobileHeader` | `group=--`
+
+### Minimal (No Navigation) (`minimal-no-navigation`)
+Preset: none
+
+- Sticky Header on Mobile | `static_id=sticky-header-on-mobile` | `css=js-pageStickyMobileHeader` | `group=--`
+
+### Modal Dialog (`modal-dialog`)
+Preset: none
+
+- Remove Body Padding | `static_id=remove-body-padding` | `css=t-Dialog--noPadding` | `group=--`
+- Stretch to Fit Window | `static_id=stretch-to-fit-window` | `css=ui-dialog--stretch` | `group=--`
+
+### Right Side Column (`right-side-column`)
+Preset: none
+
+- Sticky Header on Mobile | `static_id=sticky-header-on-mobile` | `css=js-pageStickyMobileHeader` | `group=--`
+
+### Standard (`standard`)
+Preset: none
+
+- Sticky Header on Mobile | `static_id=sticky-header-on-mobile` | `css=js-pageStickyMobileHeader` | `group=--`
+
+### Wizard Modal Dialog (`wizard-modal-dialog`)
+Preset: none
+
+- Remove Body Padding | `static_id=remove-body-padding` | `css=t-Dialog--noPadding` | `group=--`
+- Stretch to Fit Window | `static_id=stretch-to-fit-window` | `css=ui-dialog--stretch` | `group=--`
+
+## Directory Rules
+- Keep only the catalog `README.md`, the `_shared/` folder, and family folders at the root of `page-layout-templates/`.
+- Put cross-family contracts in `_shared/`.
+- Keep family-specific contracts and variants inside their corresponding family folders.
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Update catalogs and usage notes whenever templates are added, removed, or renamed.
+- Keep slot and template-option guidance aligned with current Theme 42 metadata and checked-in examples.
+- Keep `page-layout-template-family-registry.json` aligned with the shared folder and family directories.

package/skills/apexlang/templates/page-layout-templates/_shared/README.md

@@ -0,0 +1,24 @@
+# Shared Page Layout Contracts
+
+## Purpose
+Shared contracts used across multiple page layout families in `page-layout-templates/`.
+
+## What belongs here
+- `page.common.md`
+  - Shared contract for non-dialog page templates such as `standard/`, `blank/`, `left-side-column/`, `right-side-column/`, `left-and-right-side-columns/`, `minimal-no-navigation/`, `marquee/`, and `login/`.
+- `page.modal-dialog.common.md`
+  - Shared contract for modal dialog families such as `modal-dialog/` and `wizard-modal-dialog/`.
+- `page.drawer.common.md`
+  - Shared contract for the `drawer/` dialog family.
+- `../README.md`
+  - Shared page-template option inventory for all Theme 42 page layouts in this tree.
+
+## How to use
+- Do not treat files in this folder as standalone template families.
+- Load the relevant shared contract before the family `_common.md` file that builds on it.
+- Keep family-specific examples, variants, and routing entrypoints in their own family folders.
+
+## Maintenance
+- Keep this folder limited to contracts reused by multiple families.
+- Update family READMEs and `_index.md` files whenever shared contract paths change.
+- Prefer `_shared/` over root-level placement for reusable page layout contracts in this tree.

package/skills/apexlang/templates/page-layout-templates/_shared/page.common.md

@@ -0,0 +1,81 @@
+---
+templateId: page.common
+component: page
+dslVersion: 1.0
+description: Shared contract for non-dialog Theme 42 page layouts.
+---
+
+## Purpose
+Define the base page-level fields, common navigation and security defaults, and shared slot-token guidance for non-dialog page layouts that use `appearance.pageTemplate`.
+
+## Variables
+| Name | Required | Type | Description |
+|------|----------|------|-------------|
+| pageNumber | yes | number | Page identifier. |
+| name | yes | string | Page name. |
+| alias | yes | string | Page alias. |
+| title | optional | string | Browser and page title. |
+| appearance.pageTemplate | yes | string | Theme 42 page template reference such as `@/standard`. |
+| appearance.templateOptions | optional | string or array | Template options supported by the chosen page template; use the accepted values documented in [`../README.md`](../README.md), keep `#DEFAULT#` standalone, and do not substitute emitted CSS classes. |
+| navigation.cursorFocus | optional | enum | Usually `doNotFocusCursor`. |
+| security.authorizationScheme | required | alias | Defaults to `mustNotBePublicUser` for generated non-login business pages unless a stricter functional authorization scheme is supplied. |
+| security.pageAccessProtection | required | enum | Must be `argumentsMustHaveChecksum` for generated non-login business pages. |
+| security.formAutoComplete | optional | boolean | Typically `false` for generated examples. |
+| layout slots | derived | slot set | Usually `BODY`, `REGION_POSITION_01`, `REGION_POSITION_04`, `REGION_POSITION_05`; some templates add column or nav slots. |
+
+## Template
+```apexlang
+page [pageNumber] (
+    name: [name]
+    alias: [alias]
+    title: [title]
+    appearance {
+        pageTemplate: [appearance.pageTemplate]
+        templateOptions: [appearance.templateOptions]
+    }
+    navigation {
+        cursorFocus: doNotFocusCursor
+    }
+    security {
+        authorizationScheme: [security.authorizationScheme]
+        pageAccessProtection: [security.pageAccessProtection]
+        formAutoComplete: false
+    }
+
+    region content (
+        name: [contentRegionName]
+        type: [contentRegionType]
+        layout {
+            sequence: 10
+            slot: BODY
+        }
+    )
+)
+```
+
+## Slot Guidance
+- `BODY`: Primary page content. Theme 42 semantic alias is usually `body`.
+- `REGION_POSITION_01`: Header or breadcrumb bar content. Common semantic alias is `breadcrumbBar`.
+- `REGION_POSITION_04`: Dialogs, drawers, and popup launch surfaces.
+- `REGION_POSITION_05`: Footer content and low-priority actions.
+- Template-specific slots such as `REGION_POSITION_02`, `REGION_POSITION_03`, `REGION_POSITION_06`, `REGION_POSITION_08`, `AFTER_LOGO`, `AFTER_NAVIGATION_BAR`, and `BEFORE_NAVIGATION_BAR` should only be used when the selected template exposes them.
+
+## Conditional Rules
+- Put server-side conditions on regions, items, buttons, and processes instead of the page template declaration.
+- Hide optional side-column or footer content rather than moving it into `BODY`.
+- Use `REGION_POSITION_04` for dialog-capable supporting regions so page chrome and launched overlays stay separated.
+- Generated business pages must keep `authorizationScheme: mustNotBePublicUser` unless functional requirements select a stricter existing scheme.
+
+## Guardrails
+- Use `appearance.pageTemplate` only for non-dialog pages. Dialog families should use `appearance.pageMode: modalDialog` plus `appearance.dialogTemplate`.
+- Keep `templateOptions` aligned with the owning Theme 42 template definition and the inventory in [`../README.md`](../README.md).
+- Pass caller-facing `static_id` values such as `sticky-header-on-mobile` or `contain-body-content`, not the emitted CSS class string.
+- Never concatenate `#DEFAULT#` with another template-option value.
+- Prefer checked-in slot tokens such as `BODY` or `REGION_POSITION_01` in examples and generated snippets.
+- Do not omit page-level authorization for non-login pages; public access is login-page only unless a security-review rationale is emitted.
+
+## Source Anchors
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/standard.sql`
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/left_side_column.sql`
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/right_side_column.sql`
+- Internal template-source metadata

package/skills/apexlang/templates/page-layout-templates/_shared/page.drawer.common.md

@@ -0,0 +1,88 @@
+---
+templateId: page.drawer.common
+component: page
+dslVersion: 1.0
+description: Shared contract for drawer modal dialog page layouts.
+---
+
+## Purpose
+Define page-level variables, slot usage, and guardrails for drawer-style modal dialog pages that use the Theme 42 `Drawer` page template.
+
+## Variables
+| Name | Required | Type | Description |
+|------|----------|------|-------------|
+| pageNumber | yes | number | Page identifier. |
+| name | yes | string | Page name. |
+| alias | yes | string | Page alias. |
+| title | optional | string | Drawer title. |
+| appearance.pageMode | yes | enum | Must be `modalDialog`. |
+| appearance.dialogTemplate | yes | string | Must resolve to the drawer template, `@/drawer`. |
+| appearance.templateOptions | optional | string or array | Drawer position and size options supported by Theme 42; use the accepted values documented in [`../README.md`](../README.md), keep `#DEFAULT#` standalone, and do not substitute emitted CSS classes. |
+| security.authorizationScheme | required | alias | Defaults to `mustNotBePublicUser` for generated non-login drawer pages unless a stricter functional authorization scheme is supplied. |
+| security.pageAccessProtection | required | enum | Must be `argumentsMustHaveChecksum` for generated non-login drawer pages. |
+| page slots | derived | slot set | `BODY` (`contentBody`), `REGION_POSITION_01` (`dialogHeader`), `REGION_POSITION_03` (`dialogFooter`). |
+| footer button patterns | derived | slot set | Drawer footer implementations commonly expose `PREVIOUS`, `DELETE`, `CLOSE`, `EDIT`, `CREATE`, `NEXT`, and `FOOTER` through a footer region or the inline-drawer region template. |
+
+## Template
+```apexlang
+page [pageNumber] (
+    name: [name]
+    alias: [alias]
+    title: [title]
+    appearance {
+        pageMode: modalDialog
+        dialogTemplate: @/drawer
+        templateOptions: [appearance.templateOptions]
+    }
+    security {
+        authorizationScheme: [security.authorizationScheme]
+        pageAccessProtection: [security.pageAccessProtection]
+        formAutoComplete: false
+    }
+
+    region content (
+        name: [contentRegionName]
+        type: [contentRegionType]
+        layout {
+            sequence: 10
+            slot: BODY
+        }
+    )
+)
+```
+
+## Slot Guidance
+- `BODY`: Drawer body content.
+- `REGION_POSITION_01`: Drawer header content.
+- `REGION_POSITION_03`: Drawer footer content, typically a buttons region.
+- `NEXT`, `PREVIOUS`, `CLOSE`, `EDIT`, `CREATE`, `DELETE`: Common button-slot tokens used by footer button containers and the inline drawer region template.
+
+## Conditional Rules
+- Use conditions to tailor footer actions for create, edit, and read-only drawer scenarios.
+- Keep page-level footer content small; large supporting regions belong in the drawer body instead.
+- Generated drawer pages must keep `authorizationScheme: mustNotBePublicUser` unless functional requirements select a stricter existing scheme.
+
+### Condition Examples
+```apexlang
+serverSideCondition {
+    type: itemIsNotNull
+    item: P100_ID
+}
+
+serverSideCondition {
+    type: request!=Value
+    value: WIZARD
+}
+```
+
+## Guardrails
+- Keep `appearance.pageMode: modalDialog` and `appearance.dialogTemplate: @/drawer` together.
+- Align drawer position and size values with the live compiler/theme inventory in [`../README.md`](../README.md). For APEX 26.1 drawer position, emit values such as `js-dialog-class-t-Drawer--pullOutEnd`; do not emit stale short IDs such as `end`.
+- Never concatenate `#DEFAULT#` with another template-option value.
+- When the footer needs button-slot semantics, route them through a footer region pattern rather than treating them as page display points.
+- Do not emit public drawer pages by default.
+
+## Source Anchors
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/drawer.sql`
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/region/inline_drawer.sql`
+- Internal template-source metadata (`page-drawer`)

package/skills/apexlang/templates/page-layout-templates/_shared/page.modal-dialog.common.md

@@ -0,0 +1,74 @@
+---
+templateId: page.modal-dialog.common
+component: page
+dslVersion: 1.0
+description: Shared contract for standard modal dialog page layouts.
+---
+
+## Purpose
+Define the page-level variables, slot usage, and guardrails for modal dialog pages that use `appearance.pageMode: modalDialog`.
+
+## Variables
+| Name | Required | Type | Description |
+|------|----------|------|-------------|
+| pageNumber | yes | number | Page identifier. |
+| name | yes | string | Page name. |
+| alias | yes | string | Page alias. |
+| title | optional | string | Dialog title. |
+| appearance.pageMode | yes | enum | Must be `modalDialog`. |
+| appearance.dialogTemplate | yes | string | Dialog template reference such as `@/modal-dialog` or `@/wizard-modal-dialog`. |
+| appearance.templateOptions | optional | string or array | Dialog-template options supported by the chosen template; use the accepted values documented in [`../README.md`](../README.md), keep `#DEFAULT#` standalone, and do not substitute emitted CSS classes. |
+| security.authorizationScheme | required | alias | Defaults to `mustNotBePublicUser` for generated non-login dialog pages unless a stricter functional authorization scheme is supplied. |
+| security.pageAccessProtection | required | enum | Must be `argumentsMustHaveChecksum` for generated non-login dialog pages. |
+| layout slots | derived | slot set | Standard modal dialogs use `BODY`, `REGION_POSITION_01`, and `REGION_POSITION_03`. |
+
+## Template
+```apexlang
+page [pageNumber] (
+    name: [name]
+    alias: [alias]
+    title: [title]
+    appearance {
+        pageMode: modalDialog
+        dialogTemplate: [appearance.dialogTemplate]
+        templateOptions: [appearance.templateOptions]
+    }
+    security {
+        authorizationScheme: [security.authorizationScheme]
+        pageAccessProtection: [security.pageAccessProtection]
+        formAutoComplete: false
+    }
+
+    region content (
+        name: [contentRegionName]
+        type: [contentRegionType]
+        layout {
+            sequence: 10
+            slot: contentBody
+        }
+    )
+)
+```
+
+## Slot Guidance
+- `contentBody`: Main dialog content. Do not emit `body` or `BODY` for modal form regions; the live compiler expects the modal semantic slot.
+- `REGION_POSITION_01`: Dialog header content.
+- `REGION_POSITION_03`: Dialog footer content, often a button region.
+
+## Conditional Rules
+- Keep close and submit logic on explicit buttons and processes rather than relying on custom JavaScript.
+- Put optional dialog header or footer regions behind conditions when the page can run in compact or full modes.
+- Generated dialog pages must keep `authorizationScheme: mustNotBePublicUser` unless functional requirements select a stricter existing scheme.
+
+## Guardrails
+- Every dialog page should keep `appearance.pageMode: modalDialog`.
+- Use the dialog template that matches the intended chrome instead of retrofitting a standard page with modal behavior.
+- When the page needs wizard-specific header and footer semantics, switch to `@/wizard-modal-dialog`.
+- Pass dialog option `static_id` values such as `remove-body-padding` or `stretch-to-fit-window`, not the emitted CSS class string.
+- Never concatenate `#DEFAULT#` with another template-option value.
+- Do not emit public dialog pages by default.
+
+## Source Anchors
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/modal_dialog.sql`
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/wizard_modal_dialog.sql`
+- Internal template-source metadata

package/skills/apexlang/templates/page-layout-templates/blank/README.md

@@ -0,0 +1,18 @@
+# Blank Templates
+
+## Purpose
+Canonical guidance for the `@/blank` page layout family and its markdown entrypoints.
+
+## Usage
+- Load [`../_shared/page.common.md`](../_shared/page.common.md) first to align shared non-dialog variables and slot guidance.
+- Load `blank._common.md` next for the `@/blank` family contract.
+- Load `blank.basic.md` for a baseline example.
+
+## Template Catalog
+- `blank._common.md`
+- `blank.basic.md`
+
+## Maintenance
+- Keep this README synchronized with the files in this folder.
+- Preserve the markdown-only contract for page layout templates in this tree.
+- Keep slot and template-option guidance aligned with current Theme 42 metadata.

package/skills/apexlang/templates/page-layout-templates/blank/blank._common.md

@@ -0,0 +1,59 @@
+---
+templateId: page.blank
+component: page
+dslVersion: 1.0
+description: Blank page layout with only body content and overlay support.
+---
+
+## Purpose
+Apply the shared non-dialog page contract to the Theme 42 `Blank` page template. Use this layout for utility pages, embedded surfaces, and stripped-down pages that still need APEX page lifecycle behavior.
+
+## Variables
+| Name | Required | Type | Description |
+|------|----------|------|-------------|
+| base page vars | inherited | `page.common` | Load [`../_shared/page.common.md`](../_shared/page.common.md) first. |
+| appearance.pageTemplate | yes | string | Must be `@/blank`. |
+| appearance.templateOptions | optional | string or array | `#DEFAULT#` or `contain-body-content`; use the `static_id` values from the inventory in [`../README.md`](../README.md). |
+| layout slots | derived | slot set | `BODY` (`body`), `REGION_POSITION_04` (`dialogsDrawersAndPopups`). |
+
+## Template
+```apexlang
+page [pageNumber] (
+    name: [name]
+    alias: [alias]
+    title: [title]
+    appearance {
+        pageTemplate: @/blank
+        templateOptions: [appearance.templateOptions]
+    }
+    security {
+        authorizationScheme: mustNotBePublicUser
+        pageAccessProtection: [security.pageAccessProtection]
+        formAutoComplete: false
+    }
+
+    region content (
+        name: [contentRegionName]
+        type: [contentRegionType]
+        layout {
+            sequence: 10
+            slot: BODY
+        }
+    )
+)
+```
+
+## Slot Guidance
+- `BODY`: Main content region or free-form page body.
+- `REGION_POSITION_04`: Supporting dialogs, drawers, and popup-capable regions.
+
+## Conditional Rules
+- Keep supporting overlays out of `BODY` when they are launched or hidden by default.
+- Use page-level conditions sparingly; blank pages are usually simplest when most logic sits on the main content region.
+
+## Guardrails
+- Do not use this template when the page needs breadcrumb, footer, or navigation display points.
+- If the page should render contained content instead of full-width content, align the chosen option with the Theme 42 blank-template body containment setting.
+
+## Source Anchors
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/blank.sql`

package/skills/apexlang/templates/page-layout-templates/blank/blank._index.md

@@ -0,0 +1,18 @@
+---
+templateId: blank.index
+componentType: template
+dslVersion: 1.0
+imports:
+  - ../_shared/page.common.md
+  - blank._common.md
+description: Routing entrypoint for blank page templates.
+---
+
+## Purpose
+Primary routing entrypoint for `blank` templates.
+
+## Load Order
+1. Load this file.
+2. Load `../_shared/page.common.md`.
+3. Load `blank._common.md`.
+4. Load `blank.basic.md` when a baseline example is needed.

package/skills/apexlang/templates/page-layout-templates/blank/blank.basic.md

@@ -0,0 +1,42 @@
+---
+templateId: page.blank.basic
+component: page
+dslVersion: 1.0
+imports:
+  - blank._common.md
+description: Baseline blank page example with a single body region.
+---
+
+## Purpose
+Provide a minimal `@/blank` example for utility pages, embedded views, or lightweight task flows.
+
+## Template
+```apexlang
+page 40 (
+    name: Utility Surface
+    alias: UTILITY-SURFACE
+    title: Utility Surface
+    appearance {
+        pageTemplate: @/blank
+        templateOptions: #DEFAULT#
+    }
+    security {
+        authorizationScheme: mustNotBePublicUser
+        pageAccessProtection: argumentsMustHaveChecksum
+        formAutoComplete: false
+    }
+
+    region CONTENT (
+        name: Content
+        type: staticContent
+        layout {
+            sequence: 10
+            slot: BODY
+        }
+    )
+)
+```
+
+## Notes
+- Keep launched overlays in `REGION_POSITION_04` rather than mixing them into the body region.
+- Move to `@/standard` or another family when the page needs breadcrumb, footer, or side-rail chrome.

package/skills/apexlang/templates/page-layout-templates/drawer/README.md

@@ -0,0 +1,18 @@
+# Drawer Templates
+
+## Purpose
+Canonical guidance for the `@/drawer` page layout family and its markdown entrypoints.
+
+## Usage
+- Load [`../_shared/page.drawer.common.md`](../_shared/page.drawer.common.md) first to align drawer-specific variables and slot guidance.
+- Load `drawer._common.md` next for the `@/drawer` family contract.
+- Load `drawer.basic.md` for a baseline example.
+
+## Template Catalog
+- `drawer._common.md`
+- `drawer.basic.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Preserve the markdown-only contract for page layout templates in this tree.
+- Keep slot and template-option guidance aligned with current Theme 42 metadata.

package/skills/apexlang/templates/page-layout-templates/drawer/drawer._common.md

@@ -0,0 +1,65 @@
+---
+templateId: page.drawer
+component: page
+dslVersion: 1.0
+description: Theme 42 drawer page template for off-canvas modal dialogs.
+---
+
+## Purpose
+Apply the shared drawer contract to the Theme 42 `Drawer` page template. Use this layout when a modal page should slide in from a page edge or from the top or bottom.
+
+## Variables
+| Name | Required | Type | Description |
+|------|----------|------|-------------|
+| base drawer vars | inherited | `page.drawer.common` | Load [`../_shared/page.drawer.common.md`](../_shared/page.drawer.common.md) first. |
+| appearance.dialogTemplate | yes | string | Must be `@/drawer`. |
+| appearance.templateOptions | optional | string or array | Live-valid drawer option values. For APEX 26.1 position, use values such as `js-dialog-class-t-Drawer--pullOutEnd`; do not emit stale short IDs such as `end`, `start`, `top`, or `bottom`. |
+| layout slots | derived | slot set | `BODY` (`contentBody`), `REGION_POSITION_01` (`dialogHeader`), `REGION_POSITION_03` (`dialogFooter`). |
+
+## Template
+```apexlang
+page [pageNumber] (
+    name: [name]
+    alias: [alias]
+    title: [title]
+    appearance {
+        pageMode: modalDialog
+        dialogTemplate: @/drawer
+        templateOptions: [appearance.templateOptions]
+    }
+    navigation {
+        cursorFocus: doNotFocusCursor
+    }
+    security {
+        authorizationScheme: mustNotBePublicUser
+        pageAccessProtection: [security.pageAccessProtection]
+        formAutoComplete: false
+    }
+
+    region content (
+        name: [contentRegionName]
+        type: [contentRegionType]
+        layout {
+            sequence: 10
+            slot: BODY
+        }
+    )
+)
+```
+
+## Slot Guidance
+- `BODY`: Main drawer content.
+- `REGION_POSITION_01`: Header content such as title bars or helper actions.
+- `REGION_POSITION_03`: Footer region, usually the host for dialog buttons.
+
+## Conditional Rules
+- Keep create and edit action sets conditional when the drawer is reused across multiple flows.
+- Use live-valid pull-out drawer option values for side-sheet or sheet-style patterns.
+
+## Guardrails
+- Do not mix custom page CSS classes with Theme 42 drawer position classes unless the underlying template option already defines them.
+- Keep drawer content focused and task-oriented; large multi-section workflows should move to a wizard dialog or full page.
+
+## Source Anchors
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/drawer.sql`
+- Internal template-source metadata (`page-drawer`)

package/skills/apexlang/templates/page-layout-templates/drawer/drawer._index.md

@@ -0,0 +1,18 @@
+---
+templateId: drawer.index
+componentType: template
+dslVersion: 1.0
+imports:
+  - ../_shared/page.drawer.common.md
+  - drawer._common.md
+description: Routing entrypoint for drawer templates.
+---
+
+## Purpose
+Primary routing entrypoint for `drawer` templates.
+
+## Load Order
+1. Load this file.
+2. Load `../_shared/page.drawer.common.md`.
+3. Load `drawer._common.md`.
+4. Load `drawer.basic.md` when a baseline example is needed.