Using the Skills
Once setup is complete, you interact with the tooling through skills: slash commands you type inside Claude Code. The skills are provided by two child plugins, each with its own page - Claude installs either one on demand the first time you need it:
- Workspace Assist Skills (
enactor-workspace-assist) - Eclipse workspace setup and POS project create/build/launch. - Code Assist Skills (
enactor-code-assist) - codebase search and generation of entities, actions, processes, and tests.
Which skill do I need?
Ask yourself what you're trying to do:
| I'm trying to... | Use | Plugin |
|---|---|---|
| Set up an Enactor Eclipse workspace | /setup-workspace | workspace-assist |
| Check my machine meets the prerequisites | /check-prerequisites | workspace-assist |
| Create or run a POS project | /create-pos / /launch-pos | workspace-assist |
| Hot-reload the React POS UI while developing it (internal edition, Developer workspace) | /launch-pos-dev | workspace-assist |
| Build something (not sure what's involved) | /assist | code-assist |
| Find existing code or patterns first | /search-codebase | code-assist |
| Create business logic (validation, lookup, process step) | /create-action | code-assist |
| Build a UI workflow, popup, prompt, or POS process | /create-process | code-assist |
| Create a brand-new entity | /create-entity-full | code-assist |
| Test what I built | /test-process or /create-entity-test | code-assist |
| Copy an existing Enactor pattern to my code | /apply-pattern | code-assist |
You don't need to remember which plugin owns a skill - describe the task in plain English and Claude routes it (installing the child plugin first if it's missing).
Use it well
AI-generated code still needs your review. Always read the generated files, run the builds/tests, and apply the same code-review standards you would to hand-written code.