thebabush

Connect to a Blender .blend file over SQL and bootstrap a session. Use when starting work, choosing CLI vs HTTP vs the in-Blender add-on, or routing to a domain skill.

The 5.1 layered Action tree (actions → slots/layers/strips/channelbags → fcurves → keyframes), animation_data, and drivers. Use to inspect or edit keyframes, fcurves, and drivers.

The 'everything else' grab-bag — images, sounds, clips, fonts, curves, lights, cameras, armatures/bones, shape keys, vertex groups, palettes, worlds, brushes, masks, text font-curves, custom properties. Use to inspect or edit these datablocks.

Grease Pencil v3: datablocks → layer groups → layers → frames → drawings → strokes → points. Use to inspect GP, edit layer properties, delete strokes, or build new layers/frames/strokes.

Materials, GP material settings, and the unified node-tree model (node_trees/nodes/node_inputs/node_outputs/node_links/node_tree_interface). Use to inspect or edit shaders, recolor BSDFs, or build node graphs.

Meshes and their geometry — the 5.x attribute system, vertices/edges/polygons/loops/uvs. Use to inspect mesh topology or attributes. Mostly read; these are the heaviest tables on big files.

Object modifiers and constraints. Use to inspect, add, edit, or delete modifiers/constraints; query type-specific fields via params_json.

Scenes, collections, objects, the parent/child hierarchy, transforms. Use to inspect or edit objects — move/rotate/scale/parent/rename, add EMPTYs, delete objects.

Proactive code review. When the user completes a meaningful coding task or asks for a review, invoke /rrr automatically — but only if this project has opted in.

Review code changes. Run "rrr" for unstaged changes, "rrr last" for the last commit, "rrr staged" for staged changes, or with --last <N>, --since <dur>, --branch <name>, or a path. Use when asked to review uncommitted changes, staged changes, the last N commits, changes since a time window, a branch diff, or the overall project.

Find cross-references (callers, callees, data references) in native binaries using the `xr` tool. Use when reverse engineering ELF, Mach-O, PE, or dyld-cache binaries and you need to find what calls a function, what references a symbol, who reads/writes a data address, or what code a given function calls — without reaching for objdump/grep pipelines.