CX Composer for Liferay — Liferay Client Extension code generator and scaffolder for VS Code and IntelliJ IDEA

CX Companion is the AI panel inside CX Composer — a workspace-aware chat available in VS Code and every JetBrains IDE. You describe what you want to build in plain English and CX Companion picks the right Liferay Client Extension type, scaffolds the full project (yaml, paired OAuth block, Dockerfile, assemble block, handler stub), edits existing yaml files, and runs the full preflight validator on every change. Nothing writes to disk until you review and accept each change — every file edit lands in a pending-edits review queue. CX Companion also hosts the **Website → Batch Client Extension** migrator: paste a URL, the plugin crawls the site, uses AI to infer an Object Definition schema from the extracted content, pulls records out as Object Entries, and produces a ready-to-deploy batch CX folder. CX Companion is Pro-only and currently in Preview. You bring your own AI key — Anthropic, OpenAI, Google, Groq, Azure, Ollama, or any OpenAI-compatible endpoint — and CX Composer calls the provider directly from your IDE; keys stay in the OS keychain and prompts never pass through cxcomposer.dev.

A Liferay Client Extension is a declarative package — defined by a client-extension.yaml manifest — that extends a Liferay DXP install without deploying a portlet or an OSGi bundle. There are 28 types spanning frontend widgets (Custom Element, IFrame), theming (Theme CSS, Global CSS/JS), configuration (OAuth apps, Instance Settings), microservices (Object Action, Workflow Action, Notification Type, CAPTCHA), batch (Batch, Site Initializer), commerce (Payment / Checkout / Shipping / Tax), and audiences. Each extension is built into a .zip with blade gw buildClientExtensionZip and deployed to a Liferay server.

Yes — CX Composer is a Liferay Client Extension code generator available as a **VS Code** extension and an **IntelliJ IDEA / JetBrains Platform** plugin (WebStorm, PhpStorm, PyCharm, GoLand, RubyMine, RustRover, DataGrip). It generates the client-extension.yaml manifest plus all the working code the extension needs: for microservice CX types (Object Action, Workflow Action, Notification Type, CAPTCHA, Commerce) it generates a Node.js or TypeScript Express handler, package.json, two-stage Dockerfile, LCP.json with liveness/readiness probes, and the paired OAuth application entry. For Site Initializer it generates the full folder tree Liferay expects (layouts, master pages, fragments, taxonomies, style books, object definitions, roles, notification templates). For Theme CSS it generates a starter frontend-token-definition.json. For Batch, right-click a batch CX folder → **Add Batch File** wizard lets you pick from **309 registered Liferay entity types** and drops a schema-correct batch/<entity>.batch-engine-data.json skeleton with the correct configuration.className, envelope shape, and required fields prepopulated. All schemas are verified against Liferay's official reference samples and DTO schemas extracted from Liferay's public OpenAPI schemas, so generated projects deploy against DXP without further tweaks.

Yes — with full schema coverage for **every one of Liferay's 309 registered batch-engine entity types** (Object Definitions, User Accounts, Sites, Taxonomies, Blog Postings, Workflow Definitions, Commerce entities, and 300 more). Schemas were extracted from Liferay's public OpenAPI schemas and enriched with 169 hand-verified runtime patches for parent-FK relationships that OpenAPI omits (e.g., Region.countryId, TaxonomyCategory.parentTaxonomyVocabularyExternalReferenceCode). Inside batch/*.batch-engine-data.json, CX Composer offers auto-complete for the configuration.className (all 309 entities, grouped and filterable), field completions inside items[] tailored to the file's specific className, hover documentation for every field pulled from Liferay's schema, and real-time diagnostics that catch missing required fields *before* you deploy — no more "No Country exists with primary key 0" errors after blade gw buildClientExtensionZip.

CX Composer is a VS Code extension **and IntelliJ IDEA plugin** that provides the full authoring lifecycle for Liferay Client Extensions: multi-step scaffolding for all 28 types (including full working Node.js or TypeScript microservices with Docker, and a complete Site Initializer folder tree), IntelliSense on client-extension.yaml (completions + hover for every field on every type), full schema IntelliSense + validation for **all 309 registered Liferay batch-engine entity types** inside batch/*.batch-engine-data.json, a workspace view listing every CX with deploy status, per-extension build via Blade, and six layered validators. Free tier validates LCP.json, Dockerfile, and yaml for four static-asset CX types (globalJS, globalCSS, themeSpritemap, jsImportMapsEntry). Pro (from $5/month, or $25/year) extends validation to every other CX type — including the full 309-entity batch surface — and unlocks the full productivity suite plus AI-powered scaffolding.

Blade CLI is a general-purpose Liferay tooling CLI — it can generate module skeletons, deploy bundles, and drive Gradle. CX Composer complements Blade with editor-first workflows: it invokes Blade under the hood for build (buildClientExtensionZip) but adds IntelliSense, validation, and a wizard-driven scaffold that Blade does not provide.

Six layered validators, all auto-running on save/open: (1) client-extension.yaml — full schema for all 28 types, unknown fields flagged with did-you-mean; (2) LCP.json — Liferay Cloud service config; (3) Dockerfile — instruction ordering + deprecation warnings; (4) folder-level companion checks — missing Dockerfile / assemble source / referenced JSON; (5) smart frontend-token-definition.json — walks up from the JSON to find its themeCSS entry and enforces the full frontendTokenCategories → sets → tokens → mappings schema; (6) **batch/*.batch-engine-data.json** — schema IntelliSense + validation against all **309 registered Liferay batch-engine entity types**, with 169 hand-verified runtime FK patches so imports don't fail with "No X exists with primary key 0". **Free tier:** LCP.json, Dockerfile, and yaml validation for the four static-asset CX types most projects iterate on — globalJS, globalCSS, themeSpritemap, jsImportMapsEntry. **Pro tier** ($5/month, $15 every 6 months, or $25/year): yaml validation for the other 24 CX types (all microservice / backend types, themeCSS, Site Initializer, Batch, Commerce), folder-level companion checks, cross-reference validation, deep frontend-token-definition.json shape checking, and the full 309-entity batch schema surface.