app-growth-design 1.0.1 → 1.0.3

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.
Files changed (2) hide show
  1. package/README.md +19 -27
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -15,6 +15,19 @@ That's it. Pick user-wide or project-only, restart Claude Code, and the skill lo
15
15
 
16
16
  ---
17
17
 
18
+ ## tl;dv
19
+
20
+ *Too long; didn't view — which is rather the point.*
21
+
22
+ - **What.** 30 app teardowns → six playbooks your agent reads instead of guessing: onboarding, paywalls, retention, psychology, growth, craft.
23
+ - **Why it's not slop.** Every non-obvious claim carries a `[NN]` marker back to the video. 243 named products with their real numbers. Where the source contradicts itself, the playbooks say so instead of picking a side.
24
+ - **The trick.** A design channel keeps its meaning *on screen* — "look at what they did here" and the captions carry `here` and nothing else. So the pipeline reads 1,161 screenshots too, and the notes come out **2.4× bigger than the speech**.
25
+ - **Install.** `npx app-growth-design` → restart Claude Code → describe your problem. It loads itself.
26
+ - **Credit.** All the insight is [Tim Gabe's](https://www.youtube.com/@TimGabe). This repo ships synthesized notes and the pipeline — no captions, no video, no screenshots.
27
+ - **Caveat.** One practitioner's opinionated view, not settled fact. Cases with real numbers are evidence; the rest are hypotheses to test.
28
+
29
+ ---
30
+
18
31
  ## What changes when it's installed
19
32
 
20
33
  Without it, ask Claude *"my paywall converts at 2%, what do I test first?"* and you get sensible, generic advice: try annual vs monthly, test your copy, add social proof.
@@ -73,34 +86,13 @@ The problem with turning a YouTube channel into agent knowledge is that the naiv
73
86
 
74
87
  So the pipeline is built around one idea: **the frames are not decoration, they are the missing half of the content.**
75
88
 
76
- ```
77
- 30 videos (5.7 h)
78
-
79
- 1 ──┤ yt-dlp: captions only, 6-wide → 2.6 MB VTT / 220,498 words
80
-
81
- 2 ──┤ dedupe rolling captions, regroup → 49,629 words, ~30s blocks
82
- │ into ~30s timestamped blocks (4.4× smaller, addressable)
83
-
84
- 3 ──┤ yt-dlp: 480p video, 3-wide → 510 MB, deleted after stage 4
85
-
86
- 4 ──┤ ONE AGENT PER VIDEO, in parallel: → 30 notes / 118,660 words
87
- │ read transcript → find the moments 1,161 frames extracted
88
- │ where meaning is on screen, not in 476 described in-line
89
- │ the audio → ffmpeg those timestamps
90
- │ → actually LOOK at the frames →
91
- │ write a structured note
92
- │ ↓
93
- │ second agent re-reads each note against the transcript and
94
- │ fixes what's missing — unresolved "this screen", dropped numbers,
95
- │ verbatim bloat, vague filler rules
96
-
97
- 5 ──┤ SIX AGENTS, one per theme, each → 6 playbooks / 55,241 words
98
- │ reading across all 30 notes: + SKILL.md router (2,378 words)
99
- │ merge, resolve contradictions,
100
- │ keep every number and product name
101
- ```
89
+ <!-- generated — edit docs/diagrams.mjs and run `node docs/diagrams.mjs`, don't hand-edit the SVG -->
90
+ <picture>
91
+ <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/bixxter/app-growth-design/main/docs/flow-dark.svg">
92
+ <img alt="Two streams enter: captions, deduped from 220,498 to 49,629 words, and 510 MB of 480p video. Both feed an enrich agent that runs once per video — read the transcript, find where meaning is on screen, cut those frames and look at them, write a structured note — followed by a verify agent. Out come 30 notes, 118,660 words and 1,161 frames, which six theme agents turn into six playbooks and a SKILL.md router." src="https://raw.githubusercontent.com/bixxter/app-growth-design/main/docs/flow-light.svg">
93
+ </picture>
102
94
 
103
- Note what happens to the word count at stage 4: the notes come out **more than twice the size of the speech**. That's the whole point — 1,161 screenshots put back what the captions lost.
95
+ Note what happens to the word count in the middle: the notes come out **more than twice the size of the speech**. That's the whole point — 1,161 screenshots put back what the captions lost.
104
96
 
105
97
  Three details that turned out to matter more than expected:
106
98
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "app-growth-design",
3
- "version": "1.0.1",
3
+ "version": "1.0.3",
4
4
  "description": "Claude Code skill: app onboarding, paywalls, pricing, retention, gamification and growth — distilled from 30 Tim Gabe teardowns into six source-marked playbooks.",
5
5
  "type": "module",
6
6
  "bin": {