Claude Prompt Library

Notion Systems Claude Architects From Scratch

20 copy-paste prompts

20 Claude prompts for database schemas, formulas, workspace architecture, workflow design, and the structured thinking Notion power users need.

Architecture

5 prompts

Workspace Architect

1/20

<task>Design my Notion workspace</task> <role>[describe]</role> <needs>[areas to manage]</needs> <team>[solo / team size]</team> <output> 1. Page hierarchy (5-7 hubs max) 2. Database vs page per area 3. Relation structure 4. What NOT to put in Notion 5. Daily + weekly usage ritual </output>

Designs Notion workspaces with page hierarchy, database relations, and usage rituals.

💡

Pro tip: Most Notion workspaces die from too many databases. Start with 3-5 (Tasks, Projects, Notes) and expand only when real pain forces it. Over-architecting kills adoption.

Database Schema

2/20

<task>Design database schema for [tracking need]</task> <entities>[list]</entities> <output> 1. Properties with types 2. Relation + rollup to avoid redundancy 3. Views per use case 4. Filters and sorts 5. What NOT to track </output>

Designs Notion database schemas with properties, relations, rollups, and purposeful views.

💡

Pro tip: 5-8 properties per database is the sweet spot. More and you've probably needed a second database with a relation, not more columns.

Second Brain / PKM

3/20

<task>Build second brain in Notion</task> <capture_habits>[describe]</capture_habits> <output_needs>[writing / teaching / decisions]</output_needs> <output> 1. Notes database schema 2. PARA or similar organization 3. Quick capture workflow 4. Weekly review ritual 5. Retrieval surfacing </output>

Builds PKM systems in Notion with capture workflow, organization, and retrieval.

💡

Pro tip: Design retrieval first, capture second. "How will I find this in 6 months?" matters more than "how do I capture fast?" Notes without retrieval are cemeteries.

Project Management Template

4/20

<task>Build PM template in Notion</task> <project_type>[describe]</project_type> <team_size>[number]</team_size> <output> 1. Projects DB with properties 2. Tasks DB related 3. Role-specific views 4. Automation opportunities 5. Archive strategy </output>

Builds Notion PM templates with related databases, views, and automation.

💡

Pro tip: Notion's relation property is what makes it real PM. Flat task lists without relations are prettier sticky notes. Relations unlock the system.

CRM Lightweight

5/20

<task>Build lightweight CRM in Notion</task> <business>[describe]</business> <output> 1. Contacts DB + stages 2. Interactions DB related 3. Kanban by stage 4. Calendar view for next steps 5. When to graduate to real CRM </output>

Builds Notion CRMs with contact management, pipelines, and graduation plan.

💡

Pro tip: Notion CRMs work up to ~100 active contacts. Past that, real CRMs win. Don't force Notion to be Salesforce — use it for the 80% solopreneur case.

XML tags are just the start. Learn the full Claude workflow.

A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.

Start 7-Day Free Trial

Formulas & Automation

5 prompts

Formula Builder (2.0)

6/20

<task>Write Notion formula for [need]</task> <properties>[list with types]</properties> <output> 1. Formula in 2.0 syntax (if/let/switch) 2. Each part explained 3. Edge cases (empty, divide-by-zero) 4. Display formatting </output>

Writes Notion 2.0 formulas with if/let/switch syntax and edge case handling.

💡

Pro tip: Notion Formula 2.0 is a massive upgrade — let/if/switch cleanly. If you're still using nested prop() 1.0 formulas, upgrade. Cleaner, faster, easier to debug.

Rollup Master

7/20

<task>Configure rollup for [scenario]</task> <output> 1. Rollup setup 2. When rollup vs formula-that-does-it 3. Filtered rollup (e.g., active tasks only) 4. Performance on big DBs 5. Dashboard display </output>

Configures Notion rollups with filtering, performance, and dashboard display.

💡

Pro tip: Rollups are Notion's most underused feature. "How many open tasks per project?" updates automatically. Most "I need a spreadsheet" moments actually need rollups.

Status Automation

8/20

<task>Automate status changes</task> <current_process>[describe]</current_process> <rules>[describe]</rules> <output> 1. Formula-based automation where possible 2. Button automations 3. Notion Automations if paid 4. External tools (Make/Zapier) for complex </output>

Automates status with formulas, buttons, Notion Automations, or external tools.

💡

Pro tip: Automation only pays when process is truly repetitive. Changing status once a day = don't automate. 20 times a day = absolutely. Count first.

Dashboard with Rollups

9/20

<task>Build cross-database dashboard</task> <databases>[list]</databases> <kpis>[describe]</kpis> <output> 1. KPI formulas/rollups 2. Single-page layout 3. Filter controls 4. Visual hierarchy 5. Refresh cadence </output>

Builds Notion dashboards aggregating across databases with filter controls.

💡

Pro tip: Dashboards with 20+ linked databases load slowly. Show only 5-7 KPIs that matter. Everything else belongs one click away.

Template Gallery for Teams

10/20

<task>Build team template gallery</task> <team_templates>[list]</team_templates> <output> 1. Categorized hub page 2. Usage instructions per template 3. Governance 4. Featured rotation 5. Onboarding guide </output>

Builds team template galleries with governance, featured rotation, and onboarding.

💡

Pro tip: Template galleries die without shepherds. Assign one owner, review quarterly, retire unused. Without ownership: 50 templates nobody uses.

Workflows

5 prompts

Daily Dashboard

11/20

<task>Design daily dashboard</task> <priorities>[describe]</priorities> <output> 1. Page layout (Today, This Week, Waiting, Capture) 2. Linked views filtered to today 3. Morning intentions 4. Quick capture buttons 5. End-of-day review </output>

Designs daily command center dashboards with morning and evening rituals.

💡

Pro tip: Daily page is the front door. If finding what you need takes >10 seconds, system isn't working. Test: can I start my day in under 5 min?

Weekly Review Template

12/20

<task>Build weekly review template</task> <areas>[work / health / etc.]</areas> <output> 1. Review questions per area 2. Auto-populated stats from other DBs 3. Pattern notes 4. Next week top 3 priorities 5. Wins celebration </output>

Builds weekly review templates with auto-stats, patterns, and celebration.

💡

Pro tip: Weekly reviews are where productivity systems earn their keep. 20 minutes every Friday beats any app or template. Without review, capture creates clutter.

Meeting Notes Template

13/20

<task>Build meeting notes template</task> <meeting_types>[describe]</meeting_types> <output> 1. Meetings DB 2. Template with agenda/notes/decisions/action items 3. Action items linked to Tasks DB 4. Follow-up reminders 5. Scratchpad variant </output>

Builds meeting notes templates with linked action items and scratchpad variant.

💡

Pro tip: Meeting notes die when action items don't escape the notes page. Always link to your Tasks DB — otherwise decisions decompose into noise.

Content Calendar

14/20

<task>Build content calendar in Notion</task> <content_types>[describe]</content_types> <output> 1. Content DB with properties 2. Calendar/Kanban/Timeline views 3. Idea backlog → scheduled pipeline 4. Post-publish performance tracking 5. Linked to Tasks DB </output>

Builds Notion content calendars with pipelines, performance tracking, and task linkage.

💡

Pro tip: Content calendars work when connected to work needed. Without linked tasks, deadlines slip. With them, deadlines stay real.

Goals / OKRs Tracker

15/20

<task>Set up goals / OKRs in Notion</task> <horizon>[annual / quarterly]</horizon> <output> 1. Goals DB with parent-child structure 2. Key results as children 3. Weekly check-in updating progress % 4. Dashboard per season 5. Retrospective template </output>

Sets up goals/OKRs tracking with parent-child structure and weekly check-ins.

💡

Pro tip: OKRs fail when reviewed quarterly. Notion makes weekly check-ins trivial — 10 min per week is the entire secret to OKRs actually working.

Advanced

5 prompts

Notion AI Workflow Design

16/20

<task>Design Notion AI usage</task> <pain_points>[describe]</pain_points> <output> 1. Specific Notion AI commands per pain 2. What stays manual (AI slop worse than human) 3. AI blocks in templates 4. Notion AI vs Claude vs ChatGPT for different tasks 5. Guardrails </output>

Designs Notion AI integration with pain-specific usage and guardrails.

💡

Pro tip: Notion AI is best for context-aware work (summarizing, rewriting). For strategic/creative work, Claude and ChatGPT still win. Pick tools by strength.

Public Notion Site

17/20

<task>Publish Notion page as public site</task> <purpose>[describe]</purpose> <output> 1. Native Notion Sites vs third-party (Super/Potion/Feather) 2. SEO considerations 3. Custom domain 4. Design limitations 5. When to migrate off Notion </output>

Publishes Notion to public sites with SEO, custom domains, and migration guidance.

💡

Pro tip: Notion Sites (official) is now good for simple sites. For heavy customization or high-traffic, migrate to a real CMS — Notion's SEO ceiling is real.

Notion + Calendar Sync

18/20

<task>Sync Notion with calendar</task> <calendar>[Google / Outlook / Apple]</calendar> <output> 1. Native integration options 2. Notion Calendar app setup 3. Zapier/Make for complex sync 4. Source-of-truth management </output>

Syncs Notion with calendars including Notion Calendar app and automation tools.

💡

Pro tip: Notion Calendar (standalone app) blends tasks + events. Best Notion feature you're not using. Schedule tasks directly alongside meetings.

Migration Plan (To/From)

19/20

<task>Migrate [from / to] Notion</task> <source>[describe]</source> <volume>[describe]</volume> <output> 1. Export format 2. Import approach 3. What preserves vs loses 4. Phased migration plan 5. Rollback plan </output>

Plans Notion migrations with phased approach, preservation analysis, and rollback.

💡

Pro tip: Never migrate everything at once. Pick one use case, migrate, use 2 weeks, then migrate next. Big-bang migrations fail because you don't know what to keep.

Habit Tracker Template

20/20

<task>Build habit tracker</task> <habits>[list]</habits> <frequency>[daily / weekly]</frequency> <output> 1. DB schema with checkboxes 2. Streak formulas (current + longest) 3. Weekly review showing consistency 4. Progress bars 5. Home page widget </output>

Builds habit trackers with streak formulas, consistency review, and home-page widget.

💡

Pro tip: Habit trackers fail when daily logging takes >60 seconds. Make it one click. If you can't log during a toothbrush session, the system dies within 3 weeks.

Frequently Asked Questions

Claude's structured thinking shines for database schema design, complex formulas, and workspace architecture. Notion AI is faster for inline writing; Claude is better for system design and reasoning about what your workspace should look like.

Yes, particularly Formula 2.0 with its cleaner syntax (if/let/switch). Always specify properties (name + type) and version. Test in a throwaway database before using in production.

Very — relations + rollups + formulas is Claude's sweet spot. For multi-database workspaces, Claude outperforms other AI tools at designing clean relational structures.

Notion AI if you want inline speed and built-in context. Claude if you need longer-form, more nuanced, or voice-matched writing. Most power users use both — Notion AI for quick, Claude for important.

Visual design (colors, emojis, cover images) — Claude works in text. For aesthetic refinement, you still need human touch. Claude handles the logic; you handle the look.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial Explore AI for Productivity courses

7-day free trial. Cancel anytime.

Browse All Claude Prompt Collections Browse All Prompt Collections