epilot-dev/epilot-core

Build, extend, review, or troubleshoot an epilot App using its manifest, components, functions, App Bridge, API Proxy, the epilot MCP App API, the epilot CLI, and Volt UI for native-feeling interfaces. Use when the user explicitly asks for an App, custom page, entity capability or widget, journey or portal block, flow action, scheduled function, App deployment, an App that does not appear, or the design, Volt UI component selection, accessibility, or visual QA of an App interface. If it is unclear whether the solution should be an App, integration, or native configuration, use epilot-platform-guide first.

Create and modify epilot journeys — the customer-facing multi-step forms and funnels built in the Journey Builder — through the epilot MCP or CLI. Use when the user wants a new journey, changes to an existing journey's steps, blocks, logic, or design, or a review of journey quality. Covers the step/block model (schema + uischema), wiring, journey settings, and design conventions. For non-journey configuration use configure-epilot; for custom journey blocks use build-epilot-app.

Create and change epilot workflows (Prozesse) — the task graphs of the flows system with phases, decision branches, loops, and automation tasks — through the epilot MCP create_workflow and update_workflow tools. Use when the user wants a new internal process, changes to an existing workflow's steps or routing, a workflow that starts on an entity event or from a journey, conditional routing of cases, retry loops, or automated steps such as emails and webhooks inside a process. For customer-facing forms use build-epilot-journey; for other configuration use configure-epilot.

Configure the epilot platform end to end in a connected organization: entity schemas and attributes, taxonomies, journeys, entity mappings, products and pricing, automations, workflows, customer and installer portals, roles and permissions, and blueprints. Use when the user wants to set up, change, audit, or package platform configuration — including plain-language business outcomes such as "customers should be able to order X online" or "new requests should create a task for sales" — rather than build custom code. If it is unclear whether the solution should be configuration, an App, or an integration, use epilot-platform-guide first.

Explain epilot's platform model and route a product idea or requirement to native configuration, an epilot App, or an integration. Use for general epilot orientation, entities and schemas, relations, journeys, products, pricing, workflows, automations, portals, messaging, Apps, integrations, blueprints, and permissions, especially when the implementation boundary is unclear. Do not use as an exhaustive API or feature reference.

Connect an external service, backend, script, middleware, ETL job, or webhook to or from epilot using public APIs, SDKs, events, webhooks, mappings, or synchronization. Use for direct inbound, outbound, or bidirectional connectivity that does not require an epilot App, and for deciding whether Batch API or Integration Toolkit is a better mechanism. Do not use for custom epilot UI or vendor-specific Lima, SAP, or ERP semantics.