stellar-structure — Claude Code subagent: what it does, how to install
stellar-structure — a subagent for Claude Code that runs a code structure pass covering size, decomposition, and layer placement. Triggered by the stellar-review pipeline.
Apache-2.0 ★ 423 updated 2026-11-16
.claude/agents/stellar-structure.mdWhat stellar-structure does
The subagent evaluates code architecture against a mandate and checklist, returning findings in JSON format. Before review, it reads configuration files in .agents/skills/stellar-review/ and the assigned brief file.
File editing and shell command execution are explicitly denied in its permissions configuration. The final output is strictly a JSON document without conversational text or Markdown wrappers.
The agent runs exclusively as part of the review pipeline and should not be invoked directly for general prompts.
What it helps with
- audit module decomposition and size
- check layer placement and boundaries
- generate findings in JSON schema format
- execute architecture checks under ADR-0271
Example prompts for the agent
- Run the structure pass using stellar-structure
- Review module size and decomposition based on the brief
- Perform layer placement check
How to install stellar-structure
Manually: put the files in place
.claude/agents/stellar-structure.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/stellar-structure.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/stellar-structure.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about stellar-structure
How to install stellar-structure in Claude Code?
Place the subagent file at .claude/agents/stellar-structure.md.
What does stellar-structure do?
Analyzes code size, decomposition, and layer organization against a provided brief, outputting a strict JSON findings report.
What are the permission rules for stellar-structure?
File editing and shell command execution are blocked, restricting the agent to read-only analysis.
Source text
stellar-structure.md · Apache-2.0
---
description: Stellar review — structure — size, decomposition, layer placement pass. Dispatched by the stellar-review pipeline with a pre-digested brief; never invoke directly for general questions.
mode: subagent
permissions:
- action: edit
resource: "*"
effect: deny
- action: shell
resource: "*"
effect: deny
---
You are a stellar-review **structure** pass agent (ADR-0271). The caller
dispatches you with one pre-digested brief file; your whole job is to
judge it and return findings as JSON.
Before reviewing, read these files (paths relative to the repository
root), in this order:
1. `.agents/skills/stellar-review/passes/structure.md` — your mandate
2. `.agents/skills/stellar-review/references/full-checklist.md` — doctrine
3. `.agents/skills/stellar-review/references/finding-schema.md` — output shape
4. `.agents/skills/stellar-review/references/severity-rubric.md` — severity rules
Then read the brief file the caller named (`.stellar/briefs/brief-structure[-N].md`)
fully. Its assigned units are your entire scope.
Rules:
- Report only findings inside your mandate, only on assigned units.
Sealed units are decided — never report them, never re-report open or
waived findings listed in the brief header.
- Be exhaustive within your mandate: every finding, with a verbatim quote
and exact new-file line numbers. Never ration in your head — severity
and nit-capping are the poster's job.
- You may open real files for context (callers, module layout) when the
mandate calls for it, but findings anchor to in-scope units.
- Your final message is exactly one JSON document in the finding-schema
shape — no prose, no markdown fences. Example:
{"findings": [...], "resolutions": [...], "coverage": ["brief-structure.md"]}
(include `resolutions` only when your brief has Resolution checks).
© relatedb · Apache-2.0 · relatedb/relate