super-ux 0.46.0 → 0.48.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +76 -0
- package/README.md +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,81 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.48.0 — 2026-08-22
|
|
4
|
+
|
|
5
|
+
**BP-235..241 — products with a long time-to-value.** Measured on
|
|
6
|
+
`babylovegrowth.ai`, the same category as BP-216..234's reference and the opposite answer to
|
|
7
|
+
almost every question: where that product is dense and instrumented, this one is patient.
|
|
8
|
+
Results arrive over months, most of a new account's numbers are zero on day one, and the
|
|
9
|
+
design's whole job is to make that read as *early* rather than as *broken*.
|
|
10
|
+
|
|
11
|
+
* **A disconnected source renders at the size its data would** (**BP-235**) — full card, one
|
|
12
|
+
sentence naming what connecting buys, the button. The dashboard's shape then does not change
|
|
13
|
+
when a source is added, and a new account reads as unfinished rather than empty.
|
|
14
|
+
* **Price the vanity metric in the currency the reader already has** (**BP-236**) — *80K
|
|
15
|
+
potential reach · $641 to buy this visibility via Ads*. A figure whose scale a user cannot
|
|
16
|
+
judge is a figure they discount.
|
|
17
|
+
* **If value takes months, put the months on the dashboard** (**BP-237**) — named phases with
|
|
18
|
+
ranges, beside the empty numbers rather than in an onboarding email. On these products the
|
|
19
|
+
first weeks look identical to failure, and the churn that follows is a reading error.
|
|
20
|
+
* **A composite score shows its parts in the same glance** (**BP-238**) — the ring tells a user
|
|
21
|
+
their state, the decomposition names their next action.
|
|
22
|
+
* **The card that is working says so on itself** (**BP-239**) — the complement of BP-217:
|
|
23
|
+
that one says do not blank a surface with a value, this one says where the progress signal
|
|
24
|
+
goes instead.
|
|
25
|
+
* **A guarantee under the CTA is the other way to remove the risk** (**BP-240**) — BP-229's
|
|
26
|
+
sibling. Two doors remove the *password*; a bounded guarantee removes the *bet*.
|
|
27
|
+
* **Two card levels, and the difference between them is the grouping** (**BP-241**) — different
|
|
28
|
+
radii, one step of tint, and a flattening rule below tablet as part of the pattern rather than
|
|
29
|
+
a fallback.
|
|
30
|
+
|
|
31
|
+
`practice-selection.md` gains three artifact rows: integration flow, long-time-to-value product,
|
|
32
|
+
and the dashboard row widened to reach the new set.
|
|
33
|
+
|
|
34
|
+
## 0.47.0 — 2026-08-21
|
|
35
|
+
|
|
36
|
+
**BP-216..227 — product dashboards.** The catalog had `Web apps, forms & performance` and
|
|
37
|
+
nothing about the screen a person opens every morning to decide what to do next. A dashboard
|
|
38
|
+
fails in ways neither a landing nor a report does: it goes stale without saying so, it encodes
|
|
39
|
+
state in a colour nobody can separate, and it blanks itself on every reload to prove it is
|
|
40
|
+
fetching. Twelve entries, every one measured on 2026-08-21 against a production surface
|
|
41
|
+
(`outrank.so/dashboard`, whose product half runs Semrush's Intergalactic), with the measurement
|
|
42
|
+
named in each `Why`.
|
|
43
|
+
|
|
44
|
+
The ones that change how a screen is built: the first block is *what to do next*, not what
|
|
45
|
+
happened (**BP-216**); a data surface **dates itself instead of blanking** (**BP-217**); a
|
|
46
|
+
number is a shape and is led like one — 32px at 32px leading (**BP-219**); a tint encodes the
|
|
47
|
+
**category**, never the state (**BP-220**); one 100% bar with a dot legend costs a text line
|
|
48
|
+
where a pie costs six (**BP-221**); a row **tints, it does not lift** (**BP-224**); an empty
|
|
49
|
+
cell **keeps its border**, because the grid's shape is the information (**BP-226**).
|
|
50
|
+
|
|
51
|
+
**BP-228..234 — the long SaaS landing, measured end to end.** A 20 806px production page, its
|
|
52
|
+
fourteen sections listed in order with the buyer question each one answers, and the finding that
|
|
53
|
+
the sequence is ordered by *when the question occurs* rather than by feature importance — the
|
|
54
|
+
mechanism precedes the capabilities because a buyer who does not believe the *how* does not read
|
|
55
|
+
the *what*. Section 12 repeats the hero **verbatim**, which is what lets a reader who scrolled
|
|
56
|
+
past it decide without scrolling back.
|
|
57
|
+
|
|
58
|
+
### Three old entries now say where they stop
|
|
59
|
+
|
|
60
|
+
This is the half that matters more than the new ids. A newer practice that quietly disagrees
|
|
61
|
+
with an older one leaves an auditor applying whichever they read first.
|
|
62
|
+
|
|
63
|
+
* **BP-117 — "one primary action per landing page"** is about *intent*, not button count, and it
|
|
64
|
+
was regularly read as the second. **BP-229** states the difference: two buttons that begin the
|
|
65
|
+
same job — an SSO door beside a credentialled one — are one action with two doors, and removing
|
|
66
|
+
the ghost in BP-117's name raises friction in the name of a rule about focus. BP-117 now
|
|
67
|
+
carries that pointer in its own entry.
|
|
68
|
+
* **BP-058 — "skeletons/progress for longer work"** now says it applies where there is **no
|
|
69
|
+
previous value**. On a surface that has already drawn data, a skeleton on re-fetch destroys a
|
|
70
|
+
reading the person could use, to signal a fetch they did not ask for.
|
|
71
|
+
* **BP-059 — "no info by color alone"** points at **BP-218**, which carries the CVD numbers that
|
|
72
|
+
make it a measurement rather than a principle: two of the reference's own status hues separate
|
|
73
|
+
by 6.9 under tritanopia.
|
|
74
|
+
|
|
75
|
+
Taxonomy gains `dashboard` and `data-density`. `practice-selection.md` gains six artifact rows —
|
|
76
|
+
long SaaS landing, dashboard home, KPI card, dense table, in-product upgrade prompt — because an
|
|
77
|
+
entry nothing routes to is an entry no skill can reach.
|
|
78
|
+
|
|
3
79
|
## 0.46.0 — 2026-08-20
|
|
4
80
|
|
|
5
81
|
**The check that decides whether a public number is real accepted any substring of the
|
package/README.md
CHANGED
|
@@ -231,7 +231,7 @@ The contracts every skill reads:
|
|
|
231
231
|
| [ux_doctor.py](plugins/super-ux/scripts/ux_doctor.py) | Contract doctor. It reports mixed or stale contract versions across a project's artifacts, files the tooling cannot find under their contract names, and audits produced against a base that is not there. `/ux-lint` checks a chain against itself; this checks it against the contract. Installed as `docs/ux/doctor.py`, read-only unless `--fix` |
|
|
232
232
|
| [best-practices-index.md](plugins/super-ux/skills/references/best-practices-index.md) | Generated tag index over the catalog: tag → ids, id → title. Read it to decide which entries to open; regenerated by `plugins/super-ux/scripts/bp_index.py` and checked for drift by the validator |
|
|
233
233
|
| [ux-design-principles.md](plugins/super-ux/skills/references/ux-design-principles.md) | How the agent thinks: the design pipeline (forward and backwards), task analysis, flow rules, heuristics PRN-01..24, the improvement procedure, anti-patterns |
|
|
234
|
-
| [best-practices.md](plugins/super-ux/skills/references/best-practices.md) | Living, tag-indexed catalog of
|
|
234
|
+
| [best-practices.md](plugins/super-ux/skills/references/best-practices.md) | Living, tag-indexed catalog of 241 proven practices: subscription-app laws, mobile/web/voice guidance (Apple HIG 2025, M3 Expressive, NN/g, Baymard, WCAG 2.2), monetization economics (RevenueCat/PLG 2025 benchmarks, ASO, freemium boundaries), web funnels end to end (landing, pricing, checkout, dunning, cancel), web2app (paid handoff, deferred deep links, storefront rules) and the funnel wiring that fails invisibly (what a personalization branch may vary, stand-up order, the three decisions a stored answer carries, GDPR Art. 13/17 timing, the access ladder), motion and page weight (HTTP Archive field data, W3C sustainability), accessibility as it actually fails (WebAIM Million, EAA/ADA exposure), frustration telemetry, gamification and trend governance, growth loops and referral mechanics, empty states, authentication (NIST SP 800-63B rev 4) and form recovery, motion craft and perceived quality, the defaults that make an interface read as generated, interface state, locale and platform surfaces (Web Interface Guidelines), visual craft, Figma structure |
|
|
235
235
|
| [practice-selection.md](plugins/super-ux/skills/references/practice-selection.md) | The deterministic bridge: product profile → mandatory consideration sets → per-artifact checklists → a compliance table where every pulled practice gets a verdict. No silent skips, no cargo cult |
|
|
236
236
|
| [funnel-research.md](plugins/super-ux/skills/references/funnel-research.md) | Reading a funnel market before designing one, `FR-01..FR-07`: where competitor funnels are visible, the four signals that survive when revenue is invisible, the fields that make a corpus comparable, which adjacent categories transfer, the stop before copying, and where each finding lands in the chain. Carried by `ux-foundation` and `ux-flows` |
|
|
237
237
|
| [component-guidelines.md](plugins/super-ux/skills/references/component-guidelines.md) | Which control for which job (radios/select/switch, sheet/alert, modal/disclosure, combobox, nav bar/rail, FAB, dates, toasts) and the platform rules of Apple HIG, Material 3, W3C ARIA APG and GOV.UK |
|
package/package.json
CHANGED