@pega/sdk 0.0.12 → 0.0.14

package/templates/react-sdk-reference/.ai-common/skills/connect-pega-server.md

@@ -4,51 +4,104 @@ ai-description: Ensure the Pega server connection (MCP config + sdk-config.json)
 
 # Pega Server Connection Gate
 
-Run this **before** the first Pega data source is executed in a chat session. It ensures the MCP server this session talks to, and `sdk-config.json`, both carry real connection values instead of the placeholder markers the project scaffolding step leaves behind. Scaffolding never asks for these — this gate is where they are actually collected, the first time a workflow needs them.
+Run this **before** the first Pega data source is executed in a chat session. It applies to both full-portal and embedded workflows. It resolves connection values from the project's existing configuration, asks once for everything still missing, and synchronizes the active MCP config and browser-served `sdk-config.json`.
 
-## 1. Locate the MCP config file
+## 1. Locate the active configuration files
 
-Find the file this session's AI tool reads its Pega MCP server list from. Do not assume a fixed name or path, and do not ask the user which file to edit — discover it by what it contains: a server entry whose key starts with `pega-`, holding a `url` that points at an `/api/service/v1/mcp/` endpoint. Search the project for a file matching that shape.
+### 1.1 MCP config
 
-## 2. Check whether it is already configured
+Find the file this session's AI tool reads its Pega MCP server list from. Do not assume a fixed name or ask the user which file to edit. Search the project for a server entry whose key starts with `pega-` and whose `url` contains `/api/service/v1/mcp/`.
 
-Read that file and `sdk-config.json`. Treat the connection as **already configured** only when none of the following markers remain, literally, in either file: `{InfinityURL}`, `{AppAlias}`, `{MCPRuleName}`, `{MCPRuleInsKey}`, `{ClientId}`, `{ClientSecret}`, and `sdk-config.json`'s `serverConfig.infinityRestServerUrl` / `serverConfig.appAlias` / `authConfig.mashupClientId` are non-empty.
+Classify the active MCP entry by its shape:
 
-If already configured, skip the rest of this gate and continue with the workflow that invoked it.
+- **Cursor-style authenticated MCP** — the entry contains `auth.clientId` and `auth.clientSecret`. Both fields are required for this MCP connection.
+- **URL-only MCP** — the entry has no auth fields, as in Copilot and Claude Code. Do not require, search for, warn about, or mention a client secret for this entry.
 
-## 3. Ask only for what is still missing
+### 1.2 Browser-served SDK config
 
-Check each value independently — ask only for the ones still a marker or blank, never re-ask for a value already present:
+Find the `sdk-config.json` the application actually serves to the browser. Do not automatically choose a same-named file at the project root:
 
-- Pega server URL
-- Application alias
-- OAuth client ID
-- MCP rule name
-- MCP rule instance key
-- **Client secret — only if the MCP config's server entry has an `auth` block containing a `clientSecret` field.** Some MCP configurations authenticate this way and some do not; let the file's own structure decide whether to ask, rather than deciding by which AI tool is running. If there is no `auth` block, do not ask for a client secret at all.
+- For an embedded project, identify the framework's served static directory (for example `public/`, `static/`, or another directory established by its build configuration) and use the `sdk-config.json` there.
+- For a full-portal project, use its scaffolded application `sdk-config.json`.
+- If more than one copy exists, determine which one the application serves. Report other copies as potentially stale and do not update them.
 
-Ask these as a single batch of questions, not one at a time.
+### 1.3 Environment files
 
-## 4. Write the values
+Environment files are commonly excluded by `.gitignore`, so do not rely on an ordinary recursive file search or glob to discover them. First enumerate the project-root directory, including dotfiles, then read every root entry named `.env` or beginning with `.env.` directly by its exact path. If directory enumeration is unavailable, search with ignored files explicitly included. A zero-result ignore-aware search is not evidence that no environment files exist.
 
-**MCP config file** — replace each marker with the value collected for it, and rename the `pega-{MCPRuleName}` server key using the real rule name:
+Read project-root environment files such as `.env`, `.env.local`, `.env.development`, `.env.production`, and other `.env.*` variants. Never print a secret value.
 
-- `{InfinityURL}` → server URL
-- `{AppAlias}` → application alias
-- `{MCPRuleName}` → MCP rule name (in both the server key and the URL path)
-- `{MCPRuleInsKey}` → MCP rule instance key
-- `{ClientId}` → client ID, if the entry has an `auth` block
-- `{ClientSecret}` → client secret, if the `auth` block has that field
+## 2. Build the connection inventory
 
-**`sdk-config.json`** — write into the existing structure, do not create new fields:
+Resolve each field independently from every applicable source. A value is unresolved when it is blank or still contains its scaffold marker.
 
-- `serverConfig.infinityRestServerUrl` → server URL
-- `serverConfig.appAlias` → application alias
-- `authConfig.mashupClientId` → client ID
-- `authConfig.portalClientId` → client ID (same value as `mashupClientId`)
+| Field                  | Allowed sources                                                                                                           | Destinations                                                   |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
+| Pega server URL        | `serverConfig.infinityRestServerUrl`, the MCP URL, or a matching environment key                                          | SDK config and MCP URL                                         |
+| Application alias      | `serverConfig.appAlias`, the MCP URL, or a matching environment key                                                       | SDK config and MCP URL                                         |
+| MCP rule name          | The `pega-*` MCP server key or a matching environment key                                                                 | MCP server key only                                            |
+| MCP rule instance key  | The MCP URL segment after `/api/service/v1/mcp/` or a matching environment key                                            | MCP URL                                                        |
+| OAuth client ID        | `authConfig.mashupClientId`, `authConfig.portalClientId`, MCP `auth.clientId` when present, or a matching environment key | Both SDK client-ID fields and MCP `auth.clientId` when present |
+| Pega MCP client secret | A private environment key only, and only when the MCP entry contains `auth.clientSecret`                                  | MCP `auth.clientSecret` only                                   |
 
-Never write the client secret into `sdk-config.json` — it belongs only in the MCP config file's `auth.clientSecret`.
+The five non-secret fields are required for every tool. The client ID is a public OAuth identifier and may be supplied in chat. A client secret is required only by a Cursor-style authenticated MCP entry; it is not required for the browser SDK or a URL-only Copilot/Claude Code MCP entry.
 
-## 5. Tell the user to reconnect
+For non-secret environment values, recognize clear semantic keys ending in `INFINITY_URL`, `SERVER_URL`, `APP_ALIAS`, `MCP_RULE_NAME`, `MCP_RULE_INS_KEY`, `MCP_RULE_INSTANCE_KEY`, or `CLIENT_ID`, including project conventions such as `PEGA_`, `VITE_`, `NEXT_PUBLIC_`, `REACT_APP_`, and `EXPO_PUBLIC_`.
 
-Most AI tools read their MCP config once at startup. After writing these values, tell the user the MCP server configuration changed and they need to reload or reconnect it (tool-dependent — e.g. restarting the MCP connection or reloading the window) before their request can proceed, and ask them to retry once reconnected.
+For a client secret, accept only a private key such as `PEGA_CLIENT_SECRET` or `CLIENT_SECRET`. Reject browser-exposed names beginning with `VITE_`, `NEXT_PUBLIC_`, `REACT_APP_`, or `EXPO_PUBLIC_`. Never infer a value from an unrelated key merely because it is the only candidate.
+
+Record each field's source and status: configured, missing, or conflicting. For a secret, record presence and source only, never its value.
+
+## 3. Resolve conflicts before writing
+
+If allowed sources contain different real values for the same non-secret field, show the field and each source/value pair and ask the user which source is authoritative. Do not silently choose or overwrite.
+
+If private environment files contain different client-secret values for a Cursor-style MCP entry, state that the secret sources disagree and name only the files and keys. Ask which environment key is authoritative without exposing either value.
+
+Equivalent values across sources are not conflicts; consolidate them without asking.
+
+## 4. Ask once for every unresolved value
+
+After reading all sources, make the first user interaction complete. Show a status table for every applicable field, using only **configured**, **missing**, or **conflicting**. For the client secret, show presence only.
+
+In that same response:
+
+1. Ask for every missing or conflict-resolved **non-secret** value as one batch. The user may provide these values directly in chat.
+2. Explain that the user may instead edit any allowed source and say when it is ready. Name the exact destinations:
+   - Environment: matching semantic keys for any non-secret field.
+   - Active `sdk-config.json`: `serverConfig.infinityRestServerUrl`, `serverConfig.appAlias`, `authConfig.mashupClientId`, and `authConfig.portalClientId`.
+   - MCP config: `{InfinityURL}` and `{AppAlias}` in the URL, `{MCPRuleName}` in the server key, `{MCPRuleInsKey}` in the URL, and `auth.clientId` when that field exists.
+3. If and only if the active MCP entry contains `auth.clientSecret` and no valid private environment value exists, explain in this first response that the **Pega MCP client secret** is missing. Tell the user to add `PEGA_CLIENT_SECRET` or another private `CLIENT_SECRET`-style key to a project-root environment file and confirm when ready. Never ask them to paste it into chat, put it in `sdk-config.json`, use a browser-exposed env key, or enter it directly into the MCP JSON.
+
+Do not stop after reporting a missing Cursor secret without also asking for every missing non-secret value. On every reply or retry, re-read all configuration sources and ask again only for fields that remain unresolved.
+
+## 5. Synchronize resolved values
+
+Once all five non-secret fields are resolved — and, for a Cursor-style MCP entry, a private environment-sourced secret is resolved — update the active files while preserving unrelated fields.
+
+**MCP config:**
+
+- Replace `{InfinityURL}` with the server URL.
+- Replace `{AppAlias}` with the application alias.
+- Rename the `pega-{MCPRuleName}` server key with the real MCP rule name. The rule name belongs in the server key, not the endpoint URL.
+- Replace `{MCPRuleInsKey}` with the MCP rule instance key.
+- When `auth.clientId` exists, write the resolved client ID.
+- When `auth.clientSecret` exists, write the private environment-sourced secret without displaying it.
+- Never add an auth block to a URL-only MCP entry.
+
+**Active browser-served `sdk-config.json`:**
+
+- Write the server URL to `serverConfig.infinityRestServerUrl`.
+- Write the application alias to `serverConfig.appAlias`.
+- Write the client ID to both `authConfig.mashupClientId` and `authConfig.portalClientId`.
+- Do not create new fields or change unrelated values.
+
+Never write a client secret into `sdk-config.json`, including `authConfig.portalClientSecret`. This file is served to the browser and is publicly readable. The user's browser-runtime OAuth grant configuration remains their choice; this gate only ensures the required public client ID is present.
+
+After writing, re-read both active files and repeat the inventory check. Continue only when all applicable markers are gone, the five non-secret values are non-empty and consistent, and a Cursor-style `auth.clientSecret` was populated from a private environment value. A URL-only MCP entry is complete without any client secret.
+
+## 6. Continue or reconnect
+
+- If the MCP config changed, tell the user it must be reloaded or reconnected before a Pega data source can run, then stop. Ask them to retry the original request; the invoking workflow must rerun this gate first. If MCP tools were started or attached after the conversation began and are not bound to this session, tell the user to start a new chat session.
+- If only `sdk-config.json` changed and the MCP connection is already available to the conversation, continue the invoking workflow without requiring an unnecessary MCP reconnect.
+- If neither file needed changes, continue immediately.

package/templates/react-sdk-reference/.ai-common/skills/embedded-flow/analyze-customer-repo.md

@@ -28,6 +28,15 @@ When Pega case flows are embedded into a customer's existing application, the ge
 
 ## Steps
 
+### Step 0 — Resolve the output path
+
+Every downstream skill and prompt writes generated components to one location: `{output_path}`. Resolve it once, here, before anything else runs. This is separate from the Design Profile document itself, which always lives at the fixed `docs/design-profile.md` and never moves with `{output_path}`.
+
+1. **Check for an existing profile first.** Look for `docs/design-profile.md` at the project root — this is its one fixed location, independent of `{output_path}`. If it exists, read its **Output Path** field (Section 1) and reuse that value as `{output_path}` — skip the rest of this step entirely. Do not ask the user again.
+2. **Otherwise, ask.** Ask the user where in their own project the generated Pega components should live. Suggest `pega-components/` at the project root as the default/recommended answer, but accept any path they type instead.
+3. **Validate the answer stays inside the project.** Reject an absolute path outside the project, any `..` traversal segment, or anything else that would resolve outside the project root — re-ask when this happens rather than writing outside the repo.
+4. **Record the confirmed path** as `{output_path}`. It is written into the Design Profile in Step 6 below, and every other embedded-flow skill/prompt reads it from there instead of asking again or assuming a fixed name.
+
 ### Step 1 — Identify project fundamentals
 
 Read the project's dependency manifest (the file that lists packages and their versions). From it, determine:
@@ -105,7 +114,7 @@ This is what makes it possible to offer the user real choices in their own vocab
 
 Produce a structured markdown document with the following sections. Use heading levels for organization and bullet lists for values. Do not include source code — describe patterns in prose and reference file paths for the AI to read during generation.
 
-**Section 1: Project Fundamentals** — list the framework name and version, language and configuration, UI library name and version (or "Custom"), styling approach, form handling library or pattern, and module system.
+**Section 1: Project Fundamentals** — start with the **Output Path** resolved in Step 0, then list the framework name and version, language and configuration, UI library name and version (or "Custom"), styling approach, form handling library or pattern, and module system.
 
 **Section 2: Design Tokens** — organize by sub-sections: Colors (primary, secondary, accent, error, warning, success, background, text, border with their semantic names and values), Spacing (scale), Typography (font families, sizes, weights), Borders and Radii (values), Shadows (elevation values), Breakpoints (if defined).
 
@@ -119,7 +128,7 @@ Produce a structured markdown document with the following sections. Use heading
 
 **Section 7: Navigation and Surfaces** — list the routing approach and how navigation is triggered, the overlay primitives the project uses and where they come from, the layout shell that wraps a routed page, and a table of existing task entry points giving each control's visible label, its file, and what it does today. The wiring workflow reads this section to decide where the embedded flow renders.
 
-Save this document to `pega-components/.design-profile.md` in the customer's project.
+Save this document to `docs/design-profile.md` in the customer's project, creating the `docs/` folder at the project root first if it does not already exist. This location is fixed — it does not move with `{output_path}`.
 
 ---
 

package/templates/react-sdk-reference/.ai-common/skills/embedded-flow/wire-integration.md

@@ -6,7 +6,7 @@ Guide the wiring of generated Pega components into a customer's existing applica
 
 ## Purpose
 
-After the `pega-components/` folder has been generated (via the component generation prompt), this skill describes the steps to integrate the Pega SDK into the customer's application — connecting authentication, bootstrapping the runtime, launching case flows on user action, and rendering the flow within the application's layout.
+After the generated components folder (its location is resolved during analysis and recorded in the Design Profile) has been generated (via the component generation prompt), this skill describes the steps to integrate the Pega SDK into the customer's application — connecting authentication, bootstrapping the runtime, launching case flows on user action, and rendering the flow within the application's layout.
 
 **Step 0 is the exception.** It is a gate, not an integration step, and it runs _before_ generation — see its own heading for why.
 
@@ -14,7 +14,7 @@ After the `pega-components/` folder has been generated (via the component genera
 
 ## Prerequisites
 
-- The `pega-components/` folder exists with generated components and a registry file named `component-map` (the extension follows the customer's framework) — required from **Step 1 onward**. Step 0 runs before generation and needs only the customer's codebase and the Design Profile
+- The generated components folder (its location is resolved during analysis and recorded in the Design Profile) exists with generated components and a registry file named `component-map` (the extension follows the customer's framework) — required from **Step 1 onward**. Step 0 runs before generation and needs only the customer's codebase and the Design Profile
 - The customer has a Pega Infinity environment with:
   - An OAuth 2.0 client configured for the application
   - A case type to embed (e.g., a service request, onboarding flow)
@@ -155,7 +155,7 @@ Add the following Pega packages to the project's dependency manifest:
 | The Pega SDK types package                                       | Shared type definitions and interfaces                          |
 | The Pega ConstellationJS core package                            | Runtime engine that provides the PCore global                   |
 
-These are the only external additions. The generated `pega-components/` use the customer's existing UI library — no additional design system packages are needed.
+These are the only external additions. The generated components use the customer's existing UI library — no additional design system packages are needed.
 
 If SDK packages were provided as `.tgz` files (interim distribution), they should already be in the project root with `file:` references in the dependency manifest. Run the project's package install command to link them.
 
@@ -295,7 +295,7 @@ The module-scoped singleton avoids this entirely because it is immune to compone
 
 1. **Authenticate** — use the SDK auth client to perform login (OAuth redirect or silent renewal)
 2. **Bootstrap in embedded/mashup mode** — initialize the SDK runtime in mashup mode (not full portal), capturing the render context returned by bootstrap
-3. **Create the component registry** — instantiate the SDK's component registry and register all components exported by the generated `pega-components/component-map` registry file
+3. **Create the component registry** — instantiate the SDK's component registry and register all components exported by the generated components folder's `component-map` registry file
 4. **Register the component creator** — tell the SDK runtime to use the registered components for rendering
 
 This module should expose:
@@ -433,7 +433,7 @@ Do not report the integration as complete on static checks alone.
 │  │  │                                                  │  │   │
 │  │  │  SDK Bridge Component                            │  │   │
 │  │  │    ↓ resolves from registry                      │  │   │
-│  │  │  pega-components/ (generated, customer-styled)   │  │   │
+│  │  │  generated components folder (generated, customer-styled) │  │   │
 │  │  │    ↓ wired to                                    │  │   │
 │  │  │  PConnect (Pega runtime state + actions)         │  │   │
 │  │  └─────────────────────────────────────────────────┘  │   │
@@ -470,7 +470,7 @@ Common integration failures and their resolutions. These are ordered by how they
 
 ## Notes
 
-- The generated `pega-components/` folder has zero dependencies beyond the customer's existing UI library and the Pega SDK packages. No additional design system installation is needed.
+- The generated components folder (its location is resolved during analysis and recorded in the Design Profile) has zero dependencies beyond the customer's existing UI library and the Pega SDK packages. No additional design system installation is needed.
 - The bootstrap module should handle token refresh/silent renewal automatically via the SDK auth client.
 - If the customer's app already has authentication, coordinate with their auth flow — the SDK auth client can share tokens if the same OAuth provider is used.
 - The Pega rendering container can be a modal, a sidebar, an inline section, or a full page. Which one is not a matter of taste — it is resolved in Step 0.2 from what the user asked for or from what their application already does.

package/templates/react-sdk-reference/.ai-common/skills/field-components.md

@@ -45,6 +45,50 @@ Extend the field input contract for component-specific additional inputs (e.g.,
 
 ---
 
+## Condition Encoding
+
+Several configuration settings describe a _condition_ rather than a fixed value. This section states their contract once; individual field skills may reference it instead of restating it.
+
+### The six shapes
+
+A condition-style setting can arrive in one of six forms: absent, the boolean true, the boolean false, an empty string, an expression-marked string, or a When-Rule-marked string. **All six are already resolved to a plain boolean by the runtime before the component receives the input.**
+
+This applies to `readOnly`, `required`, `disabled`, `visibility`, the nested visibility that governs a field-input warning message, and the same settings on any nested field descriptor. Because a descriptor is itself an ordinary field, the contract applies **recursively** to every level of nesting.
+
+### Consequences
+
+- Type every one of these inputs as a plain boolean. Never inspect its raw string form.
+- Never treat a non-empty string as automatically true. Doing so makes every expression-based or rule-based setting permanently active — the single most common way to get this wrong.
+- Treat absent, an empty string, and an explicitly-emitted default value as equivalent to the setting's documented default.
+- Ensure a resolved `disabled` or `readOnly` genuinely prevents interaction, rather than being accepted as an unused input.
+
+### Key presence never indicates intent
+
+Configuration does not clear a setting's key consistently when its control stops being relevant. All of the following occur:
+
+- A control that becomes hidden may leave its last value behind as a stale key.
+- A control that becomes hidden may instead have its key cleared.
+- A key cleared by one change may reappear later carrying a **re-seeded default**, not the value that was last configured for it.
+- Some presentations emit a setting's default explicitly while others omit it entirely, for the identical setting at the identical value.
+
+Therefore: decide which settings are active from the component's mode and presentation, never from which keys are present, and never assume a key's value reflects the last choice made for it.
+
+### Convenience visibility choices
+
+Visibility offers extra options phrased as "if not blank" and "if not zero". These are authoring conveniences that compile to ordinary expressions evaluated against the field's own bound value — they introduce no new value shape. They are offered only where the field has a single scalar bound value to test; a field bound to a list, or one presented as an embedded form, offers only the always / expression / rule choices.
+
+Never implement show/hide logic from `visibility`. A field whose visibility resolves to false is not rendered by the surrounding runtime at all.
+
+### Exception: conditions scoped to a single row
+
+A condition that governs an individual row of a list does **not** arrive resolved.
+
+Such a setting must be read from the component's **raw** configuration — the resolved inputs do not carry it — and evaluated per row against that row's own data, using the platform's expression engine. The configuration surface offers these settings only three choices: never, always, and a custom condition. The When-Rule option is deliberately absent, because a When Rule resolves once and cannot vary from row to row.
+
+Two failure modes to avoid. Typing such a setting as a boolean silently discards the per-row behaviour and applies one verdict to the whole list. Truthiness-checking the raw marked string makes the action permanently available for every row. Handle the three real cases explicitly: absent or true means allowed, an expression means evaluate per row, and anything else means denied.
+
+---
+
 ## Implementation Pattern
 
 ### Abstract Field Component Pattern
@@ -146,35 +190,37 @@ After creating a component, register it in the project's component map: import t
 
 ## Existing Field Components
 
-| Component       | Pega Name       | Description                       |
-| --------------- | --------------- | --------------------------------- |
-| AutoComplete    | AutoComplete    | Typeahead search field            |
-| CancelAlert     | CancelAlert     | Cancel confirmation dialog        |
-| Checkbox        | Checkbox        | Single checkbox with label        |
-| Currency        | Currency        | Currency input with formatting    |
-| Date            | Date            | Date picker                       |
-| DateTime        | DateTime        | Date + time picker                |
-| Decimal         | Decimal         | Decimal number input              |
-| Dropdown        | Dropdown        | Select/dropdown with options      |
-| Email           | Email           | Email input with icon             |
-| Group           | Group           | Field group container             |
-| Integer         | Integer         | Integer-only input                |
-| Location        | Location        | Google Maps location picker       |
-| Multiselect     | Multiselect     | Multi-select dropdown             |
-| ObjectReference | ObjectReference | Reference to another object       |
-| Percentage      | Percentage      | Percentage input                  |
-| Phone           | Phone           | Phone input with country selector |
-| RadioButtons    | RadioButtons    | Radio button group                |
-| RichText        | RichText        | Rich text editor                  |
-| ScalarList      | ScalarList      | List of scalar values             |
-| SelectableCard  | SelectableCard  | Card-style selection              |
-| SemanticLink    | SemanticLink    | Clickable link to another case    |
-| TextArea        | TextArea        | Multi-line text input             |
-| TextContent     | TextContent     | Static text display               |
-| TextInput       | TextInput       | Single-line text input            |
-| Time            | Time            | Time picker                       |
-| URL             | URL             | URL input with validation         |
-| UserReference   | UserReference   | User picker                       |
+| Component         | Pega Name         | Description                                    |
+| ----------------- | ----------------- | ---------------------------------------------- |
+| AutoComplete      | AutoComplete      | Typeahead search field                         |
+| CancelAlert       | CancelAlert       | Cancel confirmation dialog                     |
+| Checkbox          | Checkbox          | Single checkbox with label                     |
+| Currency          | Currency          | Currency input with formatting                 |
+| Date              | Date              | Date picker                                    |
+| DateTime          | DateTime          | Date + time picker                             |
+| Decimal           | Decimal           | Decimal number input                           |
+| Dropdown          | Dropdown          | Select/dropdown with options                   |
+| Email             | Email             | Email input with icon                          |
+| EmbeddedData      | EmbeddedData      | Single embedded record shown as a picker       |
+| EmbeddedDataMulti | EmbeddedDataMulti | List of embedded records (table, groups, tabs) |
+| Group             | Group             | Field group container                          |
+| Integer           | Integer           | Integer-only input                             |
+| Location          | Location          | Google Maps location picker                    |
+| Multiselect       | Multiselect       | Multi-select dropdown                          |
+| ObjectReference   | ObjectReference   | Reference to another object                    |
+| Percentage        | Percentage        | Percentage input                               |
+| Phone             | Phone             | Phone input with country selector              |
+| RadioButtons      | RadioButtons      | Radio button group                             |
+| RichText          | RichText          | Rich text editor                               |
+| ScalarList        | ScalarList        | List of scalar values                          |
+| SelectableCard    | SelectableCard    | Card-style selection                           |
+| SemanticLink      | SemanticLink      | Clickable link to another case                 |
+| TextArea          | TextArea          | Multi-line text input                          |
+| TextContent       | TextContent       | Static text display                            |
+| TextInput         | TextInput         | Single-line text input                         |
+| Time              | Time              | Time picker                                    |
+| URL               | URL               | URL input with validation                      |
+| UserReference     | UserReference     | User picker                                    |
 
 ---