The skills Triumph is actually using.

Explains a query's plan in plain English, identifies the expensive bits (usually an implicit scan on `AttributeValue`), and rewrites it if it can do so without changing results. Pairs well with the new `PersonAliasHistorical` indexes.

Scaffolds the full Rock block stack — C# block class, Obsidian view, SCSS, block settings, and a skeleton test — from a single description. Understands the Rock 17 block conventions and fills in the boring parts so you can focus on the interesting logic. Works against any plugin with a standard `src/` layout and will match your existing naming style (PascalCase blocks, kebab-case folders, etc.) by reading two neighbors before generating anything new.

Instead of 'here's every Lava filter', this one asks what you're trying to do and returns 2-3 idiomatic snippets from real Rock templates. Examples are pinned to the Rock version you're on so they don't drift.

Walks a Rock plugin, bumps the target framework + Rock package references, and rewrites the well-known breaking changes (attribute matrix API, new block settings shape, the Lava engine swap). Leaves a comment on anything that looks risky but needs a human eye.

Walks a Lava template step by step, showing what's in scope at each point and why a filter or tag didn't match. Handles the common 'capture inside a for-loop' footgun and the less common 'child workflow attribute shadows the parent'.

Converts a ministry-side description ('when a new visitor registers, notify their campus pastor and follow up in 2 weeks') into a real Rock workflow — activities, actions, attribute plumbing, and post-back wiring. Skips the boilerplate and flags decisions it had to guess.