@askewly/design 0.5.1 → 0.6.0

package/README.md

@@ -1,31 +1,34 @@
-# @askewly/design
-
-Query, inject, and verify the [Askewly Design](https://ui.askewly.com) system from your terminal or coding agent.
-
-```bash
-npx @askewly/design verify src
-```
-
-## Commands
-
-| Command | What it does |
-|---|---|
-| `verify [dir]` | Scan for color values that bypass the token system — hex literals and raw `rgb()`/`hsl()`/`oklch()`. Comments and SVG markup are exempt. |
-| `terms search <query>` | Search the UI vocabulary (562 terms, Korean + English). |
-| `terms show <id>` | Definition, aliases, visual anatomy, anti-use cases, prompt phrases. |
-| `tokens` | Print the design token set. |
-| `init [dir]` | Drop token CSS into a project. |
-| `add <recipe>` | Add a component recipe. |
-| `recipes list` / `recipes show <id>` | Agent-ready implementation contracts (45 recipes). |
-
-## Why `verify` exists
-
-A screenshot cannot tell `#3B82F6` from `var(--color-accent)` — they render identically. Whether a screen actually uses the token system is a question for a machine, not an eye.
-
-`verify` exits `1` on violations and prints `file:line [rule] excerpt`, so a coding agent can read the list, fix, and re-measure.
-
-Exempt by design: generated token files (`tokens.css`, `askewly.css`), build directories, comments, and SVG markup.
-
-## License
-
-MIT
+# @askewly/design
+
+Query, inject, and verify the [Askewly Design](https://ui.askewly.com) system from your terminal or coding agent.
+
+```bash
+npx @askewly/design verify src
+```
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `verify [dir]` | Scan for color values that bypass the token system — hex literals and raw `rgb()`/`hsl()`/`oklch()`. Comments and SVG markup are exempt. |
+| `terms search <query>` | Search the UI vocabulary (562 terms, Korean + English). |
+| `terms show <id>` | Definition, aliases, visual anatomy, anti-use cases, prompt phrases. |
+| `tokens` | Print the design token set. |
+| `init [dir]` | Drop token CSS into a project. |
+| `add <recipe>` | Add a component recipe. |
+| `recipes list` / `recipes show <id>` | Agent-ready implementation contracts (45 recipes). |
+| `assets search <query>` / `assets show <id>` | One md per asset (registry + recipes): definition, usage rules, install command. Bundled, works offline. `show` on an unknown id exits `1` with 3 closest ids (0.6.0). |
+| `site list` / `site get <slug> [dir]` | Download a reproduced-site bundle: structure only (code, layout, motion, text). Images are same-size blank placeholders; video, audio and fonts are left out (originals stay with their owners). Verifies sha256, refuses a non-empty dir, unknown slug exits `1` with closest slugs. Base URL override: `ASKEWLY_SITE_BUNDLE_URL`. |
+| `prompt <id>` | Paste-ready agent prompt: asset md URL + install command + usage rules + one-line instruction (0.6.0). |
+
+## Why `verify` exists
+
+A screenshot cannot tell `#3B82F6` from `var(--color-accent)` — they render identically. Whether a screen actually uses the token system is a question for a machine, not an eye.
+
+`verify` exits `1` on violations and prints `file:line [rule] excerpt`, so a coding agent can read the list, fix, and re-measure.
+
+Exempt by design: generated token files (`tokens.css`, `askewly.css`), build directories, comments, and SVG markup.
+
+## License
+
+MIT