Find project symbols across proto, schema, handlers, hooks and stores with forge project shapes; inspect library APIs without hunting generator source.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Shapes?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/reliant-labs-shapes)
---
name: shapes
description: Find project symbols across proto, schema, handlers, hooks and stores with forge project shapes; inspect library APIs without hunting generator source.
---
# Project reconnaissance
From the start-here skill: use this before hunting symbols across layers.
### `forge project shapes` — start recon here, not with `grep`
**Use it the moment you need to know where something is or what shape it has.**
It answers, in ONE call, the question that otherwise becomes a sequence of
greps: *where is this symbol, in every layer, and what is its signature?*
```bash
forge project shapes # every symbol in the project
forge project shapes --grep Estimate # one entity across ALL layers at once
forge project shapes --kind rpc,handler # what is DECLARED vs what is IMPLEMENTED
forge project shapes --unimplemented # declared rpcs with no handler, or only a stub
forge project shapes --service Chat # one service's rpcs and handlers
```
Every line carries `file:line`, so the next step is a targeted read — never
another search:
```
rpc RoofopsService.ListMaterials proto/services/roofops/v1/roofops.proto:368 in=ListMaterialsRequest out=ListMaterialsResponse
message Material proto/services/roofops/v1/roofops.proto:737
table materials db/migrations/00010_create_materials.up.sql:9
handler RoofopsService.ListMaterials internal/handlers/roofops/handlers_crud.go:790
hook useListMaterials frontends/dashboard/src/hooks/roofops-service-hooks_gen.ts:212
```
Reach for it when you would otherwise:
- hunt for a file — `--grep <Name>` names it and the line
- open a large proto to find one message — the line number takes you straight there
- ask "is this RPC implemented yet?" — `--unimplemented` lists every declared rpc with no handler or an `unwired-stub` (handler lines are named like their rpc, and list rpc handlers only)
- ask "does a hook exist for this?" — `--kind hook`
It parses the protos, migrations and source **live on every call** (~2s on a
15-entity project). It deliberately does NOT read `gen/forge_descriptor/`:
that file is a derived cache, and a recon answer that is confidently wrong is
worse than no answer.
### Call graphs: `gopls`, not grep
`shapes` says where a symbol is. Two questions it does not answer, and grep
cannot: **who calls this / what does it call**, and **what implements this
interface**. A Go call site never names its receiver's type and an
implementation never names its interface, so a grep walk matches every
same-named method (`Get`, `Handle`, `Execute`) and the error compounds at each
level. Ask `gopls`:
```bash
gopls call_hierarchy path/to/file.go:LINE:COL # callers AND callees
gopls implementation path/to/file.go:LINE:COL # interface -> concrete types
```
Get LINE:COL from an `rg -n` hit (COL is the 1-based offset of the
identifier) and chain both into one command. Everything else — a definition,
references to a distinctive name — stays with `shapes` or `rg`. Use
`forge project libraries` for forge's own packages, `gopls` for this repo's
code.
**Never search the filesystem for forge's own source.** Name the package and
`forge project libraries` prints its full exported API — every signature, no
file reading:
```
forge project libraries svcerr the whole package
forge project libraries crud orm svcerr three packages, one call
forge project libraries orm.Context one type, with its methods
```
Reach for that rather than `go doc <pkg>`, which collapses every struct and
interface to `struct{ ... }` and lists no methods — it cannot tell you
`crud.Repo.UpdateMasked`'s parameters. (For your OWN generated interfaces,
`go doc ./internal/db Store` is fine: `go doc` renders interfaces in full.)