Skip to main content

Enactor AI Tooling

Enactor's AI Tooling turns Claude Code into an Enactor-aware development assistant. It installs as a single Claude Code super plugin (enactor-ai-tooling) that manages child plugins for you. Claude installs the right one on demand, based on what you ask for:

  • enactor-workspace-assist: environment automation. Eclipse workspace setup and POS project create, build, and launch.
  • enactor-code-assist: codebase search and code generation. Entities, actions, endpoints, processes, and tests, all following Enactor's own patterns.
In one sentence

Install one plugin and describe what you want in plain English. Claude fetches the right tooling on demand and does the rest.

What can it do for you?​

You want to...The tooling gives you...
Set up an Enactor Eclipse workspaceAutomated download/checkout, Maven build, Eclipse import - with prerequisite checks and resume
Create and run a POSScaffolded POS Maven project, database, launch configs, one-command launch
Build a new entity, action, or processGenerated Java classes + Process XML that follow Enactor patterns
Find how something works in the codebaseSemantic search over the customer-facing codebase branches, 2.7 and 3.0.9
Reuse an existing Enactor patternPattern search, apply, build, and a change report
Test your workGenerated entity tests and process tests, run via Maven

How it fits together​

You install only the super plugin. When a request needs a child plugin that isn't installed yet, Claude asks once, installs it from the Enactor marketplace, and carries on with your request.

┌─────────────────────────────────────┐
│  enactor-ai-tooling  (the suite)    │  ← the only plugin you install
│  routes each request to a child     │
└──────────────┬──────────────┬───────┘
               │              │  installed on demand
               ▼              ▼
   enactor-workspace-assist   enactor-code-assist
   (workspace & POS setup)    (search & generate)

The code-assist child and its servers​

The code-assist child (enactor-code-assist) is where codebase search and code generation happen, and it does that work through two MCP (Model Context Protocol) servers:

  • enactor-local runs on your own machine as a small Python server, over stdio. It handles everything that needs your real checkout: searching your local code, reading files, validating process XML and Java (actions, endpoints, entities), and running process tests without a Maven build.
  • enactor-remote is a shared search-index server you reach over the network. It does semantic search across the whole indexed Enactor codebase, so you can find how something works without having every branch checked out yourself.
┌────────────────────────┐   stdio    ┌──────────────────────────────┐
│                        │◄──────────►│  enactor-local               │
│  Claude Code           │            │  (your machine · Python)     │
│  + Enactor AI plugin   │            │  local search · validate ·   │
│  (enactor-code-assist) │            │  parse · test                │
│                        │    http    └──────────────────────────────┘
│                        │  (OAuth)   ┌──────────────────────────────┐
│                        │◄──────────►│  enactor-remote              │
│                        │            │  (Enactor search gateway)    │
└────────────────────────┘            │  semantic code search        │
                                      └──────────────────────────────┘

What you'll learn in this section​

  1. Setup Guide: install the plugin and get both MCP servers connected (about 10 minutes).
  2. Using the Skills: which skill to use when, at a glance.
  3. Workspace Assist Skills: workspace setup & POS lifecycle skills, with example prompts.
  4. Code Assist Skills: codebase search & code generation skills, with example prompts and a hands-on exercise.
A note on working with AI

"The tooling makes you faster. The thinking is still yours."

  • Let the AI do: the searching, the boilerplate, the repetitive work.
  • You still do: the design decisions, the reviews, the final call.
  • Never ship what you don't understand, you own the code, not the AI.

How far this tooling takes you is almost entirely up to you. Use it well, and be 4x faster.