Guru

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 the knowledge base I actually need instead of Guru.

Copy the one idea that makes this product different from a wiki: **every card has an owner and an expiry date.** A wiki rots invisibly; this one tells you which parts have rotted.

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

THE DATA MODEL
- cards: id, title, body_md, collection_id, owner_id, verify_every_days, verified_at, verified_by, status
- revisions: id, card_id, body_md, author_id, at — append-only, so a wrong edit is recoverable
- verifications: id, card_id, verifier_id, at, note — append-only, and the audit somebody will ask for
- uses: id, card_id, person_hash, context, at — where a card was actually read
- links: id, card_id, target_kind, target_ref — the ticket, the deal, the page it belongs to

VERIFICATION, THE FEATURE THAT MATTERS
- Every card names one person and an interval. When it lapses, the card is marked unverified **everywhere it is displayed**, not just in an admin list
- Verifying is one button. If it takes a form, nobody does it, and the whole mechanism fails
- A weekly digest to each owner listing only their lapsed cards, never everybody's
- A public count of the unverified share of each collection. **That number is the health of your knowledge base and it is the only honest one**

SEARCH THAT FINDS THINGS
- FTS5 over title and body with a title weighting; prefix matching as somebody types
- Boost recently used and recently verified cards, demote unverified ones
- Record every search that returned nothing. **The empty-result log is the list of cards to write next**, and it is the best content roadmap this kind of product has

WRITING
- Markdown, one screen, no folders more than two deep. Depth is where knowledge bases go to die
- A card is one answer to one question. Title it as the question — 'how do I refund a customer' — because that is what people search
- Templates for the recurring shapes: a policy, a how-to, a definition

GETTING IT TO WHERE PEOPLE ARE
- A search endpoint returning ranked cards as JSON, so your chat tool, help desk or command palette can call it
- A keyboard shortcut opening search over whatever you are doing
- Every read recorded with its context, so 'which cards do support actually use' is answerable and the rest can be archived

WHAT MATTERS MOST
The expiry with a named owner, and the empty-search log. One stops the base filling with wrong answers; the other tells you what to write.