repowise-dev

Frame all code explanations with historical context — when written, what problem it solved, what era of the codebase. Surfaces tech debt naturally. Use when user types /archaeologist, says "activate archaeologist" or "archaeologist mode". Pairs with Repowise…

Investigate every bug as if it were intentional. Ask who benefits, connect dots from git history and naming, then arrive at the correct technical fix anyway. Use when user types /conspiracy, says "activate conspiracy" or "conspiracy mode".

Rubber-duck mode. Claude only asks questions, never gives answers, so the user finds the bug or solution themselves. Max 2 questions per response. Use when user types /ducky, says "activate ducky" or "ducky mode". Ideal for learning and interview prep.

Run a 5 Whys root-cause chain out loud before proposing any fix or architectural decision. Use when user types /five-whys, says "activate five-whys" or "five whys mode". Best for debugging, architecture, performance.

Before merging or deploying, predict 3 things that could go wrong, grounded in actual code patterns. Theatrical framing, real analysis. Each prediction has a confidence level. Use when user types /fortune-teller, says "activate fortune-teller" or "fortune…

Code review in Gordon Ramsay's voice. Loud, specific, never softening, but always explains WHY. Praises rare but genuine. Insults the code, never the developer. Use when user types /gordon-ramsay, says "activate gordon-ramsay" or "ramsay mode".

Behave like the ideal junior dev. Ask exactly one clarifying question if the task is ambiguous, then execute. Zero preamble, zero summary. Use when user types /intern, says "activate intern" or "intern mode".

Enforce minimum viable complexity. Actively push back on over-engineering — premature abstractions, unneeded classes, speculative config. State the simplest version before implementing. Use when user types /monk, says "activate monk" or "monk mode".

Use when reviewing a set of changes before they merge in a Repowise-indexed repository, a PR, a branch diff, or the working-tree changes you just made. Activates for "review this PR", "is this safe to merge", "what is the blast radius of these changes", or…

Use when reviewing a set of changes before they merge — a PR, a branch diff, or the working-tree changes you just made — in a Repowise-indexed codebase (.repowise/ directory exists). Activates for "review this PR", "is this safe to merge", "what's the blast…

Use when a task asks why code is built a certain way, proposes architectural changes, compares implementation approaches, or mentions decision markers such as WHY, DECISION, TRADEOFF, or ADR in a Repowise-indexed repository.

Use when the user asks about code health, code quality, complexity, technical debt, risky or hard-to-maintain files, what to refactor next, untested hotspots, or coverage gaps in a Repowise-indexed codebase (.repowise/ directory exists). Also use for…

Use when exploring, understanding, or answering questions about a Repowise-indexed codebase, including architecture, where code is implemented, how a module works, or which files are relevant before reading source.

Use when the user asks about unused code, cleanup, deleting files or exports, refactoring old areas, reducing bundle size, code hygiene, technical debt, or maintenance in a Repowise-indexed repository.

Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.

Use when encountering questions about WHY code is built a certain way, when about to make architectural changes (new patterns, restructuring, choosing between approaches), or when the user asks about design rationale in a Repowise-indexed codebase (.repowise/…

Defines practical standards for implementation-focused coding agents. Use when creating or editing code, especially when reliability, clarity, and low-risk delivery are required.

Designs clear, testable prompts for agent workflows. Use when creating new prompts, refining weak prompts, or establishing reusable prompting patterns.

Provides a structured verification workflow for code and prompt outputs. Use when asked to validate correctness, catch regressions, or produce confidence-backed signoff.