---
description: Scaffold or adapt a feature/page for a specific client instance (FPI, JPT, KEA, AGOB, ...).
argument-hint: <instance> + <what to add/adapt>
---

Per-instance work: **$ARGUMENTS**

Use the `multi-instance` agent:
- Identify whether this is all-instances or one — gate per-instance behaviour on `config('app.domain')` or a setting, never copy-paste divergence.
- Routing: add to the correct per-domain branch in `routes/web.php`, in the correct subdomain group.
- Frontend theme: fork only the Blade under `resources/views/frontend/{instance}/` when the design truly differs; reuse shared backend.
- Brevo: check whether this instance has email enabled/disabled before assuming mail delivery.
- No hard-coded lists — use DB models.
- Never commit `.env.*`.

If the task is "upgrade <instance> to Unified", map old features to the shared codebase, list gaps, migrate incrementally. Report shared vs instance-specific files + a test against the instance subdomain.