Update the UI

When Enjab UI changes, the Changelog lists exactly what changed and the action to adopt it. Update your project by applying the entries you have not adopted yet.

The update prompt

Hand an agent this message:

Update this project to the latest Enjab UI. Read https://developers.enjab.ae/llms.txt and
the changelog at https://developers.enjab.ae/docs/changelog, then apply ONLY the changelog
items this project has not adopted yet. Re-install changed components with
`npx shadcn add @enjab-ui/<name>` (overwrite). Re-apply the theme if tokens changed.
Do not refactor or restyle anything else, keep the change surface minimal.

The agent will fetch the docs and the changelog, check your project against the latest entries, and apply only what you have not already adopted.

How updates work

Read the changelog

Read the Changelog (or fetch https://developers.enjab.ae/docs/changelog). Note which components and design tokens changed.

Identify what you need

Compare your project's installed components against the changelog. You only need to update the components and theme items your tool actually uses.

Reinstall changed components

For each component that changed and that your project uses, run:

npx shadcn add @enjab-ui/<name> --overwrite

This pulls the latest version and overwrites the local copy. For example:

npx shadcn add @enjab-ui/button --overwrite
npx shadcn add @enjab-ui/data-table --overwrite

Update the theme if tokens changed

If the changelog lists theme changes (colors, fonts, radius, or sidebar), reinstall the theme:

npx shadcn add https://ui.enjab.ae/r/theme.json --overwrite

Always reinstall theme FIRST if you're also adding other components, since every component depends on the design tokens.

Keep the change surface minimal

Only update components your tool uses. Do not refactor or restyle anything else. The goal is to stay in sync with Enjab UI without introducing unrelated changes.

If a component update requires a prop change (for example, a new required parameter), the agent will catch it during testing and show you what changed in the component's API.