b2c-app-builder 0.221.39

package/catalog/generated/firstparty/surfaces/starters/ai-chat-companion/starter/package.json

@@ -0,0 +1,29 @@
+{
+  "name": "ai-chat-companion-starter",
+  "version": "0.1.0",
+  "private": true,
+  "scripts": {
+    "dev": "next dev",
+    "build": "next build",
+    "start": "next start",
+    "typecheck": "tsc --noEmit",
+    "test:rls": "supabase test db"
+  },
+  "dependencies": {
+    "@anthropic-ai/sdk": "0.104.1",
+    "@supabase/ssr": "0.12.0",
+    "@supabase/supabase-js": "2.108.1",
+    "next": "16.2.9",
+    "posthog-js": "1.384.1",
+    "posthog-node": "5.36.10",
+    "react": "19.2.7",
+    "react-dom": "19.2.7",
+    "stripe": "22.2.0"
+  },
+  "devDependencies": {
+    "@types/node": "22.19.20",
+    "@types/react": "19.2.17",
+    "@types/react-dom": "19.2.3",
+    "typescript": "5.9.3"
+  }
+}

package/catalog/generated/firstparty/surfaces/starters/ai-chat-companion/starter/proxy.ts

@@ -0,0 +1,12 @@
+import { type NextRequest } from "next/server";
+import { updateSession } from "@/lib/supabase/proxy";
+
+// Next.js 16 network boundary (formerly middleware.ts). Refreshes the
+// Supabase session on every matched request.
+export async function proxy(request: NextRequest) {
+  return await updateSession(request);
+}
+
+export const config = {
+  matcher: ["/((?!_next/static|_next/image|favicon.ico|.*\\.(?:svg|png|jpg|jpeg|gif|webp)$).*)"],
+};

package/catalog/generated/firstparty/surfaces/starters/ai-chat-companion/starter/supabase/migrations/0001_init.sql

@@ -0,0 +1,78 @@
+-- AI chat companion starter schema (prompt 01 baseline).
+-- Conversations and messages are strictly private: owner-only RLS on every
+-- table, tested in supabase/tests/0001_rls.test.sql per backend-data-contract.md.
+
+create table public.profiles (
+  id uuid primary key references auth.users (id) on delete cascade,
+  display_name text,
+  persona_preferences jsonb not null default '{}'::jsonb,
+  created_at timestamptz not null default now()
+);
+
+create table public.conversations (
+  id uuid primary key default gen_random_uuid(),
+  owner_id uuid not null references public.profiles (id) on delete cascade,
+  title text,
+  created_at timestamptz not null default now(),
+  updated_at timestamptz not null default now()
+);
+
+create table public.messages (
+  id uuid primary key default gen_random_uuid(),
+  conversation_id uuid not null references public.conversations (id) on delete cascade,
+  owner_id uuid not null references public.profiles (id) on delete cascade,
+  role text not null check (role in ('user', 'assistant')),
+  content text not null,
+  created_at timestamptz not null default now()
+);
+
+-- Long-term memory snippets (prompt 05). One row per remembered fact, scoped
+-- to the owner; the model only ever sees memories for the requesting user.
+create table public.memories (
+  id uuid primary key default gen_random_uuid(),
+  owner_id uuid not null references public.profiles (id) on delete cascade,
+  content text not null,
+  source_conversation_id uuid references public.conversations (id) on delete set null,
+  created_at timestamptz not null default now()
+);
+
+-- Usage metering (prompt 06). Append-only event log the quota check sums over.
+create table public.usage_events (
+  id uuid primary key default gen_random_uuid(),
+  owner_id uuid not null references public.profiles (id) on delete cascade,
+  kind text not null check (kind in ('message', 'tokens')),
+  amount integer not null check (amount > 0),
+  created_at timestamptz not null default now()
+);
+
+create index conversations_owner_idx on public.conversations (owner_id, updated_at desc);
+create index messages_conversation_idx on public.messages (conversation_id, created_at);
+create index memories_owner_idx on public.memories (owner_id, created_at desc);
+create index usage_events_owner_idx on public.usage_events (owner_id, created_at desc);
+
+alter table public.profiles enable row level security;
+alter table public.conversations enable row level security;
+alter table public.messages enable row level security;
+alter table public.memories enable row level security;
+alter table public.usage_events enable row level security;
+
+-- Owner-only access everywhere; there is no public surface in a chat product.
+create policy "read own profile" on public.profiles for select using ((select auth.uid()) = id);
+create policy "insert own profile" on public.profiles for insert with check ((select auth.uid()) = id);
+create policy "update own profile" on public.profiles for update using ((select auth.uid()) = id);
+
+create policy "read own conversations" on public.conversations for select using ((select auth.uid()) = owner_id);
+create policy "insert own conversations" on public.conversations for insert with check ((select auth.uid()) = owner_id);
+create policy "update own conversations" on public.conversations for update using ((select auth.uid()) = owner_id);
+create policy "delete own conversations" on public.conversations for delete using ((select auth.uid()) = owner_id);
+
+create policy "read own messages" on public.messages for select using ((select auth.uid()) = owner_id);
+create policy "insert own messages" on public.messages for insert with check ((select auth.uid()) = owner_id);
+create policy "delete own messages" on public.messages for delete using ((select auth.uid()) = owner_id);
+
+create policy "read own memories" on public.memories for select using ((select auth.uid()) = owner_id);
+create policy "insert own memories" on public.memories for insert with check ((select auth.uid()) = owner_id);
+create policy "delete own memories" on public.memories for delete using ((select auth.uid()) = owner_id);
+
+create policy "read own usage" on public.usage_events for select using ((select auth.uid()) = owner_id);
+create policy "insert own usage" on public.usage_events for insert with check ((select auth.uid()) = owner_id);

package/catalog/generated/firstparty/surfaces/starters/ai-chat-companion/starter/supabase/tests/0001_rls.test.sql

@@ -0,0 +1,75 @@
+-- pgTAP RLS tests — run with `supabase test db` (requires the local stack).
+-- backend-data-contract.md: untested authorization rules are a launch blocker.
+-- Chat data is strictly private: owner access works, cross-user and anonymous
+-- access are denied.
+begin;
+create extension if not exists pgtap with schema extensions;
+select plan(6);
+
+insert into auth.users (id, email)
+values
+  ('00000000-0000-0000-0000-000000000001', 'user1@test.local'),
+  ('00000000-0000-0000-0000-000000000002', 'user2@test.local');
+
+insert into public.profiles (id, display_name)
+values
+  ('00000000-0000-0000-0000-000000000001', 'User One'),
+  ('00000000-0000-0000-0000-000000000002', 'User Two');
+
+insert into public.conversations (id, owner_id, title)
+values ('10000000-0000-0000-0000-000000000001', '00000000-0000-0000-0000-000000000001', 'private thoughts');
+
+insert into public.messages (conversation_id, owner_id, role, content)
+values ('10000000-0000-0000-0000-000000000001', '00000000-0000-0000-0000-000000000001', 'user', 'hello');
+
+-- Authenticated as user 1: owner access works.
+set local role authenticated;
+set local request.jwt.claims to '{"sub": "00000000-0000-0000-0000-000000000001", "role": "authenticated"}';
+
+select results_eq(
+  $$select count(*) from public.conversations$$,
+  array[1::bigint],
+  'owner can read their own conversation'
+);
+
+select lives_ok(
+  $$insert into public.messages (conversation_id, owner_id, role, content)
+    values ('10000000-0000-0000-0000-000000000001', '00000000-0000-0000-0000-000000000001', 'assistant', 'hi')$$,
+  'owner can append messages to their conversation'
+);
+
+-- Authenticated as user 2: another user''s chat is invisible and immutable.
+set local request.jwt.claims to '{"sub": "00000000-0000-0000-0000-000000000002", "role": "authenticated"}';
+
+select results_eq(
+  $$select count(*) from public.conversations$$,
+  array[0::bigint],
+  'other users cannot read someone else''s conversations'
+);
+
+select results_eq(
+  $$select count(*) from public.messages$$,
+  array[0::bigint],
+  'other users cannot read someone else''s messages'
+);
+
+select throws_ok(
+  $$insert into public.messages (conversation_id, owner_id, role, content)
+    values ('10000000-0000-0000-0000-000000000001', '00000000-0000-0000-0000-000000000001', 'user', 'forged')$$,
+  '42501',
+  'new row violates row-level security policy for table "messages"',
+  'users cannot write messages as someone else'
+);
+
+-- Anonymous: nothing is visible.
+set local role anon;
+set local request.jwt.claims to '{}';
+
+select results_eq(
+  $$select count(*) from public.conversations$$,
+  array[0::bigint],
+  'anonymous visitors cannot read any conversations'
+);
+
+select * from finish();
+rollback;

package/catalog/generated/firstparty/surfaces/starters/ai-chat-companion/starter/tsconfig.json

@@ -0,0 +1,41 @@
+{
+  "compilerOptions": {
+    "target": "ES2022",
+    "lib": [
+      "dom",
+      "dom.iterable",
+      "esnext"
+    ],
+    "allowJs": true,
+    "skipLibCheck": true,
+    "strict": true,
+    "noEmit": true,
+    "esModuleInterop": true,
+    "module": "esnext",
+    "moduleResolution": "bundler",
+    "resolveJsonModule": true,
+    "isolatedModules": true,
+    "jsx": "react-jsx",
+    "incremental": true,
+    "plugins": [
+      {
+        "name": "next"
+      }
+    ],
+    "paths": {
+      "@/*": [
+        "./*"
+      ]
+    }
+  },
+  "include": [
+    "next-env.d.ts",
+    "**/*.ts",
+    "**/*.tsx",
+    ".next/types/**/*.ts",
+    ".next/dev/types/**/*.ts"
+  ],
+  "exclude": [
+    "node_modules"
+  ]
+}

package/catalog/generated/firstparty/surfaces/starters/habit-tracker/README.md

@@ -0,0 +1,43 @@
+# Habit Tracker — Boilerplate Prompt Pack
+
+The **app-archetype prompt pack** for B2C habit and daily-utility apps: habit trackers, streak apps, daily routine and wellness utilities. Routing, the upfront archetype question, and how each prompt threads into the launch lanes live in [`../../../knowledge/product/habit-tracker.md`](../../../knowledge/product/habit-tracker.md). Read that first.
+
+These are **starting prompts**, not final code. Each file has a copy-paste block plus skill-integration notes. The streak mechanic at this archetype's center is a HIGH-risk Experience Card — the ethics contract in the lane reference is not optional.
+
+## How to use
+
+1. Confirm the product shape from the existing mandate, using a user question only for missing product constraints (habit model, primary surface, optional systems, niche) — see the reference. Record product decisions in `product.yaml` and render `PRODUCT.md`.
+2. **Copy the runnable starter** ([`starter/`](./starter/README.md)) into the business repo and install it — it is the pre-wired floor (auth, tested owner-only RLS migrations, PostHog event catalog, Stripe/RevenueCat stubs, names-only `.env.example`, CI). Do not regenerate this wiring from scratch; `check:archetype-starter` enforces its contract.
+3. Run prompt **00** strategy work on the web interface / Claude.ai.
+4. Run prompts **01 → 04** in order as Claude Code build prompts against the starter (the starter README maps each prompt to the scaffold area it customizes). Build one system, test it, then move on.
+5. Add optional prompts **05 → 07** based on the founder's selection.
+6. Apply a **variant** (wellness coach or simple counter utility) if relevant.
+
+## Default stack
+
+These are this starter's implementation choices, not platform-wide requirements.
+The public architecture separates capability contracts from provider choices.
+This starter has not yet been converted into an externally loadable recipe;
+public composition preview does not reconfigure its integrations.
+
+Next.js App Router + Supabase (Postgres, Auth) + Vercel, shipped as web/PWA — that is the pack's default and the fastest path to a working product. Be honest with the founder, though: **native iOS/Android is the natural home for habit apps**. Reliable reminders, lock-screen widgets, and push notifications are the retention surface, and they all push toward native; if the founder picks native, the Apple/Play store lanes in `SKILL.md` apply in full. Billing follows the surface: **RevenueCat + StoreKit/Play Billing for native subscriptions, Stripe for web**. Streak computation depends on the user's local midnight — capture timezone at signup and compute server-side.
+
+## Build order
+
+| #   | File                                                                                 | Build it                                                     | Optional? |
+| --- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------ | --------- |
+| 00  | [`prompts/00-positioning-strategy.md`](./prompts/00-positioning-strategy.md)         | Niche, wedge, the one habit loop (Claude.ai)                 | strategy  |
+| 01  | [`prompts/01-database-schema.md`](./prompts/01-database-schema.md)                   | Schema (profiles, habits, check-ins, reminders) + RLS + seed | required  |
+| 02  | [`prompts/02-auth-system.md`](./prompts/02-auth-system.md)                           | Auth + profile + timezone capture                            | required  |
+| 03  | [`prompts/03-habit-core-loop.md`](./prompts/03-habit-core-loop.md)                   | Today view + one-tap check-in + streak display               | required  |
+| 04  | [`prompts/04-reminders-and-streaks.md`](./prompts/04-reminders-and-streaks.md)       | Reminder scheduling + server-side streaks + recovery/freeze  | required  |
+| 05  | [`prompts/05-stats-and-insights.md`](./prompts/05-stats-and-insights.md)             | History heatmap, completion rates, weekly review             | optional  |
+| 06  | [`prompts/06-paywall-and-monetization.md`](./prompts/06-paywall-and-monetization.md) | Freemium cap vs hard paywall, RevenueCat/Stripe              | optional  |
+| 07  | [`prompts/07-social-accountability.md`](./prompts/07-social-accountability.md)       | Buddies, shared habits, accountability circles               | optional  |
+
+## Variants
+
+| File                                                                                         | Turns the base into                                                      |
+| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
+| [`prompts/variants/wellness-coach.md`](./prompts/variants/wellness-coach.md)                 | Guided wellness/coaching program app (programs, day plans, content)      |
+| [`prompts/variants/simple-counter-utility.md`](./prompts/variants/simple-counter-utility.md) | Single-purpose counter/tracker utility with a focused product scope |

package/catalog/generated/firstparty/surfaces/starters/habit-tracker/prompts/00-positioning-strategy.md

@@ -0,0 +1,47 @@
+# 00 — Positioning Strategy (Claude.ai, not Claude Code)
+
+**Run this first, on the web interface / Claude.ai.** Habit tracking is a saturated category with free incumbents and an OS-level competitor (phone reminders). A generic "track anything" app loses; the win is one niche, one habit loop done better than anyone, and a reason to return that a to-do list cannot give. Replace the bracketed parts with the founder's answers.
+
+```
+I want to build a habit/routine app for [describe the niche: who the user is and
+the specific habit or routine they are trying to build or keep].
+
+Help me define the positioning:
+1. Why do people in this niche fail with generic habit trackers, phone reminders,
+   and paper? What is specifically broken for them?
+2. What is THE one habit loop my app does better than anything else — the single
+   check-in moment, what it looks like, and why it feels worth doing daily?
+3. What does my app know or do for this niche that a generic tracker cannot
+   (domain content, terminology, schedule shapes, community)?
+4. What is the free experience, and what specifically would a paid tier unlock
+   (more habits, stats/insights, accountability features)?
+5. What is the moment that would make a user show the app to a friend — a streak
+   milestone, a weekly review, a shared habit?
+6. Where do the first 100 users in this niche already gather, and what is the
+   honest pitch that gets them to try it this week?
+
+Also define:
+- The product name direction (3 options with rationale)
+- The tagline (under 8 words)
+- The single sharpest use case to feature in onboarding and the App Store
+- The moat contract for `PRODUCT.md`'s category and wedge section: the top 2-3
+  incumbents by revenue (what each does well, the moment we beat them, what stops
+  each shipping a copy in a week), the moat class being built (data / workflow /
+  community / taste / model / distribution) with its concrete build plan, and the
+  one-week-copy test answer
+
+Strings: every user-facing label, headline, button, empty state, and error
+comes from product/copy/COPY_DECK.md (author missing rows first — voice from product/copy/COPY_BRIEF.md,
+craft from knowledge/words/conversion-copy.md), typed via the externalized resource
+named in engineering/TECH_SPEC.md. Example copy in this prompt is voice guidance, not
+shipping strings.
+```
+
+## Skill-integration notes
+
+- Answers 1–3 define the wedge → `strategy/RESEARCH.md` and the 11-star magical moment (the check-in, prompt 03). A focused niche is the whole strategy; "habit tracker for everyone" is the losing default.
+- Answer 4 constrains monetization (prompt 06) — reconcile with `revenue-monetization.md`; pricing and plan mix are founder-gated.
+- Answers 5–6 feed `VIRAL_GROWTH.md` and `growth/LAUNCH_NARRATIVE.md`; the first-100-users plan is the launch narrative's opening beat.
+- Name directions feed naming/collision checks; the tagline and featured use case feed `APP_STORE_LISTING.md` and landing copy (run `geo-seo.md` before editing landing copy).
+- Keep the positioning honest about motivation: the app helps users keep a goal they already own. Copy that promises transformation it cannot deliver fails the truthfulness test in `ethics-guardrail.md`.
+- **Transcribe the wedge into the product contract:** the answers above land in `PRODUCT.md`'s evidence and category section and are held to `product-moat.md`'s tests (one-week-copy, moat class, incumbent beat moment). A done product lane needs a real incumbent row and a named moat class in `PRODUCT.md` — a wedge that lives only in this chat is invisible to every gate.

package/catalog/generated/firstparty/surfaces/starters/habit-tracker/prompts/01-database-schema.md

@@ -0,0 +1,54 @@
+# 01 — Database Schema (build first)
+
+The foundation: profiles, habits with a cadence, check-ins, and reminders. Two things must be right from day one: owner-only RLS (habit data is private health-adjacent data) and a timezone-aware day model — streak computation across timezones and DST is the classic bug in this category.
+
+```
+Design a PostgreSQL database schema for a habit-tracking application (Supabase).
+
+The product supports:
+- Users with accounts (auth handled by Supabase Auth); a profiles table with
+  display name and an IANA timezone (e.g. "America/New_York") captured at signup
+- Habits: each user has many habits with a name, optional description/emoji,
+  a cadence (daily, specific weekdays, or N times per week), an active/archived
+  flag, sort order, and timestamps
+- Check-ins: a habit_checkins table recording that a habit was completed on a
+  local calendar date. Store the user's LOCAL DATE (date column) computed from
+  their profile timezone, plus the UTC timestamp. Enforce at most one check-in
+  per habit per local date with a unique constraint
+- Reminders: per-habit reminder rows with a local time-of-day, enabled flag,
+  and delivery channel (push/email)
+- Streak support: streaks are computed from check-ins (current streak, longest
+  streak), not stored as a mutable counter; add a streak_freezes table
+  (user_id, habit_id, used_on_date) for recovery mechanics
+
+Create:
+1. Full schema with all tables, columns, data types, and constraints (including
+   the one-check-in-per-habit-per-day unique constraint)
+2. Indexes for the hot paths: a user's active habits for the today view
+   (user_id + active + sort order) and streak computation over a habit's
+   check-ins (habit_id + local date descending)
+3. Row Level Security policies so a user can only read/write their own
+   profiles, habits, check-ins, reminders, and freezes — owner-only on every
+   table
+4. A SQL function or view that computes current and longest streak per habit
+   from check-ins, respecting the habit's cadence (a weekday-only habit is not
+   broken by a weekend)
+5. A seed script with 2 test users in different timezones, a few habits with
+   different cadences, and check-in history that exercises streak edge cases
+
+Output as SQL I can run directly in Supabase's SQL editor.
+
+Strings: every user-facing label, headline, button, empty state, and error
+comes from product/copy/COPY_DECK.md (author missing rows first — voice from product/copy/COPY_BRIEF.md,
+craft from knowledge/words/conversion-copy.md), typed via the externalized resource
+named in engineering/TECH_SPEC.md. Example copy in this prompt is voice guidance, not
+shipping strings.
+```
+
+## Skill-integration notes
+
+- Reconcile with `engineering/TECH_SPEC.md` (data model, API contracts, RLS) before building clients. **RLS is the security lane, not a checkbox**: habit data reveals routines, health, and location-adjacent patterns — every table needs a tested owner-only policy referenced from `trust/SECURITY.md` (pgTAP tests per `backend-data-contract.md`; the starter ships them).
+- **Timezone/DST correctness is the trap.** A check-in at 11:58pm local must count for that local day; a user flying across timezones or hitting a DST shift must not lose a streak to UTC math. Storing the local date explicitly (derived from the profile timezone, prompt 02) and computing streaks server-side from that column (prompt 04) is the defense. Add the edge cases to `engineering/TECH_SPEC.md` test plans.
+- Streaks are **derived, never stored as a mutable counter** — a stored counter drifts and then the product lies, which fails the truthfulness test in `ethics-guardrail.md`.
+- Cadence-aware streaks matter: punishing a "Mon/Wed/Fri" habit for Tuesday is a correctness bug that users read as cruelty.
+- Seed data is development-only.

package/catalog/generated/firstparty/surfaces/starters/habit-tracker/prompts/02-auth-system.md

@@ -0,0 +1,42 @@
+# 02 — Authentication System
+
+Identity first. Same pattern as any Supabase app, with one archetype-specific requirement: **capture the user's timezone at signup**, because every streak in the product depends on the user's local midnight.
+
+```
+Build the authentication system using Next.js App Router and Supabase Auth.
+
+Requirements:
+- Email magic-link sign-in (passwordless) as the primary path
+- OAuth login with Google and Apple
+- Protected routes that redirect to login if not authenticated
+- A profile row created on first sign-in: display name and IANA timezone.
+  Detect the timezone automatically from the browser
+  (Intl.DateTimeFormat().resolvedOptions().timeZone), show it for confirmation,
+  and let the user change it — do not silently guess wrong
+- Session management with JWT refresh
+- A settings page where the user can later change display name and timezone;
+  on timezone change, note that today's check-in day boundary moves with it
+
+Create:
+1. Login page (/login) with magic-link form and OAuth buttons
+2. Auth middleware that protects all /app/* routes
+3. A useUser() hook that returns the current user and profile anywhere
+4. A lightweight first-run step: display name + timezone confirmation + create
+   your first habit (name only; the full habit editor comes later)
+
+Design: clean, calm, fast. Form validation with clear error messages.
+
+Strings: every user-facing label, headline, button, empty state, and error
+comes from product/copy/COPY_DECK.md (author missing rows first — voice from product/copy/COPY_BRIEF.md,
+craft from knowledge/words/conversion-copy.md), typed via the externalized resource
+named in engineering/TECH_SPEC.md. Example copy in this prompt is voice guidance, not
+shipping strings.
+```
+
+## Skill-integration notes
+
+- OAuth client secrets and the Supabase service role key are secrets → route via `SECRETS.md` (`secrets-management.md`). Magic-link and lifecycle emails go through `resend-email-ops.md`.
+- **Timezone capture is load-bearing**, not profile decoration: prompts 01 and 04 compute the local check-in date and streaks from it. A wrong timezone silently breaks streaks — confirm it visibly rather than guessing. Handle timezone *changes* deliberately (recompute the day boundary going forward; do not retroactively rewrite past local dates).
+- The first-run "create your first habit" step is an onboarding surface (`onboarding-conversion.md`) and a Commitment moment (`consumer-product-design-agency.md`): the user states a goal in their own words, which seeds the today view (prompt 03) and reminder copy (prompt 04).
+- Reconcile the look with Design Room tokens (`design-room.md`); don't invent a one-off style.
+- Add `sign_up_completed`, `oauth_used`, `timezone_confirmed`, `first_run_completed` to `analytics/ANALYTICS.md`.

package/catalog/generated/firstparty/surfaces/starters/habit-tracker/prompts/03-habit-core-loop.md

@@ -0,0 +1,50 @@
+# 03 — Habit Core Loop (the magical moment)
+
+The today view and the one-tap check-in are the product. The check-in must feel instant, certain, and quietly satisfying — that two-second moment is what the user comes back for. Build it against the schema from prompt 01; reminders and server-side streak hardening come in prompt 04.
+
+```
+Build the core habit loop: the today view and the check-in interaction.
+
+Today view (the home screen):
+- The list of habits due TODAY based on each habit's cadence and the user's
+  profile timezone (a Mon/Wed/Fri habit does not appear on Tuesday)
+- Each habit row: emoji/name, current streak count, and a single large
+  check-in control
+- One-tap check-in with optimistic UI: the row flips to its completed state
+  instantly, the streak count increments, and a short satisfying completion
+  animation plays; persist to Supabase in the background with rollback + a
+  clear error state if the write fails
+- Tap again to undo today's check-in (mistakes happen; undo is free and easy)
+- Completed habits move to a "done today" section; when everything is done,
+  show an all-done state that closes the session warmly ("That's everything
+  for today") — no nudge to keep scrolling
+- An empty state for new users that points to creating a habit
+
+Habit management:
+- Create/edit habit: name, emoji, cadence (daily / weekdays / N times per week),
+  reminder time (wired in prompt 04)
+- Archive (not delete) a habit, preserving its history; hard delete available
+  in settings
+
+Streak display:
+- Current streak per habit, computed from check-ins via the prompt 01
+  function/view — never a client-side counter
+- A subtle milestone acknowledgment at 7/30/100 days tied to the habit's name
+
+Design: calm and focused. The check-in animation must respect
+prefers-reduced-motion with a non-animated completed state.
+
+Strings: every user-facing label, headline, button, empty state, and error
+comes from product/copy/COPY_DECK.md (author missing rows first — voice from product/copy/COPY_BRIEF.md,
+craft from knowledge/words/conversion-copy.md), typed via the externalized resource
+named in engineering/TECH_SPEC.md. Example copy in this prompt is voice guidance, not
+shipping strings.
+```
+
+## Skill-integration notes
+
+- **This is the 11-star magical moment.** Run `eleven-star-experience.md` over it: the tap → instant flip → streak tick is the engineered moment that decides whether the app feels alive. Name it in `11_STAR_EXPERIENCE.md` with its PostHog event and the reduced-motion fallback (`consumer-product-design-agency.md`, `emotional-design-system.md`).
+- **Two Experience Cards apply, and one is HIGH-risk.** The check-in maps to the **Commitment** card (the user acts on their own stated goal). The streak display maps to the **Streak / Loss Aversion** card, which is HIGH-risk per `ethics-guardrail.md` and requires, before ship: an `ethics_attestation`, a `user_control_escape_hatch` (the streak freeze/repair built in prompt 04), a `counter_metric` (e.g. streak-anxiety signals: undo-then-redo churn, late-night panic check-ins), and a truthfulness proof (streaks derived from real check-ins, never inflated). The attestation block lives in the emotional-design artifact; `check:emotional-design` enforces the fields.
+- The all-done state is the session close (peak-end rule) — a completion signal, not an engagement hook. Do not add "one more thing" mechanics there.
+- The optimistic write needs a rollback path and an honest failure state (`engineering/TECH_SPEC.md`); a check-in that silently fails and breaks a streak is the worst bug this product can have.
+- Add `habit_created`, `habit_checked_in`, `streak_extended`, `streak_recovered` to `analytics/ANALYTICS.md` before this surface locks (`analytics-attribution.md`); `streak_recovered` is emitted by prompt 04's recovery flow.

package/catalog/generated/firstparty/surfaces/starters/habit-tracker/prompts/04-reminders-and-streaks.md

@@ -0,0 +1,58 @@
+# 04 — Reminders And Streaks (the retention engine)
+
+Reminders bring the user back; streak computation decides whether the product is trustworthy; recovery mechanics decide whether it is ethical. All three are server-side concerns. Notification copy is part of this prompt because guilt-based copy is a dark-pattern veto, not a style choice.
+
+```
+Build the reminder system and harden streak computation.
+
+Streak computation (server-side):
+- Compute current and longest streak per habit on the server from
+  habit_checkins local dates (the prompt 01 function/view), respecting cadence:
+  daily habits break on a missed day; weekday habits ignore off-days; N-per-week
+  habits evaluate per week
+- All "what day is it" logic uses the user's profile IANA timezone. Write tests
+  for: a check-in at 11:58pm local; a user who changes timezone mid-streak;
+  DST transitions in both directions; the N-per-week boundary at week rollover
+- Never trust a client-supplied date for a check-in: the server derives the
+  local date from the authenticated user's timezone at write time
+
+Streak recovery (the escape hatch — required, free):
+- Each user gets a small number of free streak freezes per month (e.g. 2);
+  applying a freeze to a missed day preserves the streak
+- A repair flow: when a streak breaks, offer to apply an available freeze to
+  yesterday within a grace window (e.g. 48 hours). Recovery must never be
+  paywalled as the only option — the first protection is always free
+- Record freezes in streak_freezes; emit streak_recovered when used
+
+Reminders:
+- Per-habit reminder at a local time-of-day, scheduled in the user's timezone
+  (a 7:00am reminder fires at 7:00am local, including across DST)
+- A scheduled job (Supabase cron / scheduled function) that finds due reminders
+  and delivers them: web push for the PWA, email fallback
+- Skip the reminder if the habit is already checked in for today
+- A per-habit and global mute; reminder settings honor quiet hours
+
+Notification copy rules (hard rules, do not remove):
+- Motivate without guilt: name the habit and the user's goal ("7:00 — your
+  10-minute stretch"), or note the streak factually ("Day 12")
+- Never use shame, fear, or loss-threat copy ("Don't throw away your streak!",
+  "You're about to lose everything", "Everyone else checked in") and never
+  manufacture urgency that isn't real
+- At most one reminder per habit per day; missing a day never triggers a
+  guilt-trip follow-up, only the calm repair offer
+
+Strings: every user-facing label, headline, button, empty state, and error
+comes from product/copy/COPY_DECK.md (author missing rows first — voice from product/copy/COPY_BRIEF.md,
+craft from knowledge/words/conversion-copy.md), typed via the externalized resource
+named in engineering/TECH_SPEC.md. Example copy in this prompt is voice guidance, not
+shipping strings.
+```
+
+## Skill-integration notes
+
+- **This prompt is the Streak / Loss Aversion card's compliance surface.** Per `ethics-guardrail.md`, the streak card is HIGH-risk and the free recovery mechanism is the required `user_control_escape_hatch` / `streak_recovery_mechanism` attestation field. Paid-only forgiveness is the named dark line for this card. Combining a streak-break notification with a spend prompt is the highest-risk pattern — never pair them.
+- **Confirmshaming and commitment-guilt copy is a dark-pattern veto.** The copy rules in the prompt are enforced by the emotional-design audit (`emotional-design-system.md`, `failure-cards.md`); review final notification strings against `strategy/BRAND.md §Voice` and the bright-line test (goal alignment, truthfulness, informed exit).
+- Timezone/DST tests are the acceptance bar — put them in `engineering/TECH_SPEC.md` and CI. A streak engine that lies after a DST shift fails the truthfulness proof.
+- Push credentials (VAPID keys / APNs / FCM) and cron secrets route via `SECRETS.md` (`secrets-management.md`); reminder email goes through `resend-email-ops.md`. Treat the reminder job as an abuse/cost surface in `trust/SECURITY.md` (rate limits, idempotent delivery).
+- On native surfaces, local notifications replace web push and are a major reason the founder may choose native (see the lane reference); the server-side streak engine carries over unchanged.
+- Add `reminder_scheduled`, `reminder_sent`, `reminder_muted`, `streak_recovered`, `streak_freeze_applied` to `analytics/ANALYTICS.md`; pair `streak_extended` vs `streak_recovered` with the counter-metric from prompt 03's attestation.

package/catalog/generated/firstparty/surfaces/starters/habit-tracker/prompts/05-stats-and-insights.md

@@ -0,0 +1,44 @@
+# 05 — Stats And Insights (optional)
+
+The reflective layer: history a user can be proud of, and a weekly review that closes the loop on their goal. This is also where the paid tier usually earns its price (prompt 06) and where emotional measurement gets its data.
+
+```
+Build the stats and insights surface.
+
+Per-habit history:
+- A contribution-style heatmap of check-ins by local date (last 12 months),
+  rendered from the habit_checkins local-date column; freezes shown distinctly
+  from real check-ins (never disguise a freeze as a completion)
+- Current streak, longest streak, total check-ins, completion rate over the
+  last 30/90 days computed against the habit's cadence (missed weekend days
+  don't count against a weekday habit)
+
+Overview:
+- A simple all-habits view: completion rate this week, best day of week,
+  habits trending up or down
+
+Weekly review:
+- A once-a-week summary screen (and optional email): what was completed, the
+  honest completion rate, one observed pattern ("Tuesdays are your hardest
+  day"), and one suggestion grounded in the data
+- Tone: factual and encouraging. Show real numbers, including misses — no
+  inflated stats, no shame framing of a bad week
+
+Performance:
+- Compute aggregates with SQL (the prompt 01 indexes cover habit_id + date);
+  don't ship a year of raw rows to the client
+
+Strings: every user-facing label, headline, button, empty state, and error
+comes from product/copy/COPY_DECK.md (author missing rows first — voice from product/copy/COPY_BRIEF.md,
+craft from knowledge/words/conversion-copy.md), typed via the externalized resource
+named in engineering/TECH_SPEC.md. Example copy in this prompt is voice guidance, not
+shipping strings.
+```
+
+## Skill-integration notes
+
+- Insights feed retention and the emotional-measurement contracts (`emotional-experience-measurement.md`): the weekly review is a reflective-tier moment (`consumer-product-design-agency.md`) and a natural session close — give it a PostHog event and treat its arrival cadence as a retention lever, not a spam channel.
+- **Honesty is the design constraint.** Stats must reflect real check-ins; freezes are visually distinct; completion rates are cadence-aware. Inflated or massaged numbers fail the `ethics-guardrail.md` truthfulness test and poison the streak card's attestation.
+- The weekly review email routes through `resend-email-ops.md` with an unsubscribe path; respect the user's quiet hours and mute settings from prompt 04.
+- This surface is the standard upgrade hook for prompt 06 (full history and insights behind the paid tier, current week free) — decide the split with the founder there, not here.
+- Add `stats_viewed`, `heatmap_viewed`, `weekly_review_opened` to `analytics/ANALYTICS.md`.

package/catalog/generated/firstparty/surfaces/starters/habit-tracker/prompts/06-paywall-and-monetization.md

@@ -0,0 +1,50 @@
+# 06 — Paywall And Monetization (optional)
+
+Habit apps default to the cozy choice — generous freemium, a $1.99 price, a 3-day trial — and the benchmarks say the cozy choice quietly loses. Surface the trade-offs from `revenue-monetization.md` §3 (RevenueCat State of Subscription Apps 2026 figures) as **strong defaults to test, not dogma**, and get founder approval before building: pricing, plan mix, trial length, and paywall model are all founder-gated.
+
+```
+Add subscription monetization to the habit app.
+
+Paywall model — implement the founder's approved choice between:
+a) Freemium with a habit cap: free tier limited to N habits (confirm N with the
+   founder; 2-3 is typical), with full history/insights (prompt 05) and
+   unlimited habits in the paid tier
+b) Hard paywall after onboarding: free first-run that creates the first habit
+   and shows the today view, then the paywall with a trial before continued use
+
+Plans and trial (founder-approved values):
+- Annual as the highlighted plan with monthly visible alongside it
+- A trial long enough for a habit loop to form (confirm length with the
+  founder; default hypothesis 14+ days, A/B-tested)
+- Price from the founder's approved value — do not invent a price
+
+Billing by surface:
+1. Web/PWA: Stripe Checkout + Customer Portal; webhook handler for created/
+   updated/cancelled/payment-failed updating a cached entitlement
+2. Native iOS/Android: RevenueCat with StoreKit/Play Billing products and an
+   entitlement the app reads; digital subscriptions on native go through IAP,
+   not Stripe
+3. Feature gates (habit cap, history depth, insights) read the cached
+   entitlement on the server, not the billing provider per request
+
+Hard rules:
+- Streak recovery/freezes from prompt 04 stay free — never paywall the escape
+  hatch
+- The paywall never appears in response to a streak break or inside the
+  reminder flow
+- Cancellation is reachable from settings without confirmshaming copy
+
+Strings: every user-facing label, headline, button, empty state, and error
+comes from product/copy/COPY_DECK.md (author missing rows first — voice from product/copy/COPY_BRIEF.md,
+craft from knowledge/words/conversion-copy.md), typed via the externalized resource
+named in engineering/TECH_SPEC.md. Example copy in this prompt is voice guidance, not
+shipping strings.
+```
+
+## Skill-integration notes
+
+- **Reconcile with `revenue-monetization.md` §3 before building, and present the trade-offs to the founder rather than reaching for the reflex default**: hard paywalls convert roughly 5x better than freemium on Day-35 download-to-paid (~10.7% vs ~2.1%); apps whose most popular plan is yearly realize the highest revenue per install; trials of ≤4 days convert ~25.5% vs ~42.5% at 17–32 days; and low price anchors train users to value the app at nothing (high-priced apps show ~5.4x monthly realized LTV, with *higher* download-to-paid). Freemium is still a deliberate, defensible choice when free users drive word of mouth or accountability-circle network effects (prompt 07) — the anti-pattern is choosing it by reflex and never surfacing the trade-off.
+- **The ethics boundary holds under monetization pressure.** Free streak recovery (prompt 04) is the streak card's required escape hatch; paywalling it, or pairing the paywall with streak-loss grief, is the named highest-risk dark pattern in `ethics-guardrail.md`.
+- Billing path follows the surface: Stripe for web, RevenueCat + IAP for native (`revenue-monetization.md`). Do not ship the web Stripe paywall inside a native binary without resolving store policy first. Webhook signing secrets and API keys route via `SECRETS.md`; webhooks are an abuse surface in `trust/SECURITY.md` and updates must be idempotent.
+- Paywall timing relative to the first check-in and any review prompt is governed by `onboarding-conversion.md`; the emotional peak (first check-in) belongs before the paywall.
+- Add `paywall_shown`, `checkout_started`, `trial_started`, `subscription_activated`, `subscription_cancelled`, `payment_failed` to `analytics/ANALYTICS.md`; judge the model on cohort LTV and renewal, not install-day conversion alone.