en un clic
orient
Use when entering unfamiliar code to map both breadth (peer modules, callers, dependencies, cross-cutting concerns) and depth (architecture down to critical implementation details), in the project's domain vocabulary.
Menu
Use when entering unfamiliar code to map both breadth (peer modules, callers, dependencies, cross-cutting concerns) and depth (architecture down to critical implementation details), in the project's domain vocabulary.
Use when posting validated code review findings as GitHub PR line-level comments or a GitHub PR review after completing a review.
Use when reviewing branch or PR changes against a base branch for correctness, security, concurrency, architecture, maintainability, testing, and performance risks.
Applies Karl Popper’s critical rationalism to software engineering, programming, and product building by treating requirements, designs, implementations, and product ideas as falsifiable hypotheses. Emphasizes conjectures and refutations, explicit assumptions, fast error discovery, small risky experiments, observable failure signals, reversible designs, and iterative elimination of mistakes.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design.
Baseline coding behavior. Use before writing, reviewing, debugging, or refactoring code. Establishes ground rules for assumptions, simplicity, surgical edits, and verification.
Generate or check Codex CLI .codex-plugin/plugin.json and Gemini CLI gemini-extension.json manifests from a Claude Code .claude-plugin/plugin.json source manifest. Use when maintaining one plugin across Claude Code, Codex CLI, and Gemini CLI, syncing plugin metadata, preserving platform-specific manifest fields, or validating cross-platform plugin manifests before release.
| name | orient |
| description | Use when entering unfamiliar code to map both breadth (peer modules, callers, dependencies, cross-cutting concerns) and depth (architecture down to critical implementation details), in the project's domain vocabulary. |
| disable-model-invocation | true |
I'm unfamiliar with this code. Map it across two axes:
Use the project's domain vocabulary. Cite file:line. Flag where to start and what I can safely defer.