メニュー
Trace a feature across the layered architecture (REST v2, GraphQL, Service, Repository, DB, Errors) and explore the entity source tree — includes how to read the 21k-line supergraph.graphql without loading it whole
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Guide for implementing REST and GraphQL APIs (create, get, search, update, delete, purge, scope prefix patterns, admin_ prefix, SearchScope, BaseFilterAdapter, @api_function, Click CLI)
./bai v2 CLI usage for testing/verifying API endpoints and managing resources — entity-command reference, login/config, search patterns, testing workflow (REST API client, NOT the v1 backend.ai CLI)
Guide for writing and managing BEPs (Backend.AI Enhancement Proposals) - creation workflow, document segmentation, context-for-ai blocks, Decision Log
Guide for implementing Backend.AI client SDK and CLI (Session, BaseFunction, @api_function, Click commands, Pydantic models, FieldSpec, output handlers, APIConfig, testing)
Inspect and apply database schema migrations (alembic current/heads, upgrade, downgrade, diverged heads) for Backend.AI components (manager, accountmgr, appproxy)
Local server management — ./dev start/stop/restart via tmux, startup-crash debugging, pre-flight infra checks, raw component start-server commands, post-change restart workflow
| name | code-trace |
| description | Trace a feature across the layered architecture (REST v2, GraphQL, Service, Repository, DB, Errors) and explore the entity source tree — includes how to read the 21k-line supergraph.graphql without loading it whole |
| tags | ["exploration","navigation","rest-api","graphql","layers"] |
Locate where a feature lives across layers. The codebase is split per entity, so once you know the entity name (user, session, deployment, …) every layer is a predictable path.
{entity} = entity name)| Layer | Path | What's there |
|---|---|---|
| REST v2 entry | manager/api/rest/v2/{entity}/registry.py | RouteRegistry — method + path + middleware → handler method |
| REST v2 handler | manager/api/rest/v2/{entity}/handler.py | V2{Entity}Handler — calls a Processor |
| GraphQL resolver | manager/api/gql/{entity}/resolver/{query,mutation}.py | Strawberry query/mutation resolvers |
| GraphQL types | manager/api/gql/{entity}/types/ | node, inputs, payloads, filters, enums, scopes |
| GraphQL root | manager/api/gql/schema.py | assembles all resolvers into the schema |
| Service | manager/services/{entity}/ | service.py, processors.py, actions/, types.py |
| Repository | manager/repositories/{entity}/ | repository.py, creators.py/updaters.py/purgers.py, db_source/ |
| DB models | manager/models/ | SQLAlchemy tables |
| Errors | {component}/errors/{domain}.py | see manager/errors/AGENTS.md |
Flow: API handler → Processor → Service → Repository → DB. Handlers never call Services directly.
grep -rn "reg.add" manager/api/rest/v2/{entity}/registry.py (REST) or open gql/{entity}/resolver/.services/{entity}/actions/.It is a generated single file. Extract only the block you need:
# find the line number of a type/input/query
grep -n "^type User\b\|^input .*User\|^type Query\|^type Mutation" supergraph.graphql
Then Read with offset/limit around that line. For the actual resolver logic, jump to the source under gql/{entity}/ instead — the schema only shows the contract.
/api-guide — implement REST/GraphQL endpoints/repository-guide, /service-guide — layer patternsmanager/errors/AGENTS.md — find/define exceptions