/lego-show — Lego Show
Category: Lego (Modular Models) · Primary agent: modeling-methodology-specialist
Shows a model as a lego set: baseplate, bricks, joints, open studs, parts bin and suggested bricks, in text, an HTML picture, or a Mermaid diagram.
Arguments: whatever the user wrote after the command name.
Purpose
Show a model as a lego set in terms an economist can act on: what the core is, which components are attached and what they exchange, which inputs still run on stubs and what that means economically, which bricks could fill the gaps, which blocks are solved jointly, and in what order. On request it draws the set as a self-contained HTML picture or a Mermaid diagram, with bricks stacked on the bricks whose outputs they read, at any number of levels.
Use it when explaining a model to colleagues or counterparts, deciding what to add next, or documenting structure.
Do not use it when the wiring must be verified (/lego-check).
Before you start
- Check required inputs. For each input below record
FOUND or ABSENT (never 'assumed'):
- A model.lego.json manifest (create one with /lego-map)
If a required input is
ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
- Check confidentiality. Identify the data classification level of the inputs (
.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow.
- Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.
Agents
modeling-methodology-specialist — primary agent; coordinates the work and integrates results
economic-reasoning-specialist — Frames the economic question and tests whether results make economic sense
Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.
Workflow
- Run
python tools/lego.py show <manifest> and read the output to the user in plain language: what the core is, which bricks are attached, what each exchanges
- Explain the open studs: which inputs currently run on stubs and what that means economically (for example 'exports are exogenous, so the exchange rate cannot affect demand through trade')
- Offer the catalog bricks that would fill each open stud, and the parts bin of detached bricks
- Point out simultaneous blocks (solved jointly) and the solve order
- Explain the colours: the brick colour is the component type; the studs show what the brick is made of (x variables, = equations, θ parameters, ε shocks, D data series, ≤ constraints), in proportion to their counts
- Read out the Inside the bricks findings: non-square bricks, parameters that are assumptions without a source, constraints not yet verified in a run
- On request, write the picture with
--html <file> (a self-contained page) or --mermaid for documents. Bricks stack on the bricks whose outputs they read, with no limit on levels. To build the picture as a stepped pyramid, show the plan of python tools/lego.py arrange <manifest> and, with approval, add --apply; --style grid returns to the default. Positions change the picture only, never the wiring; report any picture: warnings from check
Checkpoints with the user
- Before applying a new arrangement to the picture
Common pitfalls
- Describing channels the manifest does not contain
- Confusing picture positions with wiring
- Ignoring stubs when interpreting results
Output
(conversation); optionally lego-view.html next to the manifest
The explanation is given in conversation; the optional HTML page or Mermaid diagram sits next to the manifest.
Gate / verdict
- The description matches the tool's output; nothing is inferred beyond it
- Economic consequences of open studs are explained
- Element findings (non-square bricks, unsourced parameters, unverified constraints) are reported when declared
Suggested next steps
/lego-add
/lego-detach
/lego-swap
1---2name: lego-show3description: "Shows a model as a lego set: baseplate, bricks, joints, open studs, parts bin and suggested bricks, in text, an HTML picture, or a Mermaid diagram."4metadata:5 source: https://skillmd.com/skills/majiayu000/lego-show6---78<!-- Generated from .claude/skills/lego-show/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->910# /lego-show — Lego Show1112**Category:** Lego (Modular Models) · **Primary agent:** `modeling-methodology-specialist`1314Shows a model as a lego set: baseplate, bricks, joints, open studs, parts bin and suggested bricks, in text, an HTML picture, or a Mermaid diagram.1516Arguments: whatever the user wrote after the command name.1718## Purpose19Show a model as a lego set in terms an economist can act on: what the core is, which components are attached and what they exchange, which inputs still run on stubs and what that means economically, which bricks could fill the gaps, which blocks are solved jointly, and in what order. On request it draws the set as a self-contained HTML picture or a Mermaid diagram, with bricks stacked on the bricks whose outputs they read, at any number of levels.2021**Use it when** explaining a model to colleagues or counterparts, deciding what to add next, or documenting structure.2223**Do not use it when** the wiring must be verified (`/lego-check`).2425## Before you start261. **Check required inputs.** For each input below record `FOUND` or `ABSENT` (never 'assumed'):27 - A model.lego.json manifest (create one with /lego-map)28 If a required input is `ABSENT`, that part is **`NOT ASSESSED — NO DATA`**: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.292. **Check confidentiality.** Identify the data classification level of the inputs (`.claude/docs/confidentiality-and-ai-use.md`). Do not proceed with restricted or confidential data in a way the policy does not allow.303. **Collaboration.** Follow `.claude/docs/collaboration-protocol.md`: ask questions first, present options, get approval before writing files, and update `production/session-state/active.md` after each approved section.3132## Agents33- `modeling-methodology-specialist` — primary agent; coordinates the work and integrates results34- `economic-reasoning-specialist` — Frames the economic question and tests whether results make economic sense3536Each agent is defined in `.claude/agents/<name>.md`. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.3738## Workflow391. Run `python tools/lego.py show <manifest>` and read the output to the user in plain language: what the core is, which bricks are attached, what each exchanges402. Explain the open studs: which inputs currently run on stubs and what that means economically (for example 'exports are exogenous, so the exchange rate cannot affect demand through trade')413. Offer the catalog bricks that would fill each open stud, and the parts bin of detached bricks424. Point out simultaneous blocks (solved jointly) and the solve order43 - Explain the colours: the brick colour is the component type; the studs show what the brick is made of (x variables, = equations, θ parameters, ε shocks, D data series, ≤ constraints), in proportion to their counts44 - Read out the **Inside the bricks** findings: non-square bricks, parameters that are assumptions without a source, constraints not yet verified in a run455. On request, write the picture with `--html <file>` (a self-contained page) or `--mermaid` for documents. Bricks stack on the bricks whose outputs they read, with no limit on levels. To build the picture as a stepped pyramid, show the plan of `python tools/lego.py arrange <manifest>` and, with approval, add `--apply`; `--style grid` returns to the default. Positions change the picture only, never the wiring; report any `picture:` warnings from `check`4647## Checkpoints with the user48- Before applying a new arrangement to the picture4950## Common pitfalls51- Describing channels the manifest does not contain52- Confusing picture positions with wiring53- Ignoring stubs when interpreting results5455## Output56`(conversation); optionally lego-view.html next to the manifest`5758The explanation is given in conversation; the optional HTML page or Mermaid diagram sits next to the manifest.5960## Gate / verdict61- The description matches the tool's output; nothing is inferred beyond it62- Economic consequences of open studs are explained63- Element findings (non-square bricks, unsourced parameters, unverified constraints) are reported when declared6465## Suggested next steps66- `/lego-add`67- `/lego-detach`68- `/lego-swap`