pi-apexlang 0.1.0

package/skills/apexlang/templates/shared-components/authorizations/authorizations.plsql.boolean.md

@@ -0,0 +1,69 @@
+---
+templateId: authorizations.plsql.boolean
+componentType: authorizations
+version: 1.0
+imports:
+  - authorizations.common
+---
+
+# Purpose
+
+Generate an Oracle APEX authorization component of type `plSqlFunctionBody`.
+
+This template must be used only when authorization logic is implemented as a PL/SQL function body that returns BOOLEAN.
+
+---
+
+# Generation Rules (MANDATORY)
+
+1. `settings.plsqlFunctionBody` MUST contain a RETURN statement returning TRUE or FALSE.
+2. The PL/SQL block may optionally include BEGIN/END, but must be syntactically valid.
+
+---
+
+# Variable Contract
+
+## Required Variables
+
+- settings.plsqlFunctionBody
+  - Type: plsql
+  - Constraints:
+    - Must return BOOLEAN.
+    - Must include RETURN TRUE or RETURN FALSE.
+    - Must not include trailing slash (/).
+
+---
+
+# Conditional Rendering Rules
+
+- If `serverCache.evaluationPoint` is not provided, omit the entire `serverCache {}` block.
+- If `error.errorMessage` is not provided, omit the entire `error {}` block.
+- If `comments.comments` is not provided, omit the entire `comments {}` block.
+
+---
+
+# Output Template
+```
+authorization {{name}} (
+    name: {{displayName}}
+    authorizationScheme {
+        type: plSqlFunctionBody
+    }
+    settings {
+        plsqlFunctionBody:
+            ```plsql
+            {{settings.plsqlFunctionBody}}
+            ```
+    }
+    serverCache {
+        evaluationPoint: {{serverCache.evaluationPoint}}
+    }
+    error {
+        errorMessage: {{error.errorMessage}}
+    }
+    comments {
+        comments: {{comments.comments}}
+    }
+)
+```
+---

package/skills/apexlang/templates/shared-components/authorizations/authorizations.role.md

@@ -0,0 +1,75 @@
+---
+templateId: authorizations.role
+componentType: authorizations
+version: 1.0
+imports:
+  - authorizations.common
+---
+
+# Purpose
+
+This template should be used when a user requests access to a resource, and the authorization check is based on the user being a member or not being a member of a specific role or group.
+
+---
+
+# Generation Rules (MANDATORY)
+
+None
+
+---
+
+# Variable Contract
+
+## Required Variables
+
+- authorizationScheme.type:
+    - isInRoleOrGroup - User is in a specific role or group
+    - isNotInRoleOrGroup - User is not in a specific role or group
+
+- settings.type:
+    - custom - Custom role or group defined in the application
+    - workspaceGroup - Role or group defined at the workspace level
+    - `no value` - Role defined in the application roles [default]
+
+- settings.names:
+    - The display name(s) of the role(s) or group(s) to check for membership.
+    - Emit as a bracketed multi-line list under `names: [` with one role display name per line.
+    - Each role display-name line must be indented twelve spaces inside the `names` block.
+    - Do not emit ACL role static IDs in this field.
+    - Do not emit comma-separated inline names.
+
+---
+
+# Conditional Rendering Rules
+
+- If `serverCache.evaluationPoint` is not provided, omit the entire `serverCache {}` block.
+- If `error.errorMessage` is not provided, omit the entire `error {}` block.
+- If `comments.comments` is not provided, omit the entire `comments {}` block.
+
+---
+
+# Output Template
+```
+authorization {{name}} (
+    name: {{displayName}}
+    authorizationScheme {
+        type: {{authorizationScheme.type}}
+    }
+    settings {
+        type: {{settings.type}}
+        names: [
+{{settings.names}}
+        ]
+    }
+    serverCache {
+        evaluationPoint: {{serverCache.evaluationPoint}}
+    }
+    error {
+        errorMessage: {{error.errorMessage}}
+    }
+    comments {
+        comments: {{comments.comments}}
+    }
+)
+```
+---

package/skills/apexlang/templates/shared-components/breadcrumbs/breadcrumb-entries.md

@@ -0,0 +1,88 @@
+---
+templateId: breadcrumb-entries
+componentType: breadcrumb-entries
+version: 1.0
+---
+
+# Purpose
+
+The breadcrumb entries component is embedded inside a breadcrumb component. It contains one entry per referenced page. Parent entries are optional only for true root pages; hub-launched, management, contextual, detail, and parent-child pages must declare their parent entry.
+
+---
+
+# Generation Rules (MANDATORY)
+
+1. Create the name and displayName
+2. All updates should be made to the breadcrumbs.apx file found under an application's /shared-components directory
+3. For full-app generation, do not emit a flat breadcrumb list. Match the hierarchy declared in the application spec and `.apexlang/app-ux-contract.json`.
+4. Put `parentEntry` only inside `appearance {}`. Never put it in `execution {}`.
+
+---
+
+# Variable Contract
+
+## Required Variables
+
+- entry
+  - Type: text
+  - The entry name; all lowercase, no spaces
+  - Used whe referencing a parent entry
+
+- entry.name
+    - Friendly name for the breadcrumb
+
+- entry.pageNumber
+    - Page Number that the breadcrumb entry is current for
+
+- entry.execution.sequence
+    - Sequence of breadcrumb entry; used to order them
+
+---
+
+# Conditional Rendering Rules
+
+- entry.appearance.parentEntry
+    - @entry of parent breadcrumb entry
+    - must always start with @
+    - entire `appearance` block only required when there is a parent present
+    - Common mistake: do not place `parentEntry` in `execution`; that is invalid.
+
+- entry.link.target
+    - Link that when clicked, the user will follow
+    - Typically uses the stadard APEX nominclature for links: f?p=&APP_ID.:1:&APP_SESSION.::&DEBUG.:::
+    - if not needed, the entire `link` block does not need to be rendered
+
+---
+
+# Output Template - No Parent
+```
+   entry {{entry}} (
+        name: {{entry.Name}}
+        pageNumber: {{entry.pageNumber}}
+        execution {
+            sequence: {{entry.execution.sequence}}
+        }
+        link {
+            target: {{entry.link.target}}
+        }
+    )
+```
+
+---
+
+# Output Template - With Parent
+```
+   entry {{entry}} (
+        name: {{entry.Name}}
+        pageNumber: {{entry.pageNumber}}
+        appearance {
+            parentEntry: @{{entry.appearance.parentEntry}}
+        }
+        execution {
+            sequence: {{entry.execution.sequence}}
+        }
+        link {
+            target: {{entry.link.target}}
+        }
+    )
+```

package/skills/apexlang/templates/shared-components/breadcrumbs/breadcrumbs.md

@@ -0,0 +1,53 @@
+---
+templateId: breadcrumbs
+componentType: breadcrumbs
+version: 1.0
+imports:
+  - breadcrumb-entries.md
+---
+
+# Purpose
+
+The breadcrumb component is used to provide page-level navigation for users.  It is composed of two parts: the breadcrumb itself (as defined in this file) and
+
+---
+
+# Generation Rules (MANDATORY)
+
+1. Create the name and displayName
+2. All updates should be made to the breadcrumbs.apx file found under an application's /shared-components directory
+
+---
+
+# Variable Contract
+
+## Required Variables
+
+- name
+  - Type: text
+  - all lowercase, no spaces - replace with dashses
+
+- displayName
+    - Friendly name for the breadcrumb
+
+- {{breadcrumbEntries}}
+    - This will be a list of entries that make up the breadcrumb
+    - rules defined in breadcrumb-entries.md
+
+---
+
+# Conditional Rendering Rules
+
+None
+
+---
+
+# Output Template
+```
+breadcrumb {{name}} (
+    name: {{displayName}}
+
+{{breadcrumbEntries}}
+
+)
+

package/skills/apexlang/templates/shared-components/build-options.md

@@ -0,0 +1,73 @@
+---
+templateId: build-options
+componentType: build-options
+version: 1.0
+---
+
+# Purpose
+
+This tempalte is used to create build options.
+
+---
+
+# Generation Rules (MANDATORY)
+
+None
+
+---
+
+# Variable Contract
+
+## Required Variables
+
+- name
+    - the name of the build option. This is required and must be unique across all build options.
+    - lower case and using - vs. spaces
+
+- displayName
+    - the display name of the build option. This is required and is used for display purposes in the UI.
+    - use spaces where needed as well as capitalization
+
+---
+
+## Optional Variables
+
+- status.status
+    - the status of the build option. When set to include, return `include`; else omit this attribute.
+    - Default is to omit this attribute.
+
+
+- status.defaultOnExport
+    - sets the export status to the current value of the build option.
+    - default is to omit this attribute; can be either `export` or `import`
+
+- status.onUpgradeKeepStatus
+    - `true` if the status of the build option should be kept during upgrade, `false` otherwise. Default is `false`.
+
+- comments.comments
+    - comments to be added to the build option. While not required, always try to create meaningful comments.
+
+---
+
+# Conditional Rendering Rules
+
+- If `status.status` is not provided, omit the entire `status.status {}` block.
+- If `status.defaultOnExport` is not provided, omit the entire `status.defaultOnExport {}` block.
+- If `comments.comments` is not provided, omit the entire `comments {}` block.
+
+---
+
+# Output Template
+```
+buildOption {{name}}
+    name: {{displayName}}
+    status {
+        status: {{status.status}}
+        onUpgradeKeepStatus: {{status.onUpgradeKeepStatus}}
+        defaultOnExport: {{status.defaultOnExport}}
+    }
+    comments {
+        comments: {{comments.comments}}
+    }
+)
+```

package/skills/apexlang/templates/shared-components/component-settings/component-settings._common.md

@@ -0,0 +1,20 @@
+---
+templateId: shared-components.component-settings.common
+componentType: shared-component
+version: 1.0
+description: Canonical contract for shared component default settings.
+---
+
+# Purpose
+Define deterministic defaults for APEX component settings. Use this markdown family as canonical input; `component-settings.example.md` preserves concrete syntax when needed.
+
+# Required Inputs
+- component static ID / native type
+- component category (`item`, `region`, `process`, `dynamicAction`, `restSource`)
+- compiler-validated `settings { attributes: {...} }` payload for the chosen component type
+
+# Guardrails
+- For current compiler compatibility, use `settings { attributes: {...} }` for component settings.
+- Do not emit direct keys inside `settings {}` (for example `display_as`, `mode`, `match_mode`).
+- Do not invent unsupported component categories.
+- Keep environment-specific values out of templates.

package/skills/apexlang/templates/shared-components/component-settings/component-settings._index.md

@@ -0,0 +1,18 @@
+---
+templateId: component-settings.index
+componentType: template
+version: 1.0
+imports:
+  - component-settings._common.md
+description: Routing entrypoint for component-settings templates.
+---
+
+# Purpose
+
+Primary routing entrypoint for `component-settings` templates.
+
+# Load Order
+
+1. Load this file.
+2. Load `component-settings._common.md`.
+3. Load one scenario template in this folder.

package/skills/apexlang/templates/shared-components/component-settings/component-settings.standard.md

@@ -0,0 +1,9 @@
+---
+templateId: shared-components.component-settings.standard
+componentType: shared-component
+version: 1.0
+imports:
+  - component-settings._common.md
+---
+
+Use this variant for standard shared component defaults across item, region, process, dynamic action, and REST source types.

package/skills/apexlang/templates/shared-components/component-settings.example.md

@@ -0,0 +1,128 @@
+---
+templateId: shared-components.component-settings.example
+componentType: markdown-apexlang-example
+version: 1.0
+migrationNote: preserved from previous standalone template example
+---
+
+# Component Settings Example
+
+## Purpose
+
+Markdown-preserved APEXlang example. Use this file for syntax and structure only after loading the family `_index.md` and `_common.md` contract.
+
+## Example
+
+```apexlang
+componentSetting NATIVE_OPEN_AI_ASSISTANT (
+    type: dynamicAction
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_COLOR_PICKER (
+    type: item
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_DATE_PICKER_APEX (
+    type: item
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_GEOCODED_ADDRESS (
+    type: item
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_SELECT_MANY (
+    type: item
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_SINGLE_CHECKBOX (
+    type: item
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_STAR_RATING (
+    type: item
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_YES_NO (
+    type: item
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_GEOCODING (
+    type: process
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_DISPLAY_SELECTOR (
+    type: region
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_IR (
+    type: region
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_MAP_REGION (
+    type: region
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_ADFBC (
+    type: restSource
+    settings {
+        attributes: {
+        }
+    }
+)
+
+componentSetting NATIVE_BOSS (
+    type: restSource
+    settings {
+        attributes: {
+        }
+    }
+)
+```

package/skills/apexlang/templates/shared-components/email-templates/email-templates._common.md

@@ -0,0 +1,75 @@
+---
+contractId: email-templates.common
+componentType: email-templates
+version: 1.0
+---
+
+# Purpose
+
+Standardize per-template variable contracts, file-level packaging rules, guardrails, and output structure for shared email templates.
+
+# Generation Rules (MANDATORY)
+
+1. Output only valid apexlang DSL.
+2. Do not output markdown.
+3. Do not explain the output.
+4. Omit optional blocks entirely if their variables are not provided.
+5. Preserve placeholder tokens verbatim.
+6. Keep HTML and plain text semantics aligned.
+7. Template Name should not contain special characters. Only the characters a-Z, 0-9 and spaces are allowed.
+8. Emit email templates into the single shared-components artifact named `email-templates.apx`.
+9. `email-templates.apx` may contain one or more consecutive top-level `emailTemplate ... )` definitions.
+10. Apply this variable contract to each individual `emailTemplate` block in `email-templates.apx`.
+11. When any feature triggers or invokes email, create or update the referenced email template in `email-templates.apx` before generating the send-email process or action.
+
+# Variable Contract
+
+| Name | Required | Type | Notes |
+|------|----------|------|-------|
+| name | yes | string | DSL identifier used in `emailTemplate {{name}}`; must obey the template-name guard rail and contain only letters, digits, and spaces. |
+| displayName | yes | string | Human-readable template name rendered as `name: {{displayName}}`. |
+| emailSubject | yes | string | Email subject line; preserve placeholder tokens exactly as provided. |
+| htmlFormat.header | no | string | Optional HTML header content rendered before the body. |
+| htmlFormat.body | yes | html | Main HTML content rendered in an `html` fenced block; preserve placeholder tokens verbatim and keep semantics aligned with `plainTextFormat.content`. |
+| htmlFormat.footer | no | string | Optional HTML footer content rendered after the body. |
+| plainTextFormat.content | yes | text | Plain text equivalent rendered in a fenced block; preserve placeholder tokens verbatim and keep semantics aligned with `htmlFormat.body`. |
+| advanced.versionNumber | no | number | Optional explicit version metadata; render as `versionNumber` when provided. |
+
+# Conditional Rendering Rules
+
+- Omit `htmlFormat.header` if `htmlFormat.header` is not provided.
+- Omit `htmlFormat.footer` if `htmlFormat.footer` is not provided.
+- Omit the entire `advanced {}` block if `advanced.versionNumber` is not provided.
+
+# Output Template
+```
+emailTemplate {{name}} (
+    name: {{displayName}}
+    emailSubject: {{emailSubject}}
+    htmlFormat {
+        header: {{htmlFormat.header}}
+        body: 
+            ```html
+            {{htmlFormat.body}}
+            ```
+        footer: {{htmlFormat.footer}}
+    }
+    plainTextFormat {
+        content: 
+            ```html
+            {{plainTextFormat.content}}
+            ```
+    }
+    advanced {
+        versionNumber: {{advanced.versionNumber}}
+    }
+)
+```
+
+# Mandatory Rendering Rules
+
+- Generate or update the shared-components artifact file named `email-templates.apx`.
+- Repeated application of this template produces additional sibling `emailTemplate` definitions in the same `email-templates.apx` file.
+- Do not split email templates into per-template `.apx` files.
+- Treat this contract as a prerequisite for any triggered or invoked email workflow.
+- Generate send-email processes or actions only after the referenced template has been added to `email-templates.apx`.

package/skills/apexlang/templates/shared-components/email-templates/email-templates._index.md

@@ -0,0 +1,20 @@
+---
+templateId: email-templates.index
+componentType: template
+version: 1.0
+imports:
+  - email-templates._common.md
+description: Routing entrypoint for email-templates templates.
+---
+
+# Purpose
+
+Primary routing entrypoint for `email-templates` templates.
+
+# Load Order
+
+1. Load this file.
+2. Load `email-templates._common.md`.
+3. Generate or update `shared-components/email-templates.example.md` using the shared contract in `email-templates._common.md`.
+4. Add additional email templates as sibling top-level `emailTemplate` definitions in the same `email-templates.apx` file.
+5. Only after the template exists in `shared-components/email-templates.example.md`, generate any process or action that invokes it.