Cringe Invite Rehearsal Booth

# Assumptions (KNOWN / ASSUMPTION / UNKNOWN) — Cringe Invite Rehearsal Booth

## KNOWN
- Assigned slot: p004
- Theme: 외로움
- Design profile: playful-experimental
- Evidence references:
- Reddit r/dating_advice modern dating fatigue thread: https://www.reddit.com/r/dating_advice/comments/1sxmy52/modern_dating_feels_broken_or_maybe_i_just_missed/
- Google News RSS dating app fatigue coverage: https://news.google.com/rss/search?q=dating%20app%20fatigue%20loneliness%20survey%202026

## ASSUMPTION
- The target user has enough urgency to try a lightweight decision workspace.
- A single-screen Stitch demo can communicate the value faster than a full app.
- The required sections are enough to make the prototype feel specific rather than generic.

## UNKNOWN
- Exact willingness-to-pay.
- Which data import path users would trust first.
- Whether users prefer automation or a manual checklist for the first version.

# Falsification checklist — Cringe Invite Rehearsal Booth

1. Does the prototype show a specific trigger/data source that differs from recent PF batches?
2. Can the target user identify themselves from the first screen copy?
3. Are the external/community signal references visible in the spec and meta.json?
4. Does the UI concept avoid generic dashboard/rescue/planner renaming?
5. Is the assigned design profile (playful-experimental) reflected in the Stitch prompt direction?
6. Does the key action produce a clear next decision, not just information display?
7. Would a user plausibly share or pay for this if the triggering pain happened today?

# PRD — Cringe Invite Rehearsal Booth

## Candidate type
- Fun / Experimental

## Theme
- 외로움

## Design profile
- playful-experimental

## Problem
- A playful social confidence lab that helps dating-app-fatigued adults practice one low-stakes invite, survive rejection, and send something human.

## Target user
- Singles and lonely young adults who want to move from endless app swiping to one real-world invite but freeze because the message might sound cringe.

## Key UX
- Pick a person/context, rehearse three invite tones, preview possible rejection responses, earn an awkwardness shield, and copy the least-cringe final message.

## Required UI sections
- dating fatigue mood card
- invite context picker
- cringe meter
- tone rehearsal cards
- rejection shield simulator
- final send-ready message drawer

## External/community signal references
- Reddit r/dating_advice modern dating fatigue thread: https://www.reddit.com/r/dating_advice/comments/1sxmy52/modern_dating_feels_broken_or_maybe_i_just_missed/
- Google News RSS dating app fatigue coverage: https://news.google.com/rss/search?q=dating%20app%20fatigue%20loneliness%20survey%202026

## Stitch prompt
Design a bold desktop social rehearsal prototype called Cringe Invite Rehearsal Booth for dating-app-fatigued adults who want to send one low-stakes real-world invite but freeze because it might sound awkward. It should help users choose a context, rehearse three invite tones, preview possible rejection responses, build an awkwardness shield, and copy a final send-ready message. Include a dating fatigue mood card, invite context picker, cringe meter, tone rehearsal cards, rejection shield simulator, and final send-ready message drawer. Design direction: use a playful-experimental aesthetic with glossy dark surfaces, neon blush and electric blue accents, expressive meters, funny-but-kind microcopy, and a charming rehearsal flow so the product feels emotionally safe, weird, and portfolio-worthy.

## Constraints
- Phase A only: spec/scaffold, no custom demo implementation.
- Preserve the assigned design profile in Stitch output.
- Use external signals as problem evidence, not market-size proof.

## Non-goals
- No external LLM API calls.
- No production backend.
- No payment flow implementation in Phase A.

## Success metrics
- A user can understand the core pain and next action within 10 seconds.
- The main UI exposes all required sections without placeholder text.
- Stitch output can be dropped into `/home/sy/Downloads/stitch_drop/2026-04-28/p004/`.

# QA checklist — Cringe Invite Rehearsal Booth

## Phase A scaffold checks
- meta.json includes `theme`, `designProfile`, `externalSignals`, and `stitchPrompt`.
- spec/prd.md contains the one-liner, target user, key UX, UI sections, signal references, and full Stitch prompt.
- Slot folder exists under `prototypes/2026-04-28-p004-cringe-invite-rehearsal-booth`.

## Stitch intake checks for 06:30 job
- Expected drop folder: `/home/sy/Downloads/stitch_drop/2026-04-28/p004/`
- Required files from user: `code.html` and `screen.png`.
- Ingest should preserve the original Stitch environment as the main demo experience.

## Acceptance verification
- Today has all slots p001 through p004.
- `node scripts/build-index.mjs` passes after scaffolding.
- No placeholder-only spec files remain for this idea.