Imported from xinyo/ClawdBook (AGENTS.md). Install upstream with npx skills add xinyo/ClawdBook. Copyright stays with the author.

Engineering Principles

When the #plan command is triggered, ask for confirmation before executing the plan.
Prefer pnpm when installing dependencies.
Prefer use Vite for project initialisation.
Use pnpm create vite@latest <project_name> -- --template react-ts to spin up a new React + Vite package with TypeScript checks ready
Find the CI plan in the .github/workflows folder
Use vitest for the testing framework with @testing-library/react for component testing
All functional changes should be covered by unit tests
Always run pnpm test after modifying JavaScript/Typescript files
React Component Test files should be placed alongside the component they test with .test.tsx extension
Mock external dependencies like uuid in tests
Every PR must include a changes summary in the description.
Branch names and PR titles must always follow semantic conventions.
Ask for confirmation before adding new production dependencies.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install ClawdBook and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

ClawdBook

About

Engineering Principles

Use it

Install ClawdBook and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews