Glossary

Look up a skill, agent, command, or shell alias. The skill, agent, slash-command, and shell-command glossaries, extracted from handbook §10–13.

← docs home

Skill Glossary

Skills give Claude specialized knowledge or workflow. Universal skills are auto-loaded everywhere; registry skills are opt-in per project.

Universal skills (`BOB_SOURCE/skills/`)

Skill	Purpose
`agent-builder`	Create and maintain agent definitions
`orchestrator`	Generate/refresh a project’s provision manifest (stack/type/capability interview)
`automation`	Switch automation level (L1/L2/L3) for current project
`code-expert`	TypeScript / SvelteKit / Cloudflare Workers / Hono / D1 / R2 / Vitest
`code-simplifying`	Reduce complexity, dedupe, refactor for clarity
`commit`	Git commit workflow (used by `/commit`)
`explaining-code`	Visual diagrams + analogies for code explanations
`pr`	Pull request workflow (used by `/pr`)
`rdb`	Toggle Remote Decision Bridge on/off
`research`	Generic research project management
`skill-creator`	Guide for creating new skills
`software-project-manager`	Strategic PM thinking (modern software delivery practices)
`stop-warp-drive`	Graceful warp-drive stop
`timelord`	Temporal accuracy guardian for documentation
`doc-audit`	Read-only documentation drift audit (#151)
`doc-sync`	Mechanical documentation drift fixes (#151)
`docs-site`	Provision and operate an engine-pluggable docs site — VitePress default, Astro Starlight alternative (#153, #689). Auto-deploy on doc changes via Cloudflare Pages (#155); see docs-site-lifecycle.md.

Registry skills (`BOB_SOURCE/registry/skills/`)

Provision per-project via cdprov or /provision add skill <name>.

Code & dev

cloudflare-dev — Cloudflare Workers development
d1-expert — Cloudflare D1 (SQLite) expertise
drupal-dev, drush — Drupal-specific
wordpress-dev — WordPress-specific
strapi-dev — Strapi headless
mcp-builder — Build Model Context Protocol servers

API & integration

api-designing — API design
kalshi-api — Kalshi-specific

Frontend & UX

frontend-design — Distinctive, production-grade UI
responsive-design — Responsive layout patterns
accessibility-auditing — WCAG 2.1 AA
ux-designing — UX design
visual-design — Visual design
visual-explainer — Visual explanations
web-artifacts-builder — Web component / page artifacts
theme-factory — Themes
design-systems — Design systems work
brand-guidelines — Brand application
information-architecting — IA

Audit & QA

performance-auditing — Web performance
seo-auditing — SEO audits
webapp-testing — Playwright-driven testing
user-research — User research projects

Deploy

deploy-cloudflare — Atomic Cloudflare Pages/Workers deploys (provides /deploy)

Document handling

docx, pdf, pptx, xlsx — Office document handling
image-processing — Image manipulation
token-report — Token usage reporting

Agent Glossary

Agents are specialized subagents the main Claude session can launch via the Task tool.

Universal agents (`BOB_SOURCE/agents/`)

Agent	When to use
`lessons-extractor`	After significant work — extract & document lessons learned
`project-historian`	Synthesize project history; answer “why did we…” questions
`requirements-analyst`	Capture or refine requirements; ensure testable acceptance criteria
`solution-architect`	Design solutions, compare alternatives, assess trade-offs

Registry agents (`BOB_SOURCE/registry/agents/`)

Code & architecture

code-expert — Deep TypeScript / Cloudflare-stack analysis
code-debugger — Bug diagnosis
code-reviewer — Code review
lead-dev-architect — Strategic technical guidance
unit-test-generator — Generate unit tests

Domain-specific

drupal-expert — Drupal 9/10
sentry-integration-expert — Sentry SDK integration

Audit

accessibility-auditor — WCAG 2.1 AA audits
seo-performance-auditor — SEO + performance
ahrefs-expert — Ahrefs SEO tools

ux-architect — UX design

PM-flavored

project-manager — Project planning / coordination
qa-strategist — Test strategy / DoD
risk-manager — Risk identification / mitigation
release-engineer — Deployment / release management
stakeholder-liaison — Stakeholder communication

Slash Command Glossary

By topic. Universal commands ship with every project. Registry commands need cdprov add per-project. Built-in commands ship with Claude Code itself.

Foundation (universal)

Command	Purpose
`/vision`	Create or update `docs/vision.md` (living strategy doc)
`/capability`	Create a capability as a GitHub Issue (label `cap`)
`/requirement`	Create a requirement as a GitHub Issue (label `req`)

Discovery (universal)

Command	Purpose
`/what-next`	Analyze project state, propose next work item

Manual development (universal)

Command	Purpose
`/start-work`	Create a feature/fix branch
`/commit`	Create a git commit
`/pr`	Open a PR with requirement traceability
`/finish-work`	Merge to master / open PR + cleanup
`/session-summary`	Close session as a GitHub Issue
`/journal`	Create decision/lesson/session issue

Autonomous (universal)

Command	Purpose
`/warp-drive [issue]`	The autonomous development loop
`/stop-warp-drive`	Graceful stop
`/auto-loop`	Legacy — predecessor of `/warp-drive`; will be removed

Parallel (universal)

Command	Purpose
`/cdfork`	Multi-agent worktree orchestration (subcommands match `cdfork` CLI)

Dev environment (universal)

Command	Purpose
`/dev-up`	Bring dev env to fully testable state

Maintenance (universal)

Command	Purpose
`/provision`	Manage provisioning (status / add / remove / refresh / diff / init)
`/rebob`	Full project state reconciliation
`/trace-mining`	Mine session journals for harness improvements

Skill toggles (universal)

Command	Purpose
`/automation`	Switch automation level
`/rdb`	Toggle Remote Decision Bridge

Registry / opt-in commands

Provision before use (cdprov add command <name>):

/research — Research project management
/deploy — Cloudflare atomic deploy (from deploy-cloudflare skill)
/release, /review-lessons, /ux-review — As provisioned

Older registry commands (/backlog, /risk, /report-bug, /change, /status, /dashboard, /standup, /retrospective) predate the GitHub-Issues hierarchy and are scheduled for removal. Do not use them on new work. /spec has been removed (#508); /solution and /incident were rewritten to file GitHub Issues (a decision and an incident issue respectively) rather than local SOL-*.md / INC-*.md files. Use /capability + /requirement + GitHub Issues with appropriate labels instead.

Built-in Claude Code & plugin commands

Always available, not BoB-specific:

Command	Purpose
`/init`	Initialize a CLAUDE.md from existing codebase
`/review`	Review pending changes
`/security-review`	Security review of pending changes
`/loop`	Run a slash command on a recurring interval
`/schedule`	Cron-style scheduling for recurring agents
`/clean_gone`	Clean up local branches that are gone on the remote (commit-commands plugin)
`/commit-push-pr`	Commit, push, open PR (commit-commands plugin)
`/help`	Built-in Claude Code help

Plugin command families also available: sentry:*, frontend-design:*, commit-commands:*. List them with /help inside Claude.

Shell Command Glossary

Every command runnable from a regular terminal.

BoB CLI aliases (set up by `bob-install.sh`)

Alias	Backed by	Purpose
`cdi`	`BOB_SOURCE/claude-init.sh`	Initialize project with BoB tooling
`cdb`	`BOB_SOURCE/claude-dashboard.sh`	Dashboard — tooling + symlink status
`cdp`	`BOB_SOURCE/claude-promote.sh`	Promote a local item to global registry
`cdl`	`BOB_SOURCE/claude-link.sh`	Link a global item into project
`cdprov`	`BOB_SOURCE/scripts/provision.sh`	Provision project from manifest
`cdproj`	`BOB_SOURCE/bin/cdproj`	Provision/reconcile the linked GitHub Project (`init/update/status/reset/item/backfill`) — see gh-projects.md
`cdr`	`BOB_SOURCE/scripts/lib/cdr.sh`	Claude Disaster Recovery — `cdr status / check / recover / reprovision / reset` (see backup-recovery.md)
`cdfork`	`BOB_SOURCE/bin/cdfork`	Parallel worktree orchestration

`claude` shell wrapper

The bob-install.sh wrapper intercepts custom flags before exec’ing the real claude CLI:

Flag	Effect
`-a1`	Set automation Level 1 (Supervised)
`-a2`	Set automation Level 2 (Trusted Dev)
`-a3`	Set automation Level 3 (Autonomous)
`-rdb`	Enable Remote Decision Bridge (Telegram)

Combine: claude -a3 -rdb is the canonical autonomous warp-drive launch.

BoB scripts (`BOB_SOURCE/scripts/` and `bin/`)

Path	Purpose
`scripts/bob-install.sh`	Set up shell wrapper + aliases (idempotent)
`scripts/deploy.sh`	Sync BOB_SOURCE → BOB_HOME (`--dry-run`, `--first-run`, `--force`)
`scripts/provision.sh`	Provision project from manifest (called by `cdprov`)
`scripts/migrate-pm-to-issues.sh`	One-shot migration: PM markdown → GitHub Issues
`scripts/migrate-to-registry.sh`	One-shot migration to registry/
`scripts/cleanup-legacy-pm.sh`	Remove forbidden PM files
`scripts/dashboard-server.js`	Local dashboard server (`cds`)
`scripts/lib/preflight-check.sh`	Common preflight (deps, tools)
`scripts/lib/safe-json-write.sh`	Atomic JSON write helper
`scripts/lib/settings-write.sh`	Safe settings.json mutation
`scripts/checks/*.sh`	`make check-*` targets
`scripts/warp-drive/state-machine.js`	Warp-drive state engine
`scripts/cdfork/{fork,status,drop,pair,from-issues}.sh`	cdfork subcommand implementations
`scripts/dev-lifecycle/{dev-up,health-check,provision-users,seed-discover,seed-generate,check-seed-coverage}.sh`	Dev env IaC
`scripts/rebob/*.js`	`/rebob` engine
`scripts/cascade-engine/*.js`	Cascade rule engine
`scripts/autoloop/state-machine.js`	Legacy auto-loop state engine

`bin/` entrypoints (intended for direct PATH use)

Bin	Purpose
`bin/warp`	Human control plane for warp-drive (`warp status`, `warp stop`, `warp config`, `warp session start/end/status`, `warp finalize`)
`bin/cdfork`	Parallel worktree orchestration (also exposed as `cdfork` alias)
`bin/cdfork-pair`	Cross-repo cdfork pair (standalone shape of `cdfork pair`)
`bin/dev-up`	Dev env lifecycle from a regular terminal
`bin/dev-health`	Shortcut for `dev-up --check`

Makefile targets

Run from BOB_SOURCE. See make help for the full list.

Verification: check, check-deps, check-schemas, check-symlinks, check-hooks, check-provisions Testing: test, test-checks, test-schemas, test-warp-drive Combined: ci (= check + test), doctor (diagnostic dump)