@vireo-ai/trellis-ui 0.1.60 → 0.1.61

package/packages/theme-engine/generated/schemas/theme-manifest-v1.json

@@ -0,0 +1,79 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trellis.build/schemas/theme-manifest-v1.json",
+  "additionalProperties": false,
+  "type": "object",
+  "required": [
+    "$schema",
+    "formatVersion",
+    "engineVersion",
+    "base",
+    "commits",
+    "outputs"
+  ],
+  "properties": {
+    "$schema": {
+      "const": "https://trellis.build/schemas/theme-manifest-v1.json",
+      "type": "string"
+    },
+    "formatVersion": {
+      "const": 1,
+      "type": "number"
+    },
+    "engineVersion": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "base": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "commits": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "outputs": {
+      "type": "array",
+      "items": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "type": "object",
+            "required": [
+              "format",
+              "path"
+            ],
+            "properties": {
+              "format": {
+                "const": "tailwind",
+                "type": "string"
+              },
+              "path": {
+                "minLength": 1,
+                "type": "string"
+              }
+            }
+          },
+          {
+            "additionalProperties": false,
+            "type": "object",
+            "required": [
+              "format",
+              "path"
+            ],
+            "properties": {
+              "format": {
+                "const": "dtcg",
+                "type": "string"
+              },
+              "path": {
+                "minLength": 1,
+                "type": "string"
+              }
+            }
+          }
+        ]
+      }
+    }
+  }
+}

package/packages/theme-engine/skills/create-trellis-theme/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: create-trellis-theme
+description: Create or tune a Trellis theme from brand, product, or visual direction using the knob catalog and source-controlled patch commits. Use for theme-wide color, typography, density, shape, depth, composition, or motion changes, rather than component-specific CSS fixes.
+---
+
+# Create a Trellis theme
+
+Translate the requested design direction into the smallest sufficient sequence of Theme Patch Commits. Preserve the
+workspace as ordinary source: a complete base, an append-ordered JSONL log, and deterministic generated outputs.
+
+## Locate the toolchain and workspace
+
+Locate the authoring resource root: the directory containing `THEME_AUTHORING.md` and `generated/knobs/v1/`.
+For this packaged skill, it is two directories above the skill folder (`../../` from
+`skills/create-trellis-theme/`). If the skill was copied into an agent's skill directory, locate those resources in the
+project's installed `@vireo-ai/trellis-ui` package, under `packages/theme-engine/` (normally
+`node_modules/@vireo-ai/trellis-ui/packages/theme-engine/`). In the Trellis repository, the root is
+`packages/theme-engine/`.
+All resource paths below are relative to this root, not the application working directory.
+
+Read `THEME_AUTHORING.md`. Confirm the local CLI is available before changing source. In a consumer project, use
+`npm exec --no -- trellis …` from the project root; this uses the installed command without fetching another package.
+In the Trellis repository, use `pnpm trellis …`. The examples below use the consumer invocation.
+If the CLI, guide, or catalog is missing, report the missing resource and the installed package version; do not guess
+config paths or silently download a replacement toolchain.
+
+Locate the intended `theme.json`; do not infer a repository-wide active theme. If several Theme Workspaces exist, use
+the one belonging to the application or site in scope. A request to create a new theme authorizes initializing its
+workspace with `npm exec --no -- trellis theme init <directory>`. Reuse the existing workspace for tuning requests.
+
+The versioned Theme Config schema is at `generated/schemas/theme-config-v1.json` and identifies itself as
+`https://trellis.build/schemas/theme-config-v1.json`. A config's own `$schema` property is optional editor metadata:
+the compiler does not require or insert it, and a Theme Patch Commit must not add or remove it as a design change.
+
+Inspect the workspace's `theme.json`, `base.json`, and relevant recent lines of `commits.jsonl`. Never hand-edit a
+configured generated artifact.
+
+## Discover knobs progressively
+
+1. Read `generated/knobs/v1/manifest.json` for the available axes, semantic groups, tier counts, and impact scopes.
+2. Search `index.json` with filesystem or JSON tools for words from the request. Keep the result narrow; do not load the
+   complete index into the conversation.
+3. Search Primary and Tuning entries first. Map promising index entries' `group` IDs to the manifest's group `file`
+   paths, and open only those files.
+4. In a group file, use the knob's path, description, constraints, defaults, parameters, `patch.operation`, and
+   `patch.missingParents` to construct valid operations.
+5. Substitute every `{parameter}` with one of the documented values before emitting a JSON Pointer.
+
+The escalation tiers are intentional:
+
+- **Primary:** establish identity and broad character. Prefer these first.
+- **Tuning:** refine a specific relationship after the primary direction is sound.
+- **Expert:** change low-level policy only when Primary and Tuning controls cannot express the result.
+- **Escape Hatch:** set exact authored values that bypass generator behavior. Use only for an explicit need and state
+  why the higher-level controls were insufficient.
+
+Do not use many low-level knobs to simulate a higher-level change. Exact palette steps are an escape hatch, not the
+normal way to select an accent or neutral direction.
+
+## Author one coherent commit
+
+Create a temporary JSON file containing one `ThemePatchCommit`:
+
+```json
+{
+  "message": "Make motion faster and more direct",
+  "operations": [
+    {"op": "replace", "path": "/motion/tempo", "value": 0.7},
+    {"op": "replace", "path": "/motion/elasticity", "value": 0.1}
+  ]
+}
+```
+
+Use only supported RFC 6902 `add`, `remove`, and `replace` operations. Follow catalog constraints exactly. When a knob
+lists missing parents, add the required structure before its leaf in the same commit. Array members may be replaced,
+but array membership cannot be changed.
+
+Prefer the fewest leaf operations that express one design intention. Do not fill optional fields merely because they
+exist, rewrite the base to record an iteration, or rewrite earlier commits for a follow-up adjustment.
+
+Apply the candidate through the toolchain:
+
+```bash
+npm exec --no -- trellis theme apply path/to/theme.json path/to/candidate.json
+```
+
+An accepted apply appends one canonical JSONL record and refreshes selected outputs. If validation or compilation
+fails, use the diagnostics and catalog metadata to correct the candidate; do not patch around the compiler.
+If apply reports a concurrent commit-log change, reload the workspace and reassess the candidate before retrying.
+
+## Inspect and iterate
+
+Review `commits.jsonl`, generated outputs, and the Git diff. When a runnable application is available, inspect
+representative components in both light and dark appearances, including text hierarchy, controls, nested surfaces,
+focus, disabled and selected states, one overlay, and motion affected by the change.
+
+Treat the user's next instruction as a new commit against the current materialized theme. Keep attribution and rollback
+in Git; do not invent conversation state, snapshots, branches, undo commands, or a second revision graph.
+
+Use `npm exec --no -- trellis theme build <manifest>` after manual source or merge changes, and
+`npm exec --no -- trellis theme check <manifest>` for a read-only stale-output check. `init` creates source files;
+run `build` to produce the initial outputs. Paths in the manifest resolve relative to the manifest; CLI operands
+resolve from the command's working directory.
+
+## Hand off
+
+Report the design intention, knob paths and tiers used, accepted diagnostics, generated outputs, and checks performed.
+Call out any Expert or Escape Hatch use explicitly. Do not paste generated CSS unless the user asks for it.

package/packages/client/types/components/runtime-docs.d.ts

@@ -1,2 +0,0 @@
-declare const componentRuntimeDocs: import("../docs/transition-docs").ComponentTransitionDocs[];
-export { componentRuntimeDocs };