launchpad-ux-custom-components

Generate custom DXCB components for Launchpad with config.json and index.tsx.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/pegasystems/pega-launchpad-agent-skills --skill launchpad-ux-custom-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launchpad-ux-custom-components
Source: https://github.com/pegasystems/pega-launchpad-agent-skills/tree/main/skills/launchpad-ux-custom-components
Command: npx skills add https://github.com/pegasystems/pega-launchpad-agent-skills --skill launchpad-ux-custom-components

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Custom DXCB components fill gaps when built-in Constellation UX or UX Boosters don't meet Launchpad needs, enabling tailored components for portals, case views, data objects, and external integrations.

Core Features & Use Cases

  • Step-by-step guidance to determine when to use OOTB components, UX Boosters, or a new custom DXCB component.
  • Instructions for gathering requirements, selecting the appropriate component type (Field, Widget, or Template), and aligning with Constellation patterns.
  • A practical workflow to design, implement, test, and package a DXCB component for Launchpad deployment.

Quick Start

Describe your custom UX requirement and follow the mandatory conversation flow to initiate a new component.

Frequently Asked Questions about launchpad-ux-custom-components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a custom UX component when Constellation out-of-the-box components don't meet Launchpad requirements?

To build a custom UX component, follow a structured workflow to gather requirements, select a component type (Field, Widget, or Template), and generate a tailored config.json and index.tsx using DXCB patterns. This ensures Cosmos and PCore/PConnect APIs are used correctly.

When should I use a custom DXCB component instead of UX Boosters?

You need a custom DXCB component when both built-in Constellation UX and UX Boosters fail to satisfy specific Launchpad needs. Use this approach to enable tailored components for portals, case views, data objects, and external integrations.

What is the process for selecting the right component type in a Launchpad custom UX workflow?

The component-type selection process involves evaluating your custom UX requirement against Constellation patterns to determine whether a Field, Widget, or Template component best fits the case view or portal page scenario.

How do I generate the required config.json and index.tsx files for a DXCB component?

Generating config.json and index.tsx files requires completing a mandatory conversation flow that gathers design requirements, aligns with DXCB patterns, and outputs tailored code ensuring correct Cosmos and PCore/PConnect API usage.

Does the Launchpad custom UX component workflow support data objects and external integrations?

Yes, the custom DXCB component workflow supports building tailored components across case views, portal pages, data objects, and external integrations when existing Constellation UX components are insufficient.

What limitations exist when creating custom DXCB components for Launchpad portals?

Custom DXCB components require strict adherence to Cosmos and PCore/PConnect API patterns. You must complete the mandatory conversation flow to ensure proper component design, testing, and packaging before Launchpad deployment.