YouC positioning

Canonical narrative for the repo (docs/youc/POSITIONING.md). Rendered here for the in-app docs shell.
# YouCapt positioning — category narrative

**Primary brand:** YouCapt (`youcapt.com`) · **Core behavior:** Watch → Capt · **Core transformation:** YouTube → YouCapt

**Legacy continuity:** YOU.C.Cards / YouC / `you.c.cards` remain on product surfaces during transition. Marketing acquisition is YouCapt-first; “Formerly YOU.C.Cards” where helpful.

**Canonical narrative for product, marketing, events, and demos.** Lead with **context capture from video**—not cards, collections, or storage metaphors.

---

## Anti-dilution guardrails

These surfaces must **reinforce the same story** (no drift back to vague “learning” or card-library UX):

- Product behavior, visual language, user psychology, economic story, community, onboarding, demos, captures, exports, Chrome extension.

**Smell test:** If a headline could describe a bookmark tool, a card app, or a meditation app without change, rewrite it. A first-time visitor should think: *“This helps me capture useful things from videos.”*

---

## Flagship lines

| Line | Use |
|------|-----|
| **Don't just watch. Capt.** | Hero / acquisition |
| **Turn videos into context.** | Category definition |
| **Watch → Capt** | Behavior shorthand |
| **YouTube → YouCapt** | Transformation shorthand |
| **Capture what matters.** | Emotional hook |
| **Watch less. Build more.** | Outcome framing |

---

## Company canon (three lines)

1. **YouTube = where you watch** — High-signal input; passive consumption is the problem, not the platform.
2. **YouCapt = what you keep** — Timestamped context, voice, and return links beside the frame.
3. **Build from video = outcome** — Reusable knowledge, not filing cards.

---

## NOT vs ARE

**You are NOT:** Watch Later, bookmarks, generic note-taking, knowledge cards, card stacks, card libraries, transcript export as the whole product story.

**You ARE:** **Video context capture** — executable continuity, timestamps, voice beside the frame, return loops, and context you can ship from.

---

## Legacy doc (YouC era)

The sections below retain workflow-memory / AI-builder ICP detail from the YouC positioning era. Update surface URLs to `youcapt.com` where public; product capture remains on `you.c.cards` until host migration completes.

---

# YouC positioning — category narrative (legacy reference)

**Canonical narrative for product, marketing, events, and demos.** Keep one vector: workflow memory and mastery for AI-native work—not generic “practice software” or wellness-adjacent framing.

---

## Anti-dilution guardrails

These surfaces must **reinforce the same story** (no drift back to vague “learning”):

- Product behavior, visual language, user psychology, economic story, community, onboarding, demos, graphs, installs, exports, Chrome extension.

**Smell test:** If a headline could describe a bookmark tool or a meditation app without change, rewrite it.

---

## SEO / category vocabulary (“practice systems”)

Off-site search and partner copy may use **practice systems** or **practice identity** language when it is **operationally anchored**: reps, return links, timestamped captures, installs, transcripts, and workflow memory on real work artifacts (code, instruments, facilitation language)—not generic wellness or “motivation content.”

Use this rule: if the sentence could sell a journaling app without naming **YouTube + exact-second return + voice beside the frame**, it fails the smell test. Identity hub pages under `/identity` on you.c.cards exist to map **who** is practicing while keeping that anchor explicit.

---

## Flagship line

**YouC preserves the path.**

AI-native work is chaotic and nonlinear. People lose prompts, breakthroughs, architecture decisions, workflow patterns, debugging context, and learning momentum. YouC preserves the **learning path itself**—deeper than “capture notes from YouTube.”

---

## Company canon (three lines)

1. **YouTube = input / dojo** — High-signal training surface; serious craft, not passive “content.”
2. **YouC = workflow memory + repetition** — The layer that makes learning stick and compound.
3. **Workflow mastery = outcome** — Economically legible capability, not a soft “practice platform.”

**Why “dojo” works:** This ICP already thinks in reps, iteration, loops, systems, practice, refinement, and feedback cycles.

---

## NOT vs ARE (dev-tool framing)

**You are NOT:** Watch Later, bookmarks, generic note-taking, transcript export as the whole product story, productivity journaling.

**You ARE:** **Workflow memory + repetition infrastructure**—executable continuity, timestamps, installs, captures, transcripts, and return loops.

---

## Primary ICP avatar (one page)

**Who:** An **AI-native developer**—ships most days with an AI-assisted IDE (e.g. Cursor), terminal, docs, and video; treats YouTube as a **dojo** for concrete workflows (auth, MCP, deploys, debugging, prompt patterns).

**Three workflow examples (IDE-led):**

1. **Cursor + MCP** — Follow a walkthrough to wire MCP servers and agent flows; return with the exact moment and voice install preserved.
2. **Supabase auth in Next.js** — Replay the walkthrough segment until the flow sticks; path survives past the single session.
3. **Ship + debug loop** — Capture the breakthrough timestamp and prompt pattern when the bug finally clears; stack reps instead of re-googling.

---

## Visual canon (screenshots and demos)

Every marketing image should look like **real AI work** so viewers think **“people like me”**:

- Cursor, React, Supabase, MCP, Vercel, debugging, prompt workflows, architecture sketches, transcripts, installs, **workflow graphs**.

**Not:** Generic inspiration, stock “learner,” or abstract flashcards.

---

## Canonical surfaces (where this story lives)

| Surface | Role |
|--------|------|
| [`/starthere`](https://c.cards/starthere) | Curated **Start Here** launchpad on apex hosts—primary “category” entry with prompt paths. |
| [`/search`](https://c.cards/search) | **AI workflow** prompt search—developer-first discovery. |
| [`/docs/youc`](https://c.cards/docs/youc) | In-product **docs hub**; this file is the **positioning** anchor. |
| `you.c.cards` / `/you` | **Capture** experience—timeline, Path, installs. |

---

## Platform stack (public positioning)

**Lead with three surfaces — not OS parity:**

| Surface | Role |
|--------|------|
| **Mac native app** | Primary desktop experience — fastest workflow loop, dock-level capture, premium native environment. |
| **Chrome extension** | Capture beside YouTube in any Chromium browser; required path on Windows/Linux. |
| **Web (`you.c.cards`)** | Full installs, Path, replay, and onboarding without a native installer. |

**Public copy prefers:** “Download for Mac”, “Install the Chrome extension”, “Use in Chrome”, “Works in your browser”.

**Avoid in marketing:** “Available on Windows” (native), “Windows download”, “cross-platform desktop app” as a headline promise.

**Still true (not marketed):** Windows keyboard shortcuts in browser and extension flows; `apps/youc-windows` build and QA at `/download/windows?native=1` for internal installer verification. Chrome on Windows is a first-class workflow surface.

---

## Event fit

**Natural homes:** AI engineer meetups, vibe coding workshops, AI workflow talks, dev tool showcases, hackathons, indie hacker communities.

**Track language:** AI engineering, AI workflows, developer tooling, vibe coding, AI productivity, human + AI collaboration—not miscellaneous productivity or wellness.

---

## Event mechanic: QR → practice environment

One scan can compress **discovery, onboarding, demonstration, and participation**—not “here’s our website” but **“try the workflow right now.”**

**Example scan destinations (3–5):**

1. Cursor-focused workflow (prompt + results or deep link into YouC capture).
2. Supabase auth walkthrough path.
3. MCP setup sequence.
4. Debugging / repro flow.
5. Prompt-engineering sequence tied to a real repo or stack.

**After the event:** YouC preserves timestamps, installs, captures, transcripts, and **repetition**—the QR is an on-ramp to a **practice environment that survives the conference**, not a one-off pageview.

**Booth one-liner:** *Practice environment that survives the conference.*

---

## Event kit (draft)

**Talk titles (examples):**

1. *Workflow memory for AI-native developers: YouTube as dojo, YouC as path.*
2. *Stop losing your debugging breakthroughs: captures, timestamps, and reps on top of video.*

**Workshop (60–90 min):** *From one YouTube walkthrough to a repeatable workflow* — pick a real stack (e.g. Supabase + Next), run a QR entry, capture three installs with voice, export or resume Path; debrief on what persisted vs bookmarks.

**Sponsor / table blurb:** *YouC is workflow memory for developers who learn on YouTube—timestamps, installs, and reps so your stack knowledge compounds after the tab closes.*

---

## Success criteria

- A stranger can say in **one sentence** who it’s for and what it does **without** “practice platform” as the core label.
- Visuals are instantly **AI-dev recognizable**.
- Event scan flows land in a **runnable workflow** and explain **what persists** after the booth.
- Nothing ships whose **headline truth** is only “notes from YouTube.”

---

## Related code and copy

- Identity hub (index + lanes): `lib/you/youc-identity-hub-page-configs.ts`, routes `app/(youc-marketing)/identity/`.
- SEO and metadata for Start Here: `lib/you/youc-seo-landing-config.ts` (`YOUC_SEO_PAGE_START_HERE`).
- Launchpad UI: `components/you/marketing/YoucStartHereLaunchpad.tsx`.
- Global short strings: `lib/brand/you-c-product-copy.ts`.
- PWA manifest: `public/manifests/domains/you.webmanifest`.