Overview
Bring an existing Enjab tool up to date on both Enjab UI and Enjab Auth, with a minimal change surface.
Enjab evolves. Updating a tool means tracking two contracts, the Enjab UI design system and the Enjab Auth integration, 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.
Two 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.
Update everything at once
To bring a tool up to date on both UI and Auth in one go, use the single update-everything prompt on the changelog overview. It reads the central docs and both changelogs, works out what your project is missing, and applies only that.
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)
Hand these to your agent and they can bring your tool up to the current standard, applying only the delta.