Notion Database Architect

Notion is simultaneously flexible and dangerous. Flexible because inline databases, relations, rollups, and formulas let you build surprisingly sophisticated systems. Dangerous because most people build systems they can't maintain — 15 interconnected databases with rollups of rollups that break when a property gets renamed and can't be debugged when they do. Good Notion architecture is simple at the interaction layer and complex only where complexity earns its keep.

The skill won't design anything before three things are clear: the actual workflow (walk me through what you do, step by step), who else uses this, and what already exists. Don't ask "what database do you want?" — ask what work happens. The workflow reveals what data matters; the user's preconceptions about structure usually don't. Existing spreadsheets are gold because they reveal the real schema — which columns were actually used and which were always empty.

The relational rules are explicit. Use a relation when the related item has its own properties that matter, when you need to roll up data from it, or when one item gets linked to multiple things. Use a multi-select tag for simple labels with no properties of their own and under 20 values. Use a separate database only when the entity has its own lifecycle, gets viewed on its own, and is referenced by multiple things. The most common mistake is creating a database for something that should be a select — if your "Categories" DB has nothing but a name column, it shouldn't exist.

Rollups are for aggregation — counting, summing, progress, status inheritance — not for displaying a single property from a related item. Formulas should be useful and short: calculated dates, simple math, conditional text. Anything that requires a comment to explain has crossed into territory Notion handles badly. When the user requests nested cascading rollups, the skill pushes back explicitly — Notion formulas referencing rollups of rollups are fragile, break silently when properties get renamed, and can't be debugged. If you need that level of calculation, you need a spreadsheet or Airtable.

There's also a redirect mode. The skill will tell you Notion isn't the right tool when you need complex calculations (use a spreadsheet), real-time collaboration on structured data (Airtable handles concurrent edits better), high-volume data above 1,000 items in a single view (Notion slows down), or complex automation triggers (use Zapier/Make alongside). The deliverable is a schema with every property typed, options listed, relations targeted, formulas defined, marked required or optional, and why each property exists — so you don't open it in three months wondering what something was for.