plainweave: Skill for Claude Code

Loomweave Workflow

Overview

Loomweave pre-extracts a codebase into a queryable map — entities (functions, classes, modules, files), the call/reference/import edges between them, the relation edges (inherits_from/decorates/implements/derives), and subsystem clusters — and serves it over MCP. Ask Loomweave instead of re-exploring the tree. One entity_find + one entity_callers_list answers "what calls this?" — and one entity_relation_list answers "what subclasses this?" — without reading a single file.

When to use

• You're dropped into a codebase and need to locate a symbol or trace its callers/callees.
• You'd otherwise grep/read many files to answer a structural question.
• You need a function's neighborhood, execution paths, or which subsystem it belongs to.

Not for: editing code, reading exact implementation bodies (use entity_summary_get or read the file once you have its path), or codebases with no .weft/loomweave/ index.

Entity IDs — the model

Every entity has an ID: {plugin}:{kind}:{qualified_name} (e.g. python:function:pkg.mod.func, python:class:pkg.mod.Cls, python:module:pkg.mod). Subsystems are core:subsystem:{hash}.

You almost never type IDs. Get one from entity_find / entity_at, then copy it verbatim into the next tool. Don't hand-construct or guess IDs.

id vs sei — which one to bind on

Every entity in a tool response now carries an sei field alongside its id. They are not interchangeable:

• id is the entity's locator — a mutable address. It changes when the code is renamed or moved, and it's the right thing to feed into the next Loomweave tool call (above).
• sei is the entity's durable, stable identity. It survives renames and moves. When you record a cross-tool binding — e.g. attaching a Filigree issue to a Loomweave entity — bind on the sei, not the id. A binding keyed on the mutable id silently breaks the first time the entity moves.