interrogate

C rules and taste for tstack (C23, GCC/Clang, sanitizers, clang-tidy, QMK keymaps).

Apple's fluid-interface principles for the web: springs, velocity handoff, momentum, rubber-banding, materials, type.

Sketch types, signatures and the module map from competing candidates before code, then implement against it.

Explain how code works, as onboarding a senior engineer.

Generate a project-local verify-<app> skill that launches the app and drives it like a user, with a feature map.

Craft rules for web UI polish (press states, origins, transforms, clip-path, gestures, performance, accessibility) and a Before/After review table.

Run N parallel attempts at one task under distinct constraints, pick a base, graft the best of the others.

Design an auditable bespoke playbook when no tuca-mode playbook fits.

Build an animation or transition that passes review-animations, or name a motion effect ("what's it called when...").

Deep-module design vocabulary (module, interface, seam, depth).

Explain a piece of work plainly (what, how, why) as one conversational account.

Find places in a UI that don't animate but should, and reject the ones that shouldn't; read-only, exact values.