better-design 0.41.0 → 0.43.0

package/README.md

@@ -25,6 +25,8 @@ The installer sends this label when creating a free key and records npm as the i
 
 Rerunning setup preserves existing connections. If setup reports a manual step, finish it first. Then ask your agent to list Better Design's design systems and confirm that a tool returns a result.
 
+If something does not work, run `npx better-design doctor`. It checks your key, the connection to the server, each client's configuration, the review hook in this project and your version, and prints the command that fixes each problem. It changes nothing.
+
 ## Try it
 
 Ask your agent:
@@ -45,7 +47,7 @@ the variables in every mode, the text and effect styles, and the components
 with their variant options. It writes them to one JSON file. You confirm the
 read in the plugin panel. Pass that file to `create-figma-prototype` as
 `kitPath` in model mode, and the prototype uses the kit's colours, font and
-radius.
+radius. Pass a `projectId` to also keep the kit on that project.
 
 A frame from a file that was not built from a Better Design library has no
 components to map, so pass `mode: "model"` and a catalog `system`. The plugin
@@ -64,8 +66,10 @@ Your agent keeps a map of the product in `.better-design/feature-map.json`:
 each feature, its flows, and the route, screen, components and data of every
 step. `build-feature-map` drafts it from `git ls-files`, `read-feature-map`
 names what a change to a flow touches, and `update-feature-map` adds, renames
-or removes a feature or flow in one call. The map stays in your repository;
-the tools store nothing.
+or removes a feature or flow in one call. The map can also hold one Main
+Quest, a goal for a set time with at most 3 initiatives, so the agent says
+when new work serves none of them. The map stays in your repository; the
+tools store nothing.
 
 ## Share your team's rules with every agent
 
@@ -121,16 +125,40 @@ holds the key can confirm it, and the code works for ten minutes.
 
 ## Review UI code
 
-Check changed JSX and TSX files in your project:
+Check changed JSX, TSX and CSS files in your project:
 
 ```bash
 npx better-design review
 ```
 
+To check each file your agent edits, add the review hook to your project:
+
+```bash
+npx better-design review --install-hook
+```
+
+It adds the hook for Claude Code and for every other agent whose folder the
+project has. Pick agents with `--host claude-code,codex,copilot,cursor,devin`
+or `--host all`. Findings go back to the agent the way each agent reads them.
+Codex asks you to approve the hook once with `/hooks`. Setup with `--project`
+adds the hook for the clients it configures. The hook runs the release that
+installed it; run the command again to move it to a newer release.
+
 It reads your `components.json`, the stylesheet it names and your UI folder, so
 a finding names your own theme colours and your components' variants. The
 check for classes Tailwind does not generate builds your Tailwind theme, which
 runs the plugins your stylesheet names, as your build does. The agent hook skips
 that check. Run `npx better-design review --help` for options.
 
+## Make a product video
+
+Ask your agent for a launch film, a changelog clip or an App Store preview.
+`plan-video` turns the one-line brief into beats, picks a Remotion component
+for each beat and writes the film's skeleton. `cut-screen-recording` measures
+a recording of your product with Remotion's own ffmpeg and cuts it into beats,
+with the browser chrome cropped and the camera on what moves. On this local
+server, `render-video-frames` renders chosen frames in your Remotion project
+and shows them to the agent, so it checks its work before the full render.
+The recording and the frames never leave your machine.
+
 [Installation guide](https://better-design.com/mcp/install) · [Design systems](https://better-design.com/design-systems) · [Website](https://better-design.com)