explore-before-acting
Systematically explore and document your target environment's structure and documentation before executing commands or awaiting further instructions.
Overview
Before diving into tasks or executing commands in an unfamiliar environment, invest time in understanding the system architecture, available tools, and project structure. This upfront exploration enables better decision-making and prevents missteps.
Steps
Navigate to the root or main project directory
- Identify the entry point of the environment you're working with
Search for and read documentation files
- Look for:
README.md, CLAUDE.md, ARCHITECTURE.md, .md files, or similar
- These files typically explain the system's purpose, structure, and available tools
Explore the directory structure
- List subdirectories and their contents
- Identify key folders: source code, documentation, config, tests, etc.
- Understand the organizational hierarchy
Document your findings
- Note the system's purpose and main components
- List available tools, commands, or APIs
- Identify any setup requirements or dependencies
- Record the location of important files
Await or plan your next steps
- You now have informed context for decision-making
- Follow instructions with better understanding, or proactively suggest approaches based on the architecture you've discovered
Tips
- Many projects include hidden gems in documentation files—don't skip this step
- Use
ls -la or file tree commands to see all contents including hidden files
- Pay special attention to any files named after the project or system (they often contain crucial information)
- This exploration typically takes 2-5 minutes but saves significantly more time later
1---2name: explore-before-acting3description: explore-before-acting4---5# explore-before-acting67Systematically explore and document your target environment's structure and documentation before executing commands or awaiting further instructions.89## Overview10Before diving into tasks or executing commands in an unfamiliar environment, invest time in understanding the system architecture, available tools, and project structure. This upfront exploration enables better decision-making and prevents missteps.1112## Steps13141. **Navigate to the root or main project directory**15 - Identify the entry point of the environment you're working with16172. **Search for and read documentation files**18 - Look for: `README.md`, `CLAUDE.md`, `ARCHITECTURE.md`, `.md` files, or similar19 - These files typically explain the system's purpose, structure, and available tools20213. **Explore the directory structure**22 - List subdirectories and their contents23 - Identify key folders: source code, documentation, config, tests, etc.24 - Understand the organizational hierarchy25264. **Document your findings**27 - Note the system's purpose and main components28 - List available tools, commands, or APIs29 - Identify any setup requirements or dependencies30 - Record the location of important files31325. **Await or plan your next steps**33 - You now have informed context for decision-making34 - Follow instructions with better understanding, or proactively suggest approaches based on the architecture you've discovered3536## Tips37- Many projects include hidden gems in documentation files—don't skip this step38- Use `ls -la` or file tree commands to see all contents including hidden files39- Pay special attention to any files named after the project or system (they often contain crucial information)40- This exploration typically takes 2-5 minutes but saves significantly more time later
claudiawong522