help

Files (1)

• SKILL.md

SKILL.md (first lines)

# Help

**Answer the question in full.** Size the answer to the question, never to what you read.

**Typed with no question** → the user is asking what to do now → `/flow:start`.

## Where the answer is

- **How Flow works, or how to do something in it** → `~/.flow/repos/flow/docs/`: `reference/` for a command, a setting, a file or a skill, and `spec/product.md`, which indexes what each part does. Where no page covers it → Flow's code in `~/.flow/repos/flow/`: `skills/` for a skill, `scripts/` for a command or a hook.
- **Something failed or acts wrong** → `flow doctor` first. Then `~/.flow/logs/failures/<year>-<month>.jsonl` for a failed command, hook or plugin, and `~/.flow/logs/install.log` for a failed install. Then the code.
- **How this computer or project is set up** → `flow settings ls`, `flow skills ls`, `flow next`, the ticket.
- **Claude Code itself**: a setting, a key, a hook, a built-in command → `/flow:research`.
- **A bug in the project's own code** → say so, and point to `/flow:debug`.

## The answer

- **End on the page that covers it**, for reading more: `docs/reference/commands.md` → `### flow sync`.
- **Answered from the code** → say no page covers it, and name the file.
- **A fix that changes anything**: a setting, a sync, a skill switched → propose it. Run it on the user's yes.

From Adrian333Dev/flow, MIT.

More from Adrian333Dev/flow