@fugood/bricks-project 2.25.0-beta.41 → 2.25.0-beta.42

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "@fugood/bricks-project",
-  "version": "2.25.0-beta.41",
+  "version": "2.25.0-beta.42",
   "main": "index.ts",
   "scripts": {
     "typecheck": "tsc --noEmit",
     "build": "bun scripts/build.js"
   },
   "dependencies": {
-    "@fugood/bricks-cli": "^2.25.0-beta.41",
+    "@fugood/bricks-cli": "^2.25.0-beta.42",
     "@huggingface/gguf": "^0.3.2",
     "@iarna/toml": "^3.0.0",
     "@modelcontextprotocol/sdk": "^1.15.0",

package/package.json.bak

@@ -1,13 +1,13 @@
 {
   "name": "@fugood/bricks-ctor",
-  "version": "2.25.0-beta.41",
+  "version": "2.25.0-beta.42",
   "main": "index.ts",
   "scripts": {
     "typecheck": "tsc --noEmit",
     "build": "bun scripts/build.js"
   },
   "dependencies": {
-    "@fugood/bricks-cli": "^2.25.0-beta.41",
+    "@fugood/bricks-cli": "^2.25.0-beta.42",
     "@huggingface/gguf": "^0.3.2",
     "@iarna/toml": "^3.0.0",
     "@modelcontextprotocol/sdk": "^1.15.0",

package/skills/bricks-design/SKILL.md

@@ -1,30 +1,20 @@
 ---
 name: bricks-design
 description: >-
-  Visual design discipline for Applications and Subspaces — type,
-  palette, asset acquisition, design language, system commitment,
-  visual rhythm, brand. TRIGGER for visual / aesthetic / system /
-  style / brand-asset work even when the user names the surface in
-  product terms — slideshow / pitch deck / introduction / explainer
-  / storyboard; kiosk / signage / menu board / lobby / reception /
-  wayfinding / retail / hospitality / museum / transit; translate /
-  port / rebuild from Figma / HTML / screenshot / website / PDF /
-  brand book; vague creative brief ("design something for the
-  lobby"); branded scene work; iteration on existing Subspace
-  (rework, redesign, audit visual system, tighten the type / palette
-  / motion / rhythm). For end-to-end briefs (kiosk, dashboard,
-  interactive screen) this skill invokes in parallel with bricks-ux,
-  which carries the interaction / flow / usability layer. SKIP for
-  pure usability / flow / journey / affordance / feedback / recovery
-  / accessibility / multilingual audits — those go to bricks-ux. SKIP
-  for single-Brick or Generator template work
-  (create-brick-or-generator), debugging or refactoring with no
-  design intent, or non-display deliverables (CLI, server, tooling).
-  Encodes architecture truths, performance and complexity guardrails,
-  input-translation rules, visual languages library, Direction
-  Advisor for vague briefs, Media Flow protocol for branded work.
-  Verification toolchain (compile, preview tool selection, on-device DevTools,
-  Path 1/2/3) lives in the bricks-ctor skill.
+  Visual design discipline for Applications and Subspaces — type, palette, asset
+  acquisition, design language, system commitment, visual rhythm, brand. TRIGGER
+  for visual / aesthetic / system / style / brand-asset work even when named in
+  product terms — slideshow, pitch deck, explainer, kiosk, signage, menu board,
+  lobby, wayfinding, retail, museum, transit; translate or rebuild from Figma /
+  HTML / screenshot / website / PDF / brand book; vague creative briefs; branded
+  scenes; rework or audit of an existing Subspace's type / palette / motion /
+  rhythm. For end-to-end briefs invoke in parallel with bricks-ux (interaction /
+  flow layer). SKIP for pure usability / flow / accessibility audits (bricks-
+  ux), single-Brick or Generator template work (create-brick-or-generator),
+  debugging without design intent, or non-display deliverables. Encodes
+  architecture truths, performance guardrails, input-translation rules, visual
+  languages, Direction Advisor, Media Flow protocol; verification toolchain
+  lives in bricks-ctor.
 ---
 
 # BRICKS Design

package/skills/bricks-ux/SKILL.md

@@ -1,26 +1,20 @@
 ---
 name: bricks-ux
 description: >-
-  Interaction design and end-user experience for any Application or
-  Subspace built on Canvases, Bricks, Generators, Data, DataCalculation.
-  TRIGGER on usability / flow / interaction / journey / state /
-  affordance / feedback / recovery / accessibility audits and design
-  work — "audit this flow", "improve usability", "design the wait
-  state", "fix the error path", "make the kiosk usable", "what does the
-  user do when X breaks", "design the QR scan UX", "design the payment
-  flow", "design the mic / listening state", "design the monitor's
-  alarm state", "design for multilingual", "design for low vision",
-  "design idle and attractor states". Also triggers in parallel with
-  visual-design work for end-to-end deliverables (kiosk / signage /
-  dashboard / interactive screen / pitch deck) where the interaction
-  shape matters as much as the look. SKIP for purely visual / aesthetic
-  / system / style / brand-asset / typography / palette work — those
-  are visual design, not interaction design. Encodes a universal
-  user-journey spine, interaction archetypes, pressable composition,
-  monitoring-screen discipline, designed flow states, accessibility,
-  and a tiered UX critique. Hardware floors are deployment-relative;
-  web habits (hover affordances, modal-as-default, scroll, page-submit
-  forms) do not transfer.
+  Interaction design and end-user experience for any Application or Subspace
+  built on Canvases, Bricks, Generators, Data, DataCalculation. TRIGGER on
+  usability / flow / interaction / journey / state / affordance / feedback /
+  recovery / accessibility audits and design work — "audit this flow", "improve
+  usability", "design the wait state", "make the kiosk usable", "design the
+  payment flow", "design idle and attractor states", "design for multilingual /
+  low vision". Also triggers in parallel with visual-design work for end-to-end
+  deliverables (kiosk, signage, dashboard, interactive screen, pitch deck) where
+  interaction shape matters as much as look. SKIP for purely visual / aesthetic
+  / style / brand-asset / typography / palette work — that is bricks-design.
+  Encodes a universal user-journey spine, interaction archetypes, pressable
+  composition, monitoring-screen discipline, designed flow states,
+  accessibility, tiered UX critique; hardware floors are deployment-relative and
+  web habits do not transfer.
 ---
 
 # BRICKS UX