Add an account/organization settings page with tabs for Organization info,
User Management, Integrations, Advanced settings, and Billing.
AI Assistant:
Do NOT add custom styles, colors, or CSS overrides to ibl.ai SDK components.
They ship with their own styling. Keep the components as-is.
Do NOT implement dark mode unless the user explicitly asks for it.
When building custom UI around SDK components, use the ibl.ai brand:
- Primary: , Gradient:
linear-gradient(135deg, #00b0ef, #0058cc)
- Button:
bg-gradient-to-r from-[#2563EB] to-[#93C5FD] text-white
- Font: System sans-serif stack, Style: shadcn/ui new-york variant
- Use shadcn components for custom UI -- they share the same Tailwind
theme and render in ibl.ai brand colors automatically.
You MUST run
before telling the user the work is ready.
After all work is complete, start a dev server (
) so the user
can see the result at
http://localhost:3000.
is NOT a
replacement — it only holds the 3
shorthand variables (
,
,
). Next.js still reads
its runtime env vars from
.
Use
as the default package manager. Fall back to
if pnpm
is not installed. The generated app should live in the current directory,
not in a subdirectory.
Before running any
command, ensure the CLI is
up to date. Run
to check the current version, then
upgrade directly:
This is safe to run even if already at the latest version.
Before proceeding, check for a
in the project root. Look for
,
, and
variables.
If the file does not exist or is missing these variables, tell the user:
"You need an
with your platform configuration. Download the
template and fill in your values:
curl -o iblai.env https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/iblai.env
"
The page reads
,
/
, and
from
localStorage. Admin status is derived from the
array.
Note: The
component uses
internally -- it is
imported from
@iblai/iblai-js/web-containers/next
.
Run
before telling the user the work is ready: