# Explore Structure First

> explore-structure-first

- Skill: `claudiawong522/explore-structure-first` (Agent Skill)
- Install (CLI): `npx skillmds@latest add claudiawong522/explore-structure-first`
- Raw SKILL.md: https://api.skillmd.com/api/skills/claudiawong522/explore-structure-first/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: claudiawong522 (https://skillmd.com/u/claudiawong522)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/claudiawong522/explore-structure-first

---

# explore-structure-first

Map out your project's directory structure before asking for help to clarify scope and available resources.

# Explore Structure First

When you need help understanding or working with a codebase, start by mapping the project structure rather than jumping straight to vague requests.

## Why This Matters
- **Clarifies scope**: You'll see what files and directories exist before asking questions
- **Saves time**: You won't need follow-up questions about what resources are available
- **Provides context**: The assistant can give better help when they know the actual structure

## Steps

1. **Run a directory exploration first**
   - Use `find`, `tree`, or your file explorer to see the project layout
   - Focus on top-level directories and key files

2. **Identify the most relevant areas**
   - Note which directories contain source code, configs, tests, docs, etc.
   - Understand the project's organization

3. **Then ask your specific question**
   - Reference the actual files/directories you found
   - Be specific: "I see a `src/` directory with X and Y components. I need help with..."
   - Instead of: "Can you understand my codebase?"

## Example
❌ **Vague**: "Can you review my project code?"  
✅ **Better**: "I explored my project and found `/src` (React components), `/api` (backend routes), and `/tests`. I need help refactoring the authentication flow in `/src/auth`."