super-ux 0.41.4 → 0.42.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 +70 -0
- package/package.json +4 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,60 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.42.0 — 2026-08-17
|
|
4
|
+
|
|
5
|
+
**The pack has carried the growth vocabulary since long before it could be asked for it.**
|
|
6
|
+
Counted across `plugins/super-ux`: **448** mentions of funnels, **499** of onboarding, **493**
|
|
7
|
+
of paywalls, **196** of retention, **171** of activation, **100** of referral. `retention`,
|
|
8
|
+
`onboarding`, `paywall`, `winback`, `lifecycle`, `activation`, `virality` and `referral` are
|
|
9
|
+
first-class tags in the practice taxonomy. `references/funnel-research.md` is 190 lines of
|
|
10
|
+
method, `FR-01`..`FR-07`. And not one of those words appeared in any skill's `description`.
|
|
11
|
+
|
|
12
|
+
That mattered more than it looks, because **a description is a routing surface**. The
|
|
13
|
+
umbrella's prompt hook may only fire on words the skill itself advertises — the fixture that
|
|
14
|
+
enforces it does a literal substring check — so fifteen of fifteen realistic growth prompts
|
|
15
|
+
reached no route at all: `как повысить ретеншн пользователей`, `спроектируй воронку
|
|
16
|
+
активации`, `добавь пейволл после онбординга`, `improve user retention`, `reduce churn on the
|
|
17
|
+
trial`, `add a paywall screen`. Measured by `test/route_coverage.js` in the umbrella.
|
|
18
|
+
|
|
19
|
+
### Two descriptions, and which word goes where is not a preference
|
|
20
|
+
|
|
21
|
+
`funnel-research.md`'s own `FR-07` already says where each finding lands, so the split follows
|
|
22
|
+
it rather than convenience:
|
|
23
|
+
|
|
24
|
+
| Word | Skill | Why that one |
|
|
25
|
+
|---|---|---|
|
|
26
|
+
| funnel, onboarding, paywall, activation funnel | `ux-flows` | *"The funnel's step chain and its branches → `docs/ux/flows.md`"* — and this skill's body already names the chain (ad → landing → quiz → loading → offer → paywall → checkout → success) |
|
|
27
|
+
| user retention, churn | `ux-foundation` | *"Who the buyer is, what job they are hiring the product for → `foundation.md`"*; a journey covers before, **during and after**, which is where retention is won and churn starts |
|
|
28
|
+
|
|
29
|
+
Neither skill could carry the other's words honestly, which is why the route now fronts two
|
|
30
|
+
skills rather than one.
|
|
31
|
+
|
|
32
|
+
### The English half is phrases and the Russian half is bare words, and that was measured
|
|
33
|
+
|
|
34
|
+
A first pass advertised the bare `activation` and `retention`. The umbrella's matcher stems
|
|
35
|
+
them to `activat-` and `retent-`, and the probe caught the cost immediately: `activate the
|
|
36
|
+
virtualenv` and `activate the feature flag` routed to `/ux`, and so did `retention policy for
|
|
37
|
+
logs`. The English words became `activation funnel` and `user retention`; «активация» and
|
|
38
|
+
«ретеншн» stayed single words, because nobody here writes «активация» about a virtualenv.
|
|
39
|
+
After the change all three noise cases are silent and every growth prompt still routes.
|
|
40
|
+
|
|
41
|
+
**Budget:** `ux-flows` 592 → 884 characters, `ux-foundation` 401 → 619. Both inside the 970
|
|
42
|
+
working limit with room left, which was the point of not spending it on the bare words.
|
|
43
|
+
|
|
44
|
+
`python3 test/validate.py` → `OK (3500 checks)`; the full gate green.
|
|
45
|
+
|
|
46
|
+
## 0.41.5 — 2026-08-16
|
|
47
|
+
|
|
48
|
+
**`copywriting` now answers when somebody asks for a landing page.** The unqualified
|
|
49
|
+
`сделай лендинг` and `build a landing page` reached no route at all — a landing is the
|
|
50
|
+
canonical two-craft surface, and the ask for one arrived at neither craft.
|
|
51
|
+
|
|
52
|
+
Both phrases are advertised here and in `sheleg-design`, so they reach the two together,
|
|
53
|
+
which is what the family's composition order says a landing needs. Verb phrases rather than
|
|
54
|
+
the bare noun: with a bare `лендинг` trigger, `напиши текст для лендинга` picked up a
|
|
55
|
+
visual route it never asked for. With the phrase it stays copywriting alone, measured
|
|
56
|
+
before and after.
|
|
57
|
+
|
|
3
58
|
## 0.41.4 — 2026-08-16
|
|
4
59
|
|
|
5
60
|
**This gate can now see an invariant it breaks one repository away.** The family umbrella
|
|
@@ -78,6 +133,11 @@ Both are recoveries from the same mistake, and only one of them is safe.
|
|
|
78
133
|
|
|
79
134
|
## 0.41.2 — 2026-08-16
|
|
80
135
|
|
|
136
|
+
> **Never released on its own.** There is no `v0.41.2` tag and no `0.41.2` on npm,
|
|
137
|
+
> so `npm install super-ux@0.41.2` and `git checkout v0.41.2` both fail. This section
|
|
138
|
+
> describes work that shipped inside a later version. The note is here because
|
|
139
|
+
> the section reads as a release (2026-08-17, umbrella `B-71`).
|
|
140
|
+
|
|
81
141
|
**A source file is not prose, and the prose rules were reading all of it.** On
|
|
82
142
|
`sshlg.me`, whose `Sources:` block points `marketing` at `src/data/*.ts`, that
|
|
83
143
|
produced 20 rhetorical-dash errors inside `//` comments and 7 keyword-stuffing
|
|
@@ -132,6 +192,11 @@ buried under twenty false ones.
|
|
|
132
192
|
|
|
133
193
|
## 0.41.1 — 2026-08-16
|
|
134
194
|
|
|
195
|
+
> **Never released on its own.** There is no `v0.41.1` tag and no `0.41.1` on npm,
|
|
196
|
+
> so `npm install super-ux@0.41.1` and `git checkout v0.41.1` both fail. This section
|
|
197
|
+
> describes work that shipped inside a later version. The note is here because
|
|
198
|
+
> the section reads as a release (2026-08-17, umbrella `B-71`).
|
|
199
|
+
|
|
135
200
|
**`B024` fined the writer for meeting a threshold this pack sets.** The
|
|
136
201
|
sentence-case check reads any capitalised word inside a sentence as Title Case,
|
|
137
202
|
and a contraction of the first person survived every exemption it had: `I'm` is
|
|
@@ -1235,6 +1300,11 @@ copy.
|
|
|
1235
1300
|
|
|
1236
1301
|
## 0.25.0 — 2026-07-29
|
|
1237
1302
|
|
|
1303
|
+
> **Never released on its own.** There is no `v0.25.0` tag and no `0.25.0` on npm,
|
|
1304
|
+
> so `npm install super-ux@0.25.0` and `git checkout v0.25.0` both fail. This section
|
|
1305
|
+
> describes work that shipped inside a later version. The note is here because
|
|
1306
|
+
> the section reads as a release (2026-08-17, umbrella `B-71`).
|
|
1307
|
+
|
|
1238
1308
|
The catalog knew how to sell inside an app and almost nothing about selling
|
|
1239
1309
|
on the web. Two funnels were missing: web-to-web (landing → pricing →
|
|
1240
1310
|
checkout → recurring billing → cancel) had only generic form advice, and
|
package/package.json
CHANGED
|
@@ -1,6 +1,9 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "super-ux",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.42.0",
|
|
4
|
+
"scripts": {
|
|
5
|
+
"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"
|
|
6
|
+
},
|
|
4
7
|
"description": "Scenario-driven UI development for AI agents (Claude Code, Cursor, 70+ agents): a versioned design chain in docs/ux/, a scenario-first hard rule, a deterministic drift linter, and evidence-backed UX audits. This package is the installer CLI.",
|
|
5
8
|
"bin": {
|
|
6
9
|
"super-ux": "bin/super-ux.js"
|