gather_contextlisted

# gather_context Acting without reading the relevant code first is the fastest path to a wrong answer. This skill gives you a repeatable sequence for pulling enough context to work confidently — without reading the entire codebase. ## When to Use This Use this skill at the start of any task where you'll touch existing code and you don't already have: - The relevant files open in context - The project's rules and conventions - Any known facts about the area you're working in Don't use it if the user just pasted the code you need. Don't use it for explanatory questions that don't require changes. ## Step 1: Understand What You're Looking For Before searching anything, write down (mentally or literally): - What is the task? (One sentence) - What domain concepts are involved? (e.g., "sessions", "billing", "auth") - What layer are you working in? (domain, application, infrastructure, API, frontend) This shapes what you search for. Looking for "the billing code" is less useful than "the Invoice aggregate and the ChargeUseCase". ## Step 2: Read Project Rules First Always read the project's rules before reading any code. Rules encode the conventions, constraints, and architectural decisions that aren't obvious from the code alone. Fetch project rules from the workspace context. If rules exist, read them in full — they may tell you exactly where things should live and what patterns to follow. **Common rules to look for:** - Where new files go (which layer, which module) - N