jig-ui 0.2.0 → 0.3.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 +16 -4
- package/dist/index.js +1794 -22
- package/package.json +1 -1
- package/templates/command-metadata.json +2 -2
- package/tokens/brand.default.css +9 -2
package/README.md
CHANGED
|
@@ -48,10 +48,22 @@ your surface needs — one brand file, one mode file:
|
|
|
48
48
|
Copy `brand.default.css` to `brand.<yourproject>.css` and edit that; `jig update`
|
|
49
49
|
will not overwrite a file you have changed.
|
|
50
50
|
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
51
|
+
Or let `jig init` do the above for you:
|
|
52
|
+
|
|
53
|
+
```
|
|
54
|
+
npx jig-ui@latest init
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
It detects your CSS system (Tailwind v4, Tailwind v3, plain CSS), derives a
|
|
58
|
+
brand colour from what your project already has (custom properties first,
|
|
59
|
+
then a Tailwind config, then the most frequent literal colour) instead of
|
|
60
|
+
asking cold, validates that colour against the contrast and collision
|
|
61
|
+
requirements stated in `brand.default.css` itself, writes
|
|
62
|
+
`.jig/tokens/brand.<project>.css` and `jig.config.json`, wires the `@import`
|
|
63
|
+
into your stylesheet when there is one unambiguous place to put it, and runs
|
|
64
|
+
a baseline `check` so you have a number to move. Add `--yes` to accept every
|
|
65
|
+
derived default non-interactively (the mode CI and agents run in). Re-running
|
|
66
|
+
`init` never overwrites a `jig.config.json` or brand file you have edited.
|
|
55
67
|
|
|
56
68
|
## Files
|
|
57
69
|
|