@fui-org/fui-cli 2.1.4 → 2.2.1

package/README.md

@@ -47,10 +47,9 @@ Installed fui with Bun? Install Playwright the same way, so fui finds it: `bun a
 
 ## Use with an AI agent
 
-`fui` installs two skills for each AI agent it finds, and refreshes them after every update:
-
-- `fui` teaches the agent the commands and safety rules. `fui skill` prints it.
-- `fui-skill` holds the FUI domain rules: module.json, components, tAPI and stored procedures, design systems.
+`fui` installs one skill, `fui`, for each AI agent it finds, and refreshes it after every update. It holds the commands, the
+safety rules and the FUI domain rules (module.json, components, tAPI and stored procedures, design systems); `fui skill`
+prints it. One AI agent handles each request from implementation through verification, without sub-agent hand-offs.
 
 | Agent       | Skills folder                  |
 | ----------- | ------------------------------ |
@@ -60,12 +59,22 @@ Installed fui with Bun? Install Playwright the same way, so fui finds it: `bun a
 
 For Claude Code it also installs the `fui-target` mod into `~/.claude/skills/fui-target`. Once a session runs `fui`, a line above the prompt shows the session target, for example `🧩 monitor-manager › device-list · fui use`.
 
-Installed an agent later? The next `fui` run adds its skills. To install by hand:
+Installed an agent later? The next `fui` run adds its skill. To install by hand:
 
 ```bash
 fui skill install [--agent claude,codex,antigravity|all]
 ```
 
+## Work with one agent
+
+Ask as usual, for example `add a search box and an edit dialog to /my-project/students`. The same agent understands the
+request, changes the UI and stored procedures, checks the result and fixes proven failures. Exact changes are handled
+directly; broader work gets a short internal plan without creating hand-off files. Checks run from cheapest to most
+expensive, and browser rendering is used only when pixels matter. After all assigned module work passes its checks, the
+agent publishes the module and deploys its SPs automatically. Say `do not upload`, `local only`, `draft` or `preview
+first` when you want it to stop before changing the server. Destructive operations and real-data writes still require
+explicit approval.
+
 ## Quick tour
 
 ```bash
@@ -114,8 +123,8 @@ fui config set api-base https://<fui-api-host>
 printf %s "$FUI_TOKEN" | fui config set api-token -
 ```
 
-Connection files from before the multi-zone layout (`_connections.json` without `"version": 2`) stop DB commands with a
-hint; convert them once with `fui db migrate` (the old file is kept in `_history/`).
+Connection files from before the multi-zone layout (`_connections.json` without `"version": 2`) are upgraded the first
+time `fui` reads them (the old file is kept in `_history/`). `fui db migrate` does the same for every project at once.
 
 ## Uninstall