Docs Save to Closet Jina Park · Persona

Docs

12 documents
Title Type Author Updated Preview
Why StyleVerse Exists Foundation MMaya 2 days ago Mission, core values, and what this is not Personas Foundation MMaya 3 days ago Jina Park (discovery) and Marcus Cole (creator) App Blueprint Foundation MMaya 1 day ago 9 screens, 4 user flows, navigation structure Seoul Minimal Foundation KKai 3 days ago Color palette, typography scale, component patterns Data Model Foundation AAlex 2 days ago Users, Posts, Outfits, Items, Tags and relationships Save to Closet Spec MMaya Today Heart icon saves, Pinterest grid, tagged item prices Feed Algorithm Spec AAlex Yesterday Full-screen swipe, recommendation engine, K-beauty bias Creator Onboarding Spec MMaya 4 days ago Sign up, post first outfit, tag items, earn first $ K-beauty Pivot Decision MMaya 5 days ago Narrow from general fashion to K-beauty crossover Pricing Model Decision MMaya 5 days ago Affiliate revenue via Lemon Squeezy, no subscription Competitive Landscape Research SSam Yesterday Lemon8, Xiaohongshu, Pinterest — positioning gaps User Interviews Research MMaya 4 days ago 12 interviews, key pain points, opportunity areas
LS
This spec looks solid. One question — do we need a save limit?
M
No limit. Closet is the retention hook — more saves = more return visits. Storage cost is negligible.
LS
Makes sense. What about when a price changes after saving — show the old price or new?
M
Both. Show current price + "was $89 when saved." I've added this as an edge case to the spec.
Spec updated
M
Save to Closet spec