# Design a Prompt Sharing Product The source separately reports a product-design interview about prompt sharing, including user flow, database schema, sharing mechanics, and a viral-growth extension. The concrete policy choices below are practice scope for discussing that reported task; this is not a request to redesign the Prompt Playground execution backend. Design a product that lets a creator publish or privately share a reusable prompt, lets a recipient understand and try it safely, and lets the creator update or revoke access without making old links misleading. Cover the end-to-end experience before going deep on infrastructure. Address target users and jobs, creation and preview, visibility choices, link and organization sharing, versioning, attribution, reuse or remixing, discovery, abuse and privacy controls, and success metrics. Propose a database schema that supports the chosen flows. Then discuss one responsible mechanism for sharing-driven growth and how you would test whether it creates durable value rather than spam. ### Constraints & Assumptions - A prompt may contain placeholders, examples, or accidental secrets. - Viewing, copying, remixing, and executing are separate permissions. - A shared item points to a stable version or clearly communicates that it follows the latest version. - Revocation and visibility changes must have understandable effects. - Growth features must respect consent, rate limits, moderation, and workspace boundaries. ### Clarifying Questions to Ask - Who is the primary creator and who is the recipient? - Is the initial product private collaboration, public discovery, or both? - Can recipients execute prompts, and who pays for execution? - Should remixes preserve attribution and lineage? - Which content or user-safety risks matter most? ### What a Strong Answer Covers - A focused user problem, primary flow, and sensible initial scope. - Clear visibility and permission semantics, version behavior, and revocation. - A schema for prompts, immutable versions, principals, grants or links, lineage, and events. - Privacy scanning, moderation, reporting, abuse prevention, and cost controls. - A measurable sharing loop with guardrails, experiment design, and counter-metrics. ### Follow-up Questions 1. What should a recipient see before deciding to run a shared prompt? 2. How should a remix behave after its parent is edited or deleted? 3. How would you prevent public links from leaking private examples? 4. Which metric would distinguish useful sharing from invitation spam?