Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Guidelines for systematically exploring and understanding directory structures.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-08 | ✗→✓ | ▲ Improved | 146% | 0% |
| case-02 | ✓→✓ | = Same ✓ | 23% | 0% |
| case-03 | ✓→✓ | = Same ✓ | 90% | 0% |
| case-04 | ✓→✓ | = Same ✓ | 31% | 0% |
| case-05 | ✓→✓ | = Same ✓ | 113% | 0% |
When you are asked to explore, understand, or map a project's file structure. This includes requests like "what is this project?", "show me the structure", or "help me find where X is".
Always begin by listing the top-level directory. The root reveals the project type faster than anything else:
README.md or README.rst → start here, it's the author's own summaryrequirements.txt, pyproject.toml, package.json → tells you the language and dependenciesDockerfile, docker-compose.yml → the project is containerizedMakefile, justfile → there are predefined commands to run.env.example → environment variables are needed; never read .env itselfList all top-level directories before diving into any single one. Build a mental map:
src/ or app/ → application code lives heretests/ or test/ → test suiteconfig/ or conf/ → configurationdocs/ → documentationscripts/ or bin/ → utility scriptsmigrations/ or alembic/ → database migrationsDon't read every file. Choose what to read based on what you're trying to answer:
src/ recursivelyutils.py could contain anything.env files — they may contain secretsnode_modules/, __pycache__/, .git/, or other generated directories__main__.py or if __name__ == "__main__" block indicates an entry pointapp.py, main.py, or server.py is usually the entry point__init__.py files in Python indicate a package; they may re-export key symbols.gitignore, .flake8, .pre-commit-config.yaml) reveal tooling choicesOther measured skills in the registry, with their headline benchmark lift.