Nuclino

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me a team wiki that replaces Nuclino: pages that open instantly, links between them, and nothing to configure.

STACK
- Node 20+ with Fastify, server-rendered HTML with a little vanilla JS
- SQLite through better-sqlite3, WAL mode, with FTS5
- Caddy in front

THE ONE IDEA
- The reason simple wikis succeed is that people write in them. Everything below is in service of that: a page opens in under a hundred milliseconds, a new page is one keystroke away, and there is nothing to decide before you start typing
- No page templates to choose, no folder to pick, no properties to fill in, no approval workflow. Those are the features that turn a wiki into a place people avoid
- Every feature added must be weighed against the time it adds before somebody can type a sentence

THE DATA MODEL
- workspaces: id, name, slug
- pages: id, workspace_id, collection_id, title, title_lower, body_md, body_html, created_by, updated_by, created_at, updated_at, is_archived
- revisions: id, page_id, body_md, author_id, at — every save, so nothing is ever lost
- links: from_page_id, to_page_id, kind — resolved at save time, which is what makes backlinks and the graph free
- collections: id, workspace_id, name, position — one level, deliberately. Nested hierarchies are where wikis go to die
- attachments: id, page_id, path, sha256, mime, bytes
- comments: id, page_id, anchor_text, author_id, body, resolved_at, created_at
- presence in memory: page_id, user_id, cursor — never stored

WRITING
- Markdown with a live editor: the formatting appears as you type rather than in a preview pane
- Slash commands for the few blocks that matter — heading, list, checklist, code, quote, table, image, embed
- Typing a bracketed page name links to it, creating it if it does not exist. That single interaction is what builds a wiki organically
- Autosave continuously; there is no save button and no draft state
- Paste from a document or a web page keeps its structure and drops its styling

LINKS AND THE GRAPH
- Backlinks on every page, with the sentence around each mention for context
- Unlinked mentions offered rather than created
- A graph view of pages and links. It needs no configuration, which is precisely why it is worth having — it is a free byproduct of the links table
- The graph is a browsing aid, not a report. Keep it simple and fast

COLLABORATION
- Real-time editing with presence, over WebSockets, with the document as a sequence of operations and a periodic persist
- Use an existing conflict-free replicated data type library for the text. Writing one is a research project, and getting it subtly wrong loses people's writing
- If real-time proves too much, the honest fallback is a per-page lock with a clear indicator of who is editing — worse, but never destructive. Choose deliberately and say which

SEARCH
- FTS5 over titles and bodies, instant, with the matching lines shown
- Titles ranked above bodies; a page called 'Onboarding' must be the first result for 'onboarding'
- A keyboard shortcut that opens search from anywhere, arrows to move, Enter to open. This becomes the main navigation, and everything else is secondary
- Filters by collection, author and date, but do not put them in the way

THE INTERFACE
- Three regions: a sidebar of collections and recent pages, the page, and the backlinks. Nothing else on screen
- Dark and light, one accent, a self-hosted variable font
- Fast on a poor connection: server-rendered HTML, no framework bundle
- Works properly on a phone, because half of wiki reading happens on one

ACCESS
- Single sign-on through OIDC, with magic links as a fallback
- Permissions per workspace and per collection: read, write, admin. Not per page — per-page permissions are how a wiki becomes a place where nobody can find anything
- Public sharing of a page or a collection by token, read-only, revocable

HISTORY
- Every revision kept, with a diff view and a one-click restore that itself writes a revision
- An archive rather than a delete, with a stated retention before anything actually goes

EXPORT
- The whole workspace as a directory of Markdown files with the attachments and the link structure intact, in one command
- A single page as Markdown, HTML or PDF
- Nothing here is trapped, and the README says so

OPERATIONS
- .env: DATABASE_PATH, STORAGE_PATH, BASE_URL, SESSION_SECRET, OIDC_*
- Migrations on boot, each once
- Nightly backup off the machine, restore script — this holds the team's institutional memory
- Health endpoint

WHAT MATTERS MOST
Speed and the bracketed link. Measure the time from clicking a page to reading it and keep it under a tenth of a second, and make creating a linked page a single gesture. A wiki that is slow or ceremonious is a wiki that quietly stops being written in, and no feature recovers from that.

Give me the repository, migrations, .env.example, a seed workspace, and a README with deploy steps behind Caddy.