Stats
Actions
Tags
From light-process
High-level context for the light-process project. Load when the user works on light-process, mentions DAG workflows, light-run, light-runner, or asks about the architecture, ecosystem, or boundaries between the three sibling repos.
How this skill is triggered — by the user, by Claude, or both
Slash command
/light-process:contextThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
light-process is a lightweight DAG workflow engine. It orchestrates code that runs in Docker containers, connected by links with conditions. Container execution is delegated to a separate `light-run` HTTP service.
light-process is a lightweight DAG workflow engine. It orchestrates code that runs in Docker containers, connected by links with conditions. Container execution is delegated to a separate light-run HTTP service.
light-process -> light-run -> light-runner -> Docker
light-runner (Fastify, POST /run, artifacts, cancel). The only service light-process talks to.| Symptom | Fix in |
|---|---|
| Container-level (image not found, caps, volumes, stream) | light-runner |
| HTTP contract (payload shape, auth, cancel, artifacts) | light-run |
| Workflow / DAG / REST API / CLI | light-process (here) |
when condition and data injectionmaxIterationsPromise.all() for parallel nodeslight pack / light unpack"type": "module"), Node 20+.js extension (TypeScript ESM convention)LightProcessErrorpackage.json<type>(<scope>): <description> + build with cc trailerLIGHT_RUN_URL - required, e.g. http://localhost:3001LIGHT_RUN_TOKEN - optional, sent as Authorization: Bearer <token>LP_API_KEY - optional, enables Bearer auth on the REST serverRefer to CLAUDE.md and ECOSYSTEM.md for the full architecture and wire contract details.
npx claudepluginhub enixcode/plugins --plugin light-processGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.