File
SMF·CAPACITIES
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·CAPACITIES

Can a prompt replace Capacities?

Notes & knowledge management — notes, wikis and personal knowledge bases

Yes Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$12/moSource: capacities.io · Checked on July 31, 2026
Per year
$144
Build time
One sitting
Votes
0 votes
Yes (checked)AlmostNot yet

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: sync, collaboration, and capture polish
Exhibit Q Questions

Verdict

A note system where every page is a typed 'object' — a Person, a Book, a Project — with structured properties specific to its type, is a real weekend-to-week build once you accept a fixed, small set of object types rather than Capacities' fully customizable type system. What doesn't survive: user-definable custom object types with their own property schemas, and cross-device real-time sync.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a note system where pages are typed objects, not freeform documents — Capacities' actual distinguishing idea. Use Next.js/TypeScript with Postgres. Implement a small fixed set of object types to start: Person, Book, Project, Note, each with its own structured property schema — a Person has name, email, and tags; a Book has title, author, rating, and status. Creating a new object requires picking a type first, then filling in that type's specific fields, plus a freeform Markdown body for everything else. Build a browsable, filterable list per type, such as all Books filterable by status, and a simple search across all objects regardless of type. Support linking one object to another, such as a Project linking to several People, with the link shown on both sides. Do not build a user-facing type designer for arbitrary custom types, real-time multi-device sync, or an AI-assisted property extraction feature — those are out of scope; this ships with a fixed, useful set of types rather than a fully general type system. Requires hosting and a database; no external API key needed.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 user-definable custom object types with their own schemas
  • B.2 cross-device real-time sync
  • B.3 a visual object-relationship graph
  • B.4 AI-assisted property extraction

Prior art

Exhibit C — Why people still pay: sync, collaboration, and capture polish

A few hardcoded object types is a weekend; letting users define arbitrary new types with their own property schemas, safely and flexibly, is meaningfully harder generalized product design.

Questions

Can I create my own custom object types, like in Capacities?

Not in this build — it ships with a fixed set: Person, Book, Project, Note. Letting users define arbitrary new types with their own schemas is real, harder generalized product design this prompt doesn't attempt.

How is this different from a tag-based notes app?

Every page has a type with structured fields specific to it, not just freeform text with tags — a Book object has a rating field, not just a tag, which changes how you can filter and browse.

Does it sync across my devices in real time?

No — that's out of scope. This runs as a hosted web app you'd access from any device, but without real-time multi-device conflict handling.

What does it cost to run?

Hosting and a database — typically a few dollars a month, since there's no external API this build depends on.

Receipt

Already built this yourself?