Set up a repo for autopilot. Works out how to boot, seed, log in to and check the app, writes .claude/autopilot.json, and proves it by booting the app once. Run once per repo before /autopilot:run, or when the app's dev setup changes.
Deliver an approved plan end to end as the staff engineer. Validates the plan file, decides the cross-unit approach, writes each unit's contract and QA personas, then starts the deliver workflow, which runs engineer, review, persona QA and verification per…
Gate-based code review for a PR, branch, or set of changes in any repo. Gathers the diff and checks its scope, dispatches one gate agent per convention topic (naming, clarity, structure, simplicity, datetime, react, i18n, testing, correctness) plus a…
Readability conventions for TypeScript, JavaScript and other source files: ternary shape, guard clauses, comments, casts and type escape hatches, magic numbers, fallback chains, dense expressions and over-extraction. Use when writing or reviewing code that…
Correctness conventions for source files in TypeScript, JavaScript, Ruby, Python, Swift, Go, Java, Kotlin, PHP, C# and Rust: logic errors (off-by-one, wrong operator, inverted condition, stale state or closure, wrong dependency array), unhandled edge cases…
Naming conventions for identifiers and file names in TypeScript, JavaScript, Ruby, Python, Swift, Go, Java, Kotlin, PHP, C# and Rust source files: role-not-type names, verb-led function names, named boolean operands, honest names, names unambiguous at the use…
React conventions for .tsx and .jsx components, hooks and API modules: component and markup structure, keys, conditional rendering, data-fetching hooks and cache updates, forms as the source of truth, state placement, memoization, render cost, layout at…
DRY, YAGNI and KISS conventions for TypeScript, JavaScript and other source files: reuse before writing, search for an existing capability first, delete or collapse what adds nothing, numeric coercion, types as narrow as their consumers, refactor leftovers,…