Step 1 — Clone the repo
Step 2 — Give your agent this prompt
Point the agent at wherever you cloned the repo — adjust the path in the prompt if it’s not a sibling directory of your project.
What the agent will actually do
- Read
INTEGRATION.md’s requirements, then pick the one integration path (vanilla JS / React / SPA) that matches your codebase — it won’t blindly paste the first snippet it sees - Add the
<script>tag, a correctly-sized container<div>, and theEPIS.init()/mountChat()call - Leave
clientId: 'your-client-id'as an obvious placeholder rather than inventing one - Derive a theme config matching your app’s brand — either by reading your existing CSS/design tokens directly, or by running the AI theming skill if you ask it to
- Start a local static server for you if your project is plain static HTML with no dev server already — see Local Development for why
file://won’t work - Stop there —
constraints.mdin the theming skill explicitly forbids touching anything outside thethemeobject, and the prompt above scopes the rest of the work to just this one integration
Step 3 — Swap in a clientId
EPIS.init() requires a non-empty clientId string — the agent leaves 'your-client-id' as a placeholder, which will throw at runtime. Replace it with any string that identifies your app (e.g. 'my-app').
clientId isn’t validated against a registered domain today — see Security. Pick any string and you’re done; there’s no signup step blocking you from testing the integration right now.