Extension Template Catalog
Overview
The extension template catalog is a remote, versioned list of Candescent-maintained starters for mobile features. Use these vetted project layouts when you want a faster path than a blank offline scaffold. The generator downloads the latest catalog, allows you to pick a feature template, and produces a runnable Nx project wired for @cdx-extensions/di-sdk (PlatformSDK) and the mobile sandbox.
Run all commands below from your FI repository root.
For embedded home-screen widgets, see Widgets — Extension Template Catalog.
Browse the Catalog
Templates are added to the catalog on an ongoing basis. See the full, up-to-date set at generation time (interactive prompts) or with the list commands below.
Setup
Install the generator package:
npm install @cdx-extensions/extension-generator-mobile
Use the same @cdx-extensions registry configuration as the rest of your FI repo (see Getting Started).
See what's available
nx run list-mobile-feature-templates
nx run list-mobile-templates
These commands fetch the same remote catalog the generators use and print entries grouped by type and category.
Example: Agent Chat (Interactive)
Browse — category and template picker:
$ nx run generate-mobile-feature
? Choose a template category: › Interactive
? Choose a template: › Agent Chat — Bring-your-own-agent full-screen chat feature.
? Enter your FI Id (digits only, e.g. 0123): › 0123
? Choose a name for your feature (kebab-case, e.g. agent-chat): › acme-chat

Outcome — generated feature in the mobile sandbox:

Template ids, categories, and counts change as Candescent publishes new starters. Use nx run list-mobile-feature-templates or the interactive generator for the current catalog.
Generate Your Feature
Interactive (feature flow)
nx run generate-mobile-feature
Equivalent:
nx g @cdx-extensions/extension-generator-mobile:feature
You can also start from the type picker and choose feature:
nx run generate-mobile-extensions
Flow:
- Fetches the latest catalog from the remote URL (with cache and local fallbacks).
- Lists feature templates grouped by category (or prompts for type first when using
generate-mobile-extensions). - Prompts you to pick a category, then a template.
- Prompts for your FI Id and feature name.
- Optionally prompts for mock API
baseUrlandapiPathwhen the template supports it. - Downloads the selected npm template package and scaffolds the project.
| Workspace command | Underlying generator |
|---|---|
nx run generate-mobile-feature | @cdx-extensions/extension-generator-mobile:feature |
nx run generate-mobile-extensions | @cdx-extensions/extension-generator-mobile:generate |
Non-Interactive / CI Usage
Pass generator options after --:
nx run generate-mobile-feature -- --template=agent-chat --fiId=0123 --name=acme-chat
| Option | Required | Description |
|---|---|---|
fiId | Yes | Numeric FI id — digits only (0-9); accepts 4 or 5 digits (e.g. 0123, 03100). Values shorter than 4 digits are zero-padded (123 → 0123). |
name | Yes | Feature slug in kebab-case |
template | Yes | Catalog template id (discover ids with nx run list-mobile-feature-templates) or full npm package name |
noCache | No | Re-download catalog and template overlays (skip ~/.cdx/cache) |
catalogUrl | No | Override remote catalog URL |
directory | No | Output parent (default features/mobile) |
sandboxPath | No | Sandbox auto-wiring (default playground/mobile-sandbox) |
baseUrl | No | Mock API origin (templates with config.ts.tmpl only) |
apiPath | No | Mock API path (templates with config.ts.tmpl only) |
skipApiValidation | No | Skip live HTTP validation during generation |
What You Get
In addition to extension source from the selected template package, the generator writes CDX project scaffold files:
package.json,project.json,tsconfig.jsonsrc/index.ts, component entry file, and branding types
Output path:
- Features →
features/mobile/<name>/
The generator also auto-wires the new project into playground/mobile-sandbox so you can preview immediately.
Only modify files inside src/ for your feature logic and UI. See Getting Started for the full editability guide.
Advanced
Optional reference for troubleshooting and CI. Most users can skip this section.
Catalog source and cache
On each run the generator syncs catalog/extension-templates.json in this order: remote URL → ~/.cdx/cache/catalog/ → local workspace catalog/extension-templates.json.
Use --noCache after a platform publish if you need a fresh catalog or template overlay. Override the catalog URL with CDX_EXTENSION_CATALOG_URL or --catalogUrl when directed by support.
Template packages are cached under ~/.cdx/cache/<package>@<version>/dist/.
Mock API URL (config.ts templates)
Templates that ship config.ts.tmpl with baseUrl and apiPath trigger a mock API flow during generation. Features without config.ts.tmpl skip URL prompts entirely.
Supported mockApiContract values: portfolio-allocation, credit-score.
Next Steps
- Getting Started — Offline starter vs catalog, editability, and project layout
- Mobile Playground — Preview generated features locally
- Platform Capabilities (Local) — How local development works with mock data
- Host App Integration — Repository structure and submission process