Overview

Bring an existing Enjab tool up to date on Enjab UI, Enjab Auth, Enjab RAG, and the Engineering Standards, with a minimal change surface.

Enjab evolves. Updating a tool means tracking the backbones, the Enjab UI design system, the Enjab Auth integration, the Enjab RAG connection, and the Engineering Standards, and adopting only what changed. The principle is always the same: apply ONLY the changelog entries your tool has not adopted, and touch nothing else.

Minimal surface

Updates are not refactors. Send your agent the Changelog, have them identify which entries your tool has not adopted yet, and apply exactly those. Stop there. Do not restyle or reorganize surrounding code.

The tracks

Update the UI

Re-install changed Enjab UI components and re-apply the theme, per the Enjab UI changelog.

Update the auth integration

Re-sync the drop-in reference files and re-check the integration rules, per the Enjab Auth changelog.

Connect to Enjab RAG

Wire the tool/agent to the shared knowledge base and keep it current, per the Enjab RAG changelog.

Update to the standards

Adopt the infrastructure and process rules (security, deployment, pipeline), per the Engineering Standards changelog.

Update everything, one prompt

Hand this to a coding agent to bring a tool up to date on Enjab UI, Enjab Auth, Enjab RAG, and the Engineering Standards in one go. It reads the central docs, works out what the project has not adopted, and applies only that. For a focused update of just one area, use the tracks above.

Update everything (UI + Auth + RAG + Standards)

Update this project to the latest Enjab standards (UI, Auth, RAG, and Engineering Standards).
Read https://developers.enjab.ae/llms.txt and the changelog at
https://developers.enjab.ae/docs/changelog (the Enjab UI, Enjab Auth, Enjab RAG, and
Engineering Standards pages), then apply ONLY the changelog entries this project has not
adopted yet.

For Enjab UI: re-install changed components with `npx shadcn add @enjab-ui/<name>`
(overwrite) and re-apply the theme with `npx shadcn add https://ui.enjab.ae/r/theme.json`
if tokens changed.

For Enjab Auth: re-sync the drop-in reference files (lib/enjab-auth.ts, the callback and
logout routes, proxy.ts) and re-check the integration rules (re-validate every request via
/userinfo with cache: "no-store", no login UI of your own, confirmed per-tool sign-out,
access is binary unless the tool is role-aware).

For Enjab RAG: if this is an agent, connect it to the shared knowledge base as an MCP server
at https://rag.enjab.ae/api/mcp (Bearer enjabrag_... key) and have it call `search` before
answering operational questions; if it is a backend, call /api/search (read) and /api/ingest
(write). 

For the Engineering Standards: check the project against each published standard (security,
deployment, pipeline, and the like) and adjust config, CI/CD, and code to match the ones it
has not adopted.

Do not refactor or restyle anything else. Keep the change surface minimal.

Live contract

This site is the single source of truth for every Enjab tool, published as plain text for agents:

The contract: https://developers.enjab.ae/llms.txt
What changed: the Changelog (Enjab UI, Enjab Auth, Enjab RAG, Engineering Standards)

Hand these to your agent and they can bring your tool up to the current standard, applying only the delta.