marketplace/bundles/pm-dev-frontend-cui/skills/plan-marshall-plugin/SKILL.md
CUI JavaScript domain manifest for plan-marshall workflow integration
npx skillsauth add cuioss/plan-marshall plan-marshall-pluginInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Domain manifest skill providing CUI-specific JavaScript project patterns as an additive extension to pm-dev-frontend.
Prohibited actions:
Constraints:
get_skill_domains() from ExtensionBaseThis bundle extends pm-dev-frontend — it does not stand alone:
| Layer | Provided by | What it gives |
|-------|-------------|---------------|
| Base | pm-dev-frontend | JavaScript domain (javascript), triage, ESLint, JSDoc, Jest testing |
| Extension | pm-dev-frontend-cui | CUI domain (javascript-cui), Maven integration, project structure defaults |
The CUI extension adds the javascript-cui domain on top of the javascript domain. Both are active for CUI JavaScript projects. The applies_to_module() check requires npm + maven (dual build system), signalling a Maven-managed frontend — the defining characteristic of CUI JS modules.
Core — Always loaded regardless of task:
cui-javascript-project as a default: project structure and Maven integration are fundamental to every CUI JS task, not optional extras.Implementation and module_testing — No CUI-specific skills required beyond what the base javascript domain provides.
Quality — No CUI-specific skills at this time.
Rationale for defaults vs optionals: A skill belongs in defaults when skipping it would mean missing critical context for routine tasks. Project structure is always relevant in a CUI JS project; domain-specific utilities (e.g., HTTP patterns) are optionals because they only apply to a subset of tasks.
Configuration is in extension.py:
| Method | Purpose |
|--------|---------|
| get_skill_domains() | Domain metadata with profiles |
| applies_to_module() | Detect CUI JS via npm + maven dual build system |
| config_defaults() | Set Maven profile defaults for CUI projects |
config_defaults() sets write-once Maven defaults (profile map and skip list) that match CUI Open Source project conventions. These are the same Maven lifecycle hooks CUI Java projects use since the frontend Maven plugin runs inside Maven.
This extension is discovered by:
skill-domains get-available - Lists available domainsskill-domains configure --domains javascript-cui - Configures the domainmarshall-steward wizard - Domain selection and config_defaults() applicationplan-marshall:extension-api - Extension API contractpm-dev-frontend:plan-marshall-plugin - Base JavaScript domainplan-marshall:build-maven - Maven profile keys used in config_defaultsdevelopment
Domain-owned OpenRewrite log-line finding parser for the java-cui domain — parses the
development
Domain-owned OpenRewrite marker detection for the java-cui domain — scans Java/Kotlin sources for cui-rewrite TODO markers, categorizes them by recipe, and fails the gate on any detected marker
development
Operator control surface for the marshalld build server — enrol/drop a project in the machine-global registry (the opt-in enable signal and anti-laundering wall), manage the daemon lifecycle (start, stop, drain, status, install, upgrade) version-pinned to the verified bundle copy, and inspect the daemon's per-project interaction-audit log (read-only)
tools
The tiny build-consumption client for the marshalld build server — submit a build job, bounded long-poll for its result, ping the daemon identity, and preflight registry-plus-liveness in one call; consumption only, never provisioning or enrolment