@csszyx/mcp-server 0.15.2 → 0.16.0

package/llms-full.txt

@@ -2691,6 +2691,21 @@ CSS custom properties (`--*`) are passed through unchanged.
 - Spaces in values are normalised to underscores: `repeat(3, 1fr)` → `repeat(3,_1fr)`.
 - Works inside `dynamic()` at runtime — the same compiler logic handles the `css` key.
 
+### Custom property as a key
+
+A CSS custom property may also be written as a key on the `sz` object itself, which is the shorter form when a token sits beside the utilities that read it. It produces the same class as the `css: {}` spelling and nests under a variant like any other key.
+
+| Concept             | Example `sz` Prop                     | Output Class                | Note                              |
+| :------------------ | :------------------------------------ | :-------------------------- | :-------------------------------- |
+| **Key spelling**    | `{ '--my-color': 'red' }`             | `[--my-color:red]`          | same class as `css: {}`           |
+| **Inside variant**  | `{ dark: { '--my-color': 'white' } }` | `dark:[--my-color:white]`   | works in all variants             |
+| **Numeric value**   | `{ '--my-alpha': 0.18 }`              | `[--my-alpha:0.18]`         | numbers coerced to string         |
+| **Spaced value**    | `{ '--my-edge': '1px solid red' }`    | `[--my-edge:1px_solid_red]` | spaces → underscores              |
+| **Bracketed value** | `{ '--my-cols': '[a] 1fr [b]' }`      | `[--my-cols:[a]_1fr_[b]]`   | brackets kept as written          |
+| **Case**            | `{ '--MyToken': 1 }`                  | `[--MyToken:1]`             | case kept; `--` is case-sensitive |
+
+The value is a declaration value, so it is a string or a number; `false` switches the property off like any key. An object body has no declaration to lower and the type rejects it; nest a variant instead. A runtime value is hoisted like any other and read back as `[--my-color:var(--_sz---my-color)]`.
+
 
 # Sizing
 
@@ -4087,9 +4102,13 @@ the built HTML carries no executable inline script and a strict CSP
 If an `sz`-generated utility also appears as a static string or template quasi in a
 source-level `class` or `className` attribute/property (including a `clsx(...)`
 expression), csszyx keeps that class unmangled. This ensures raw and `sz` consumers
-continue to reference the same emitted rule. Use `mangleExclude` when the class is
-only visible through an imported constant, DOM selector/class API, ignored
-dependency, downstream macro, or another value unavailable to the source scan.
+continue to reference the same emitted rule. When something else depends on the
+class NAME — a stylesheet matching by attribute (`[class*="bg-tag"]`), a DOM
+query, a class assembled outside any visible `className` — list it in
+`production.manglePreserve` (exact name, or a prefix ending in `*`); the
+hybrid-hazard warning prints a paste-ready value. `production.mangleExclude` is
+the other switch: it keeps the allocator from producing a token equal to a short
+class in third-party CSS, and never keeps a csszyx class from being renamed.
 
 Final-output class mangling is available in Vite, Webpack, and Rollup. The esbuild
 adapter keeps class names readable (and warns when `production.mangle: true` is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@csszyx/mcp-server",
-  "version": "0.15.2",
+  "version": "0.16.0",
   "description": "Model Context Protocol (MCP) server for csszyx — enables AI agents to understand and generate sz props",
   "license": "MIT",
   "type": "module",
@@ -28,9 +28,9 @@
     "node": "^22.18.0 || >=24.11.0"
   },
   "dependencies": {
-    "@csszyx/cli": "0.15.2",
-    "@csszyx/compiler": "0.15.2",
-    "@csszyx/unplugin": "0.15.2",
+    "@csszyx/cli": "0.16.0",
+    "@csszyx/compiler": "0.16.0",
+    "@csszyx/unplugin": "0.16.0",
     "@modelcontextprotocol/sdk": "^1.30.0",
     "zod": "^4.4.3"
   },