What this prompt does
This prompt asks the AI to design a social reading and book club app across seven modules: a home feed, personal library, book detail page, book clubs, a discussion and social layer, reading challenges, and a framework-specific build section. It anchors every decision to your product through [app_name], [app_type], [target_readers], and [social_depth], so the AI tunes the experience for, say, literary-fiction club members rather than casual trackers.
The [social_depth] variable is the lever that matters most — it tells the model whether social features are a side note or the core, which reshapes the home feed and club screens entirely. Meanwhile [content_source] (defaulting to Open Library + Google Books APIs) and [framework] (React Native + Supabase + NativeWind) push the AI to design the spoiler system, per-chapter discussions, and offline library against real data and sync constraints instead of hand-waving them.
When to use it
- You're building a reading tracker or book club platform and need the full screen inventory first.
- You want the spoiler system and per-chapter discussion threads designed carefully, not bolted on.
- You're deciding how social the app should feel and want
[social_depth]to drive that. - You need book search, barcode scanning, and an offline library specced against
[content_source]. - You're designing gamification (challenges, badges, streaks) and want it coherent across screens.
Example output
Expect a structured design document: each module broken into named screens with component detail — shelves and shelf statistics in the library, group-progress visualizations and reading schedules in clubs, threaded quote-replies and a customizable spoiler threshold in the social layer. The closing [framework] section reads as an implementation checklist covering debounced API search, ISBN scanning, offline caching with queued sync, and accessibility — a spec to build against, not finished code.
Pro tips
- Treat
[social_depth]as the design's spine: "social-forward" makes clubs and feeds primary; "tracker-first" demotes them. - Keep
[content_source]accurate to your real APIs so the search and metadata screens match what you can actually fetch. - Tune
[target_readers]to your niche — a YA audience and a non-fiction-research audience want different shelves and challenges. - If you're not on Supabase or NativeWind, swap
[framework]so the offline-sync and styling guidance stays honest. - Re-prompt module by module after the overview ("expand the Discussion & Social module to wireframe detail") to go deeper where it counts.
- The spoiler system is the trickiest piece — design and test it before trusting the rest of the social layer.
