ai-fob

Research-driven assets for AI coding assistants.

AI-FOB deploys skills, agents, and commands into your project for Claude Code. It enforces a structured workflow: plan the task, research the documentation, design the implementation, then build.

Why AI-FOB?

LLM training data goes stale. When AI coding agents skip documentation research because an API seems "standard" or "well-known," they produce implementations built on outdated assumptions.

Prefer retrieval-based reasoning over pre-training-led reasoning.

AI-FOB commands enforce a pipeline that gathers version-matched documentation and maps existing codebase files before any code is written.

Installation

# Interactive mode
npx ai-fob

# Install coding preset to current project
npx ai-fob --preset coding

# Install all Claude Code presets globally (coding + cc-assets)
npx ai-fob --preset all-claude --global

Options

| Flag | Short | Description | |------|-------|-------------| | --preset <name> | -p | Select preset (coding, cc-assets, pi-assets, pi-coding, llm-wiki, all-claude) | | --local | -l | Install to ./.claude/ (default) | | --global | -g | Install to ~/.claude/ | | --list | | List available presets and their contents | | --dry-run | | Show what would be installed without doing it | | --force | -f | Overwrite all files, even locally modified ones | | --help | -h | Show help |

Presets

coding

The full research-driven coding workflow. Includes planning, research, building, and validation.

Skills: brainstorm-plan, convex-best-practices, vercel-react-best-practices, reverse-engineering, testing-and-validation, agent-browser, retrospective-analysis, feature-documentation, FOB-state-context

Agents: architect, builder, build-validator, plan-validator, explorer, docs-researcher

Commands: plan-project, setup-project, create-highlevel-plan-phases, build-phase-V2, build-feature, plan-features, reverse-engineer-from-code, quick-fix, update-docs, learnings, add-todo, handoff

cc-assets

Tools for building Claude Code primitives (skills, agents, commands).

Skills: claude-code-primitives, brainstorm-plan

Agents: meta-agent, meta-architect-agent, meta-validator-agent

Commands: plan-cc-assets-phases, build-cc-assets-phases

llm-wiki

A domain-agnostic, citation-backed wiki maintained by an LLM curator. Scaffold with /wiki-init, populate with /wiki-ingest, read with /wiki-query, and enforce integrity with /wiki-lint. Based on Karpathy's LLM Wiki pattern.

Skills: llm-wiki, brainstorm-plan

Agents: wiki-curator

Commands: wiki-init, wiki-ingest, wiki-query, wiki-lint

all-claude

All Claude Code presets (coding + cc-assets). Does NOT include pi-coding, pi-assets, or llm-wiki — those must be installed separately.

How Updates Work

Run npx ai-fob@latest --preset coding to upgrade.

• Unmodified files are updated to the latest version
• Locally modified customizable files (like statusline.sh) are preserved -- the new version is saved as .ai-fob-new for you to compare
• Your custom assets (agents, skills, commands you created) are never touched
• settings.json is deep-merged -- your existing settings are preserved, new keys are added
• Per-project runtime configuration lives in runtime/ at the project root (not inside .claude/ or .pi/) and is never overwritten by ai-fob. Populate runtime/project.json via /setup-project; copy runtime/auth.example.json to runtime/auth.json and fill local test credentials when needed (the latter is gitignored).

A .ai-fob.json file in your .claude/ directory tracks what was installed and detects modifications.

Upgrading from v1.10.x

v1.11 moves per-project credentials (auth.json) and adds a per-project project.json for scripts/URL/mobile config. Both live in a shared runtime/ directory at the project root, replacing the v1.10 per-skill .claude/skills/testing-and-validation/auth.json (and Pi equivalent).

Two-step upgrade (the migration command ships in v1.11, so the package upgrade comes first):

# 1. Install v1.11 — this also installs the /migrate-runtime-config command.
#    The upgrade overwrites your v1.10 SKILL.md files (the customizable
#    carve-out is gone), which is intentional: per-project values now live
#    in runtime/project.json instead.
npx ai-fob@latest --preset coding

# 2. In Claude Code, from your project root, run the one-shot migration:
/migrate-runtime-config

The migration command:

• Atomically moves .claude/skills/testing-and-validation/auth.json (and Pi equivalent) to runtime/auth.json.
• Recovers your previous v1.10 SKILL.md tables to populate runtime/project.json. Because step 1 already overwrote the on-disk SKILL.md, the parser walks git history for the pre-upgrade version: it tries git show HEAD:<path> first, then walks back through the last 20 commits touching that file.
• Falls back to a template-only runtime/project.json (all values null) only when no git history is available or no commit of the v1.10 SKILL.md exists. In that case, populate runtime/project.json manually from your previous scripts.
• Deletes the orphan v1.10 files from both skill directories.
• Prints a verification summary showing which source it parsed from.

License

MIT