Skip to content
Conduit

skill

pega-constellation-skills

Skills for AI coding agents: build, debug and publish Pega Constellation custom DX components. Install into any project.

Set up

Skills are installed by placing their folder where your agent loads skills.

The download comes from github.com/SanjeevSaniel/pega-constellation-skills itself, not from our server, so what you get is exactly what its author published.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below.

README

synced Nov 8, 2026

Pega Constellation skills

Skills for AI coding agents that build, debug and publish custom DX components for Pega Constellation. Install them into an existing project and your agent knows the mental model, the config.json format, the PConnect and PCore API, how data page calls really behave, the patterns that hold up, and the build and publish workflow.

Independent community project. Not affiliated with, endorsed by or sponsored by Pegasystems Inc. "Pega" and "Constellation" are trademarks of Pegasystems. This repo contains instructions only: no Pega source code, no builder templates, no official documentation.

Install

Pick one. Each puts the skill where your agent looks for it.

With npm (works with Claude Code and any agent that reads .claude/skills/):

npx @sanjeevsaniel/pega-constellation-skills init --agents

It copies the skill into .claude/skills/pega-constellation when the project already has a .claude folder (Claude Code finds it there), and into the neutral .agents/skills/pega-constellation otherwise, and adds a short block to AGENTS.md that points at it. Choose with --target claude or --target agents, or use --dir <path>. Other commands: update, remove, and the options --personal, --dry-run, --force. It never overwrites without --force.

Or copy the folder with degit:

npx degit SanjeevSaniel/pega-constellation-skills/skills/pega-constellation .claude/skills/pega-constellation

Or install it as a plugin (Claude Code):

/plugin marketplace add SanjeevSaniel/pega-constellation-skills
/plugin install pega-constellation@pega-constellation-skills

Or use it with Codex and other agents that read AGENTS.md: copy the skill as above, then add the block from AGENTS.snippet.md to your project's AGENTS.md.

More options, updating and uninstalling: docs/INSTALL.md.

What you get

One skill, pega-constellation, with a short SKILL.md that an agent reads first and eight references it opens only when the task needs them.

ReferenceCovers
conceptsVocabulary, how a screen is drawn, the four component kinds and subtypes, keys, what a component folder holds
config-jsonEvery top-level and setting attribute, the formats, slots, groups, defaultConfig, a worked example
api-cheatsheet"I want to..." table, PConnect methods, the actions API, PCore services, props by type
data-pagesParameters in every shape, query, sort and paging, saving, dropdowns, diagnosing a failed call
component-patternsButtons, layouts, tables, search, grids, widgets, and the habits that repeat
build-publishMatching the builder to the server, tasks.config.json, commands, what publish does, a checklist
error-handlingStable codes, the banner, safe logging, error boundaries, when to offer retry
troubleshootingSymptom, cause and fix, from a blank map to a locked ruleset

Try it

After installing, ask your agent things like:

  • "Create a Pega Constellation Field component that shows a star rating, with the number of stars as a setting."
  • "Why does my server-paginated table ignore paging?"
  • "Write the config.json for a two-column layout template with two regions."
  • "My data page call says required parameters are missing. What is wrong?"
  • "Walk me through publishing this component to a 26.1 server."

How accurate is it?

Be sceptical in the right places. The skill says what it observed and where it is unsure.

  • Facts about the builder, config.json and the scaffold come from reading the public @pega/custom-dx-components package (26.1.x), so they are version-specific. Verify against your version.
  • API names come from the public @pega/pcore-pconnect-typedefs package and from real components. Calls that work but are missing from the public typedefs are marked semi-internal.
  • Patterns and workarounds come from building and maintaining a large library of components. They are written generically, with invented names and data.
  • Anything it could not verify is labelled, not stated as fact. If the official documentation or your Pega version disagrees, trust them, and please open an issue.

Repo layout

.claude-plugin/        plugin and marketplace manifests
skills/
  pega-constellation/
    SKILL.md           what an agent reads first
    references/        eight focused references, opened on demand
docs/INSTALL.md        every way to install, update and remove
scripts/validate.mjs   checks every skill is well formed
docs/validate-workflow.yml   a GitHub Actions workflow that runs the check; copy it to .github/workflows/
AGENTS.snippet.md      the block to add to an AGENTS.md

Contributing

Corrections, version notes and new patterns are welcome. Read CONTRIBUTING.md first: the rules about verifying facts and about keeping private work out are strict.

Licence

MIT. Maintained by Sanjeev Kujur.

↑↓ navigate openesc close