version: "1.0.1" name: corex-installation description: >- Load when running mix corex.new, mix corex.design.build, adding {:corex} to mix.exs, configuring esbuild --format=esm --splitting, LiveSocket with csrfToken and hooks: { ...colocatedHooks, ...corex } in assets/js/app.js, use Corex in lib/*_web.ex, type="module" on app.js script tag, toggle.css select.css for mode/theme pickers, or toast_group layout in root layout.

Corex installation

New project

mix corex.new my_app

Existing app — order matters

1. {:corex, "~> 0.2.0"} → esbuild ESM splitting → LiveSocket + hooks → type="module" script → use Corex → mix assets.build

const liveSocket = new LiveSocket("/live", Socket, {
  params: { _csrf_token: csrfToken },
  hooks: { ...colocatedHooks, ...corex },
})

Lazy hooks: PascalCase keys (Dialog: () => import("corex/dialog")).

Design + optional toast

mix corex.design.build

Import toggle.css / select.css when using mode/theme/lang pickers.

MCP: plug Corex.MCP in dev only — see corex-mcp. Prefer --no-mcp for locked-down scaffolds. Never set allow_remote_access: true casually.

Also see: updating Corex → Hexdocs update.html / skill pointers under corex-installation; accessibility/theming → corex-design; language switcher → corex-navigation; Tableau Bandit port → corex-mcp.

Full checklist: sub-rule corex:installation. MCP installation_guide when server is running.