super-ux 0.48.0 → 0.48.1

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.48.1 — the UX chain gets an installable public front door
+
+A root skill card now states the boundary between behavior, copy, visuals and
+integrations. Portable trigger and behavioral evals cover the scenario chain,
+audit and brand path without pretending they have been run against a model. The
+README opens with one install and one cancellation-flow request; CI adds the
+pinned house audit, eval plant and social-preview check.
+
 ## 0.48.0 — 2026-08-22
 
 **BP-235..241 — products with a long time-to-value.** Measured on

package/README.md

@@ -3,6 +3,23 @@
 [![npm](https://img.shields.io/npm/v/super-ux)](https://www.npmjs.com/package/super-ux)
 [![CI](https://github.com/ssheleg/super-ux/actions/workflows/validate.yml/badge.svg)](https://github.com/ssheleg/super-ux/actions/workflows/validate.yml)
 [![license](https://img.shields.io/badge/license-MIT-green)](LICENSE)
+[![site](https://img.shields.io/badge/docs-skills.sshlg.me-8ab0ff)](https://skills.sshlg.me/skills/super-ux/)
+
+**Turn product intent into traced flows, screens and scenarios before an agent writes the interface.**
+
+```bash
+npx skills add ssheleg/super-ux
+```
+
+Ask: `Design the cancellation flow and every state that proves it works.`
+
+**[Detailed docs →](https://skills.sshlg.me/skills/super-ux/)**
+
+**[Docs, and every skill →](https://skills.sshlg.me/)** · [this skill's page](https://skills.sshlg.me/skills/super-ux/) · [follow @sshlg93 on X](https://x.com/intent/follow?screen_name=sshlg93)
+
+Loads in **DeepSeek Harness** (`dsh`) with **no plugin to write**: it reads the
+Agent Skills standard directly and scans `~/.agents/skills`, which is where
+`npx skills add` puts this pack.
 
 **Scenario-driven UI development for AI agents.** Claude Code, Cursor, and
 70+ other agents.
@@ -17,19 +34,29 @@ chain in `docs/ux/` becomes the source of truth, written and approved
 used as the checklist for evidence-backed audits of the code.
 
 ```mermaid
-flowchart LR
-    V["Vision<br/>essence · principles<br/>anti-vision"] --> F["Foundation<br/>personas · JTBD<br/>journeys · stories"]
-    F --> L["Flows<br/>task analysis<br/>+ branches"]
-    L --> S["Screens<br/>states · elements<br/>Figma frames"]
-    S --> C["Scenarios<br/>action → response<br/>alt + error paths"]
-    C --> B["Build UI<br/>only now"]
-    B --> A["Audit<br/>code vs the chain<br/>file:line evidence"]
-    A --> P["Fix plan<br/>Freq × Severity<br/>× Solvability"]
+%%{init: {'flowchart': {'curve': 'linear', 'useMaxWidth': true}}}%%
+flowchart TD
+    V["Vision · essence, principles, anti-vision"]
+    F["Foundation · personas, JTBD, journeys, stories"]
+    L["Flows · task analysis + branches"]
+    S["Screens · states, elements, Figma frames"]
+    C["Scenarios · action → response, alt + error paths"]
+    B["Build UI — only now"]
+    A["Audit · code vs the chain, file:line evidence"]
+    P["Fix plan · Frequency × Severity × Solvability"]
+
+    V --> F --> L --> S --> C --> B --> A --> P
     P --> B
     B -.->|same change| C
     V -.->|alignment check| B
 ```
 
+**The build sits after the scenarios on purpose.** Everything above it is a
+document the chain owns; everything below is code and what it is judged against.
+The two dotted edges are what keeps the chain honest: a change to user-facing
+behaviour updates the scenarios **in the same change**, and the vision is what the
+interface is checked back against.
+
 Every layer traces to the one above it. New product? Build it forward. Existing
 codebase? The same artifacts get filled in backwards from the code, tagged
 `inferred` until you confirm them, so the gap between "is" and "should" becomes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "super-ux",
-  "version": "0.48.0",
+  "version": "0.48.1",
   "scripts": {
     "test": "python3 test/validate.py && python3 test/brand_lint_test.py && python3 test/ux_lint_test.py && python3 docs/ux/lint.py && python3 docs/brand/lint.py"
   },