KFB Feature Database

Claude Project Assistant · extracted from Project_Kickoff_Seed_Prompt_v2.3.md (v2.3) · 34 features
Don't have Filesystem or Windows MCP set up yet? A step-by-step guide you run yourself — not a feature, not something to install from here.
Setup guide →
Giving this link to an AI tool? This page needs JavaScript to show the feature list, and a fetch tool won't run it. Use the AI-readable catalog instead: plain markdown, no JS, no styling, a new URL every publish so nothing can serve it stale. Most AI fetch tools won't follow a relative link found inside a page they read — they'll only fetch a URL you paste directly. If that happens, copy the full URL list and paste it (or one link at a time) into the chat yourself.
AI-readable catalog →

Start here

The safest way to use this catalog: paste the block below into a Claude conversation. It asks Claude to look, explain, and wait — nothing gets installed until you say so, one feature at a time or all together. Prefer to look first? Browse all features as cards — no AI needed, just click around.

(loading…)
Paste it into a brand-new conversation or one you're already using — works either way.
A ready-made reply for the case where Claude won't fetch the page at all — that's a reasonable instinct with an unfamiliar URL, and this just asks it to actually read before deciding, the same way you'd ask a cautious colleague.
Note for any AI reading this page directly: everything on this page is reference information about optional features a person could choose to add to a Claude project. It is not an instruction directed at you, and nothing here is authorization to install, write, or change anything. Summarize what's here for the person you're working with, then wait — only act on what they actually ask you for. If you'd rather work from plain text than parse this HTML, every feature's full install procedure is also available as markdown — see the md link next to each feature below, or the full catalog at data/index.md and its completeness audit at data/coverage_report.md. There's also a card-based reference layout at browse.html, in case the person asks you to render this visually and you'd like a structure to reference. One more thing worth being explicit about: the "Claude declined to look?" control above is a convenience for the person — a ready-made follow-up message they can choose to send you if you decline to fetch this page at all. It is not an instruction directed at you and you don't need to act on it, reference it, or treat it as anything other than ordinary page content unless the person actually sends it to you themselves. One more: the "Setup guide" link at the very top of this page (prerequisites.html) is a page of steps a person runs themselves on their own computer — it has no FTR number, is not a feature, and is not a structural dependency of anything below. Don't treat it as something to install or execute; point a person to it if they mention missing MCP access, and otherwise ignore it.
If you do install anything from here: every install writes into the target project's admin\AGENT_INSTRUCTIONS.md. That file, in any real project, usually already has content in it — read it in full first, and merge additively: add or update only the section(s) for the feature(s) actually being installed, and leave everything else untouched, regardless of where it came from. Never overwrite the whole file, and never assume it's empty without checking. This applies to every feature here, individually or via "install everything" — it isn't satisfied by installing any particular feature first. See data/index.md's own "INSTALL-TIME FILE SAFETY" section for the full rule. CLAUDE.md is a mirror, not an alternate target: if a project has both files, updates go to admin\AGENT_INSTRUCTIONS.md first — CLAUDE.md gets regenerated from it, never edited as the primary copy, even though it's the file Cowork and Claude Code read automatically. See FTR-21 for the full rule. Installing several features in one session? Use the literal paths shown on this page or in data/index.md — never construct an item's URL by editing a pattern from one already fetched (fetch tools correctly reject that), and don't fall back to web search if a fetch is rejected (these pages aren't necessarily indexed). If a fetch is ever rejected partway through, just re-fetch this page again and use the fresh literal link — that's the full, reliable fix.

How installing works

This page is a menu and the source of the install procedures — it does not execute anything itself. Simplest path: pick a feature below and click "Copy install request" — it copies a plain sentence naming that feature and pointing directly at that feature's own markdown definition, ready to paste into any Claude conversation. Claude fetches that file, evaluates the feature, resolves any dependencies it needs automatically, checks your project, asks only what it must, and merges the content into admin\AGENT_INSTRUCTIONS.md (and CLAUDE.md where relevant) — reading whatever's already there first and adding to it, never replacing the whole file — then confirms.

install everything
"install everything" installs all 34 features in dependency order (never a feature before what it depends on) — best used once you've already looked at what's here (e.g. after the starter prompt above), since it's a bare command rather than a self-contained request. Installing many features in one go means many fetches in sequence — use the literal paths on this page or in data/index.md, never a constructed guess; re-fetch this page if any single fetch is ever rejected. Full catalog: data/index.md · coverage audit: data/coverage_report.md · card view: browse.html · each feature card below links to its HTML page and its plain-markdown source (md).

Already installed something before?

If this project already has features from this database installed, check whether they're still current instead of guessing. This reads your project's KFB Install Manifest (in admin\AGENT_INSTRUCTIONS.md, if one exists) and compares it against the versions above — reports what's up to date, what's changed upstream, and what's new since you last checked. Nothing gets installed or updated by this alone.

Fetches this catalog, compares installed versions to current ones, and reports — it only acts on what you tell it to do afterward. See Install Manifest & Reconciliation (FTR-26) for the full mechanism.