feature_slice
The whole feature
Every file a change touches, by layer, with why.
One MCP call hands Claude Code, Cursor or VS Code the page, API, route, data model, auth checks and tests behind any feature.
Your agent asks once. It gets back every file the change touches, in order, with proof.
“Change how API keys are revoked.”
feature_slice({ feature: "api key revocation" })
app/settings/keys/page.tsx:24calls revokeKeylib/api/keys.ts:41DELETE /api/keys/:idapp/api/keys/[id]/route.ts:12handles the requestlib/auth/scopes.ts:8requireScope('keys:delete')prisma/schema.prisma:57model ApiKeytests/keys.test.tsnpx vitest runIllustrative example. Links come from real call sites, requests and ORM calls, each with file:line.
feature_slice
Every file a change touches, by layer, with why.
trace_flow
Entry point to database, with evidence.
impact
Dependents and the exact tests to run.
review_diff
Secrets, broken imports, drift. SARIF ready.
api_map
Auth, scopes and roles for every route.
search
Ranked snippets. Optional local neural model.
The same tools your agent calls over MCP, from your terminal.
$ cb-trainer slice "article comments"
🧩 Feature slice: "article comments" (16 files, ~5,334 / 6,000 tokens)
[server]
src/app/routes/article/article.controller.ts — search match
src/app/routes/article/article.service.ts — search match
src/app/routes/article/comment.model.ts — search match
src/app/routes/profile/profile.utils.ts — favoriteArticle uses profileMapper
[data]
src/prisma/schema.prisma — search match
Flows:
routes.ts → articlesController → addComment → HttpException