better-design 0.24.0 → 0.31.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  Give your coding agent design systems, UI and UX guidance, icons, and code reviews through MCP.
4
4
 
5
- Works with Codex, Claude Code, Cursor, VS Code, Windsurf, and other MCP clients.
5
+ Works with Codex, Claude Code, Cursor, VS Code, Devin, Antigravity, and other MCP clients.
6
6
 
7
7
  ## Install
8
8
 
@@ -15,12 +15,56 @@ npx better-design
15
15
 
16
16
  The first installs the agent skill. The second connects Better Design to your coding tools. Restart your agent after setup.
17
17
 
18
+ If you have no account, setup creates a free key for you. Using that key accepts the [Terms of Service](https://better-design.com/terms) at the version setup prints. Setup saves the key in `~/.better-design/key` and reuses it when you run it again on the same machine. To start over, delete that file.
19
+
20
+ Your AI client loads Better Design at its next start. To get an answer in the session that ran setup, run `npx better-design ask "<question>"`, or add `--ux` for the UX principles.
21
+
22
+ Install links can record where you found Better Design with `npx better-design --source docs`.
23
+ Supported source labels are `docs`, `github`, `claude_directory`, `openai_catalog`, `campaign`, and `unknown` (the default).
24
+ The installer sends this label when creating a free key and records npm as the install method. It does not infer your referral source or active client from the editors installed on your computer.
25
+
18
26
  ## Try it
19
27
 
20
28
  Ask your agent:
21
29
 
22
30
  > Use Better Design to build a settings page with my project's design system, then review it for accessibility and consistency.
23
31
 
32
+ ## Build a prototype from Figma
33
+
34
+ With the Better Design plugin open in a Figma file, `create-figma-prototype`
35
+ turns a frame into one HTML page built from that design system's components.
36
+ Name a frame, or omit the name to take the current selection. The server
37
+ starts a relay on `http://localhost:4397` that only the plugin talks to, so
38
+ the file never leaves your machine. This tool is local only: the hosted
39
+ connectors cannot reach your Figma.
40
+
41
+ A frame from a file that was not built from a Better Design library has no
42
+ components to map, so pass `mode: "model"` and a catalog `system`. The plugin
43
+ asks you to confirm the frame. Your agent is the model: the tool writes a
44
+ prompt file and the frame's image, your agent writes the page on its own
45
+ plan, and a second call with `frameId` and `answerPath` checks the page and
46
+ lists every layer that did not make it. No API key is needed. To use a local
47
+ model instead, pass `provider: "openai-compatible"`: the tool calls Ollama at
48
+ `http://localhost:11434/v1` with `gemma4:latest`, or the server in
49
+ `BETTER_DESIGN_MODEL_BASE_URL`, with `BETTER_DESIGN_MODEL_API_KEY` if it needs
50
+ one.
51
+
52
+ ## Map your product's features and flows
53
+
54
+ Your agent keeps a map of the product in `.better-design/feature-map.json`:
55
+ each feature, its flows, and the route, screen, components and data of every
56
+ step. `build-feature-map` drafts it from `git ls-files`, `read-feature-map`
57
+ names what a change to a flow touches, and `update-feature-map` adds, renames
58
+ or removes a feature or flow in one call. The map stays in your repository;
59
+ the tools store nothing.
60
+
61
+ ## Share your team's rules with every agent
62
+
63
+ Paste your team's rules into
64
+ [Team rules](https://better-design.com/dashboard/settings/team-rules), one
65
+ Markdown document of up to 32 KB. `get-team-rules` gives them to any agent
66
+ that uses your key, and `get-review-rules` checks the work against them.
67
+
24
68
  ## Review UI code
25
69
 
26
70
  Check changed JSX and TSX files in your project: