Rerun Blueprint
Change how the Rerun viewer looks by writing a blueprint, for a recording or for a table.
Install
npx skills add rerun-io/rerun --skill rerun-blueprint -g -a claude-code -y- Repository
- rerun-io/rerun11.7k
- Category
- Design
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Change how the Rerun viewer looks by writing a blueprint, for a recording or for a table. Read this whenever asked to change the look of the viewer, such as laying out a recording or dataset, designing a default blueprint, deciding which views show which entities, or making a segment or catalog table look nice by hiding columns, changing column order or filtering rows. Covers archetype-to-view mapping, layout reasoning, the rrb construction API, the contents grammar, table blueprints, and the screenshot loop.
Rerun blueprint
To change how the viewer looks, change the blueprint. This holds for a
recording's layout, views and their properties, and for a table's columns, row
filters and cards. Don't click through the viewer's menus to do it. With the
viewer MCP, read and write the blueprint with rerun_get_blueprint and
rerun_set_blueprint rather than the low-level click tools.
A blueprint decides how a recording is shown, and the recording decides what exists.
Read the data, design a first layout, then verify state before assessing screenshots until it reads at a glance.
The constructors are discoverable (dir(rrb),
help(rrb.Spatial3DView)); this skill covers what you can't guess. Import as
import rerun.blueprint as rrb.
