file-tour

name	file-tour
description	Give a guided tour of a file or directory — explain its purpose, key contents, and anything surprising
argument-hint	<path>
allowed-tools	["Read","Glob","Grep"]

The user has asked for a guided tour of $ARGUMENTS.

Follow these steps:

1. Read the target. If it's a file, read it in full. If it's a directory, use Glob to list its contents first, then read the most important files.

2. One-sentence purpose. Start your response with a single sentence: what is this file/directory for?

3. Key contents. For a file: list the most important functions, classes, or exports with a one-line description of each. For a directory: describe the role of each subfolder or notable file.

4. Anything surprising. Note anything that would catch a new reader off guard — unusual patterns, non-obvious dependencies, TODOs, or things that look wrong but are intentional.

5. Format. Use headers and bullet points. Keep it scannable. Aim for under 30 lines total.

Do not summarize every single line — focus on what matters to someone opening this for the first time.