flow

Use when reviewing a codebase's structural organization, not a PR or branch. Triggers on: codebase audit, structural review, architecture audit, code organization review, audit this codebase, how is this repo organized, code health check, audit the code. Produces a findings report against a standard checklist plus project-specific conventions.

Use when working on multiple tickets simultaneously, dispatching parallel subagents across worktrees, or needing a CI-fix loop to get branches green. Covers worktree setup, parallel planning, implementation, PRs, tests, and CI monitoring.

Use when a task has a clear implementation plan and should be executed by a subagent in an isolated git worktree. Triggers on phrases like: dispatch this, send to a subagent, work on this in a worktree, dispatch to worktree, background task, isolated execution.

Use when the user wants to review existing work on a branch, find issues, and dispatch parallel fixes that get cherry-picked back. Triggers include: review and fix, review and fix this branch, find and fix issues, dispatch fixes, parallel fix, review then fix, fix all issues, code review with fixes.

Use when code needs repeated review-fix cycles until clean. Dispatches a reviewer agent, then a fixer agent, commits, and repeats until findings converge to zero or a cap is reached. Triggers on: iterate until clean, review fix loop, converge, repeated review, keep fixing until done, iterative review.

Use for ALL Rust questions including errors, design, patterns, and coding. Triggers on: Rust, cargo, rustc, Cargo.toml, compiler errors (E0382, E0597, E0277, E0308, E0499, E0502, E0506, E0507), ownership, borrowing, lifetimes, traits, generics, async/await, tokio, concurrency, Result, Option, Error, thiserror, anyhow, Box, Rc, Arc, RefCell, performance, profiling, clippy, code review, anti-pattern, idiomatic Rust, code style, best practice

Use after generating any visual design, frontend code, or .pen file to check for generic AI defaults. Triggers on: review design, audit design, check design quality, design review, does this look good, is this generic, AI slop, design check, visual QA, before shipping design, review my frontend, check my CSS, quality check, polish, improve design. Catches common AI aesthetic convergence patterns.

Use when building web components, pages, or applications with HTML, CSS, JavaScript, React, Vue, Svelte, or any frontend framework. Triggers on: build a page, create a component, design a UI, landing page, dashboard, settings panel, login page, signup form, pricing page, hero section, card component, navigation, sidebar, modal, frontend, web design, HTML, CSS, styled, Tailwind, web app, website. Ensures distinctive, production-grade output that avoids generic AI aesthetics.

Use BEFORE any Pencil MCP design work in .pen files. Triggers on: design, .pen, pen file, visual design, Pencil, batch_design, create a page, create a screen, design a dashboard, design a landing page, build a layout, mockup, wireframe, UI design, screen design, app design, website design. Ensures design constraints are established before any nodes are inserted.

CRITICAL: Use for unsafe Rust code review and FFI. Triggers on: unsafe, raw pointer, FFI, extern, transmute, *mut, *const, union, #[repr(C)], libc, std::ffi, MaybeUninit, NonNull, SAFETY comment, soundness, undefined behavior, UB, safe wrapper, memory layout, bindgen, cbindgen, CString, CStr

Use when building domain-specific Rust applications. Keywords: web server, HTTP, REST API, GraphQL, WebSocket, axum, actix, tower, CLI, command line, terminal, clap, TUI, ratatui, kubernetes, k8s, docker, grpc, tonic, microservice, cloud, embedded, no_std, MCU, ARM, firmware, embassy, RTIC, fintech, trading, decimal, currency, financial, ledger, IoT, sensor, MQTT, edge computing, machine learning, ML, AI, tensor, model, inference, candle, burn

Use for Rust code analysis via LSP. Keywords: symbols, project structure, list structs, list traits, list functions, trait implementations, find implementations, go to definition, find references, call hierarchy, call graph, dependency graph, visualize deps, refactor, rename symbol, move function, extract function

Use when working with diecut templates. Triggers include scaffolding projects, creating projects from templates, building template repositories, configuring template variables, adding conditional files, setting up hooks, or when editing diecut.toml files.