dotfiles

Code review using Git

Code review using Jujutsu

Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when you have a spec or requirements for a multi-step task, before touching code

Convert plan to actionable structured PRDs

Ultra-compressed communication mode. Distills AI output to its core — ~65% fewer tokens while keeping full technical accuracy. Use when user says "caveman", "terse", "kurz", "kurz&knapp", "kurz bitte", "less tokens", "weniger text", or invokes /caveman-distillate.

Rust LLM Coding Standard. Use when writing, refactoring, or reviewing Rust code to ensure idiomatic, safe, and maintainable outputs aligned with Rust community standards.

Ask AI's opinion on code - identify improvements, code smells, anti-patterns, and quality issues. Suggest fixes in structured format with Problem/Solution/Why triplets. Read-only, makes no changes.

Use when creating or developing a feature, this contains a focused instructions for building features.

Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.

Uses the jj (Jujutsu) version control system. Use when asked about jj commands, git push/fetch workflow, or rebasing onto main for non git repo

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior