reverse-engineer

---

name: reverse-engineer description: reverse engineering the codebase to answer user's question. Use this skill whenever a user submits a question.

The capabilities section describes additional capabilities that you can refer to.

When you need specific examples to understand how to apply the question investigation approach, load the relevant example file from the examples folder:

• "How" Questions: When investigating implementation mechanisms and processes (e.g., "How does authentication work?", "How is data persisted?"), read examples/how-questions.md
• "What" Questions: When investigating functionality or structure (e.g., "What components handle routing?", "What data structures are used?"), read examples/what-questions.md
• "Why" Questions: When investigating design rationale and decisions (e.g., "Why was this pattern chosen?", "Why does this behavior exist?"), read examples/why-questions.md
• "Where" Questions: When investigating code location and organization (e.g., "Where is error handling implemented?", "Where are types defined?"), read examples/where-questions.md

Only load example files when they are directly relevant to the current question type to minimize context size.

The rules section outlines decision criteria that determine which capabilities to apply based on the current context and user inputs.

When the user submits a question, always apply the defining-question capability first to clarify and structure it. Do not proceed with investigation until you have a clear understanding of what the user is asking.

After defining the question, apply the reverse-engineering capability to systematically investigate the codebase. Use appropriate search strategies based on the question type and available information.

Throughout the investigation, gather enough context to provide a comprehensive answer. Don't stop after finding partial information—continue until you can fully address all aspects of the question.

Always apply the answer-presentation capability when presenting your findings. Structure the answer clearly, include specific code references, and validate completeness before responding.

Do not change any code or suggest modifications unless the user explicitly asks for recommendations or improvements. This skill is for investigation and explanation only.

If the investigation reveals that the question cannot be fully answered due to missing code, unclear implementation, or ambiguous design, clearly state what you found and what remains unclear. Offer to investigate related areas or suggest how the user might find the missing information.

When presenting code references, always use proper markdown file links with line numbers (e.g., ComponentName.tsx) for easy navigation.

If during investigation you discover multiple possible interpretations of the question, present all relevant findings and let the user clarify which aspect they're most interested in.

Wait for the user's response before proceeding when clarifying questions are asked. Do not make assumptions and continue without confirmation.