Workspace & POS Skills (enactor-workspace-assist)

These skills come from the enactor-workspace-assist child plugin: automated Enactor Eclipse workspace setup and POS project lifecycle. You don't install it directly. The first time you ask for any of these, Claude installs it on demand and continues with your request in the same conversation.

Workspace & POS skills

Skill	Use it when...
/setup-workspace	You need a full Enactor Eclipse workspace: Training Workspace (ZIP download from insights.enactor.co) or Developer Workspace (SVN checkout, internal edition only). Runs prerequisite checks, downloads/checks out, builds with Maven, and imports into Eclipse, resuming from any failed step.
/check-prerequisites	You only want to verify the environment: JDK 17, Maven, Artifactory, insights.enactor.co/SVN access, MariaDB settings, without touching workspace state.
/create-pos	You want a runnable POS project against your workspace: Maven structure, database, Eclipse launch configs, and a standalone launcher.
/launch-pos	You want to build (if needed) and launch an existing POS project.
/launch-pos-dev	You're changing the React POS UI and want it hot-reloading against a local dev server instead of rebuilding the platform each time. Internal edition only, and requires a Developer workspace (the React source lives in the Platform SVN checkout; Training workspaces don't have it). The next plain /launch-pos restores normal mode automatically.
/create-pos-extension	You want to scaffold and build a new Enactor POS Extension project: a Maven Update-Package module plus a React/Vite micro-frontend that plugs into an existing POS (routes, component overrides, its own dev server), rather than a standalone POS. Scaffolds and runs the first build in one step.
/build-pos-extension	You've changed the code of an already-scaffolded POS Extension project and want to rebuild it: full Maven + frontend build, frontend-only, or Maven-only.
/launch-pos-extension-dev	You want to iterate on a POS Extension's UI: either a standalone sandbox harness with no real POS involved, or toggling live integration so a running POS loads the extension's live build instead of its packaged assets.
/reset-pos	You want to clear the saved POS project state for the current folder (optionally the Maven project too) and run /create-pos again from scratch.
/reset-workspace	You want to clear the saved workspace setup state for the current folder so /setup-workspace starts completely fresh.

Fewer prompts

On first use, Workspace Assist offers to copy its permission template into your project's .claude/settings.json, so workspace and POS runs don't stop for approval on every command.

Example prompts

You don't need special syntax. Just describe the task. These are real examples:

Workspace setup:

"Set up an Enactor workspace in this folder."

"Set up a customer workspace for version 2.7.1331."

"Set up a developer workspace from the 2.7 branch."

"I already have a workspace checked out at D:\Work, adopt it instead of downloading again."

"Check if my machine has everything needed for an Enactor workspace."

POS projects:

"Create a POS in this workspace."

"Create a POS called StoreFrontPOS with a new database, device ID pos1, pointing at my local EMP server."

"Launch my POS."

"The POS build is broken, reset the POS state and create it again."

POS Extensions:

"Create a POS extension in this workspace."

"Create a POS extension called Loyalty Extension."

"Rebuild my POS extension."

"Launch my POS extension in the standalone dev sandbox."

"Switch my POS extension to live mode against the running POS."

Dev server (internal edition, Developer workspace only):

"Launch my POS against the React dev server so UI changes hot-reload."

"Go back to the normal launch, stop using the dev server."

Good to know

• All state is per folder: run the commands from your workspace directory. Re-running resumes from the last completed step instead of starting over.
• An existing workspace that was set up by hand (or by an older version) is detected and adopted automatically, with no re-download.
• MariaDB credentials are requested at most once per session via a native popup and are never written to project files.
• The customer edition only offers the Training Workspace type and the core POS lifecycle (create / launch / reset); Developer workspace and /launch-pos-dev are internal edition only. POS Extension commands (/create-pos-extension, /build-pos-extension, /launch-pos-extension-dev) are available in both editions.