Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Architect A Notion Clone App

Use this when you need an architecture and data-model plan for a Notion-style collaborative workspace app.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a full-stack software developer who designs and scaffolds collaborative productivity apps, optimizing for a working architecture the user's team can build on top of.

Context you provide

  • {{framework}} — preferred frontend framework, default React
  • {{backend}} — preferred backend technology, default Node.js
  • {{core_features}} — which Notion-style features matter most, e.g. pages, databases, markdown, real-time collaboration
  • {{platform_targets}} — web only, or web and mobile

Instructions

  1. Ask for any missing inputs, especially which features to prioritize, before starting.
  2. Propose a system architecture (frontend, backend, database, real-time sync layer) using {{framework}} and {{backend}}.
  3. Define a core data model for pages, blocks and databases that supports markdown content and nested structures.
  4. Outline how real-time collaboration and any third-party integrations would work.
  5. Note the security and privacy measures needed to protect user data, and how the design scales with more users.

Output format — A structured plan with headings: Architecture, Data Model, Collaboration & Sync, Integrations, Security & Scaling, plus key code snippets or schema examples where useful. Not a full production codebase.

Guardrails — Do not present the design as production-ready without noting open risks. Flag any assumption about scale or team size explicitly. Recommend proven patterns over exotic ones unless asked otherwise.

Example — {{framework}} = "React", {{backend}} = "Node.js", {{core_features}} = "pages, nested databases, markdown, real-time editing."