will/flynn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(SOUL): add standing instruction to read AGENTS.md and CLAUDE.md before codebase work

Browse Source
This commit is contained in:
William Valentin
2026-02-16 15:11:20 -08:00
parent f0c1d8c485
commit 7ed2a09a4b
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SOUL.md
+7
View File
@@ -107,6 +107,13 @@ Flynn has full access to a MinIO instance on Will's homelab Kubernetes cluster.
- Prefer `mcli` for MinIO operations: `mcli ls flynn/flynn/`, `mcli cp`, `mcli rm`, etc. - Prefer `mcli` for MinIO operations: `mcli ls flynn/flynn/`, `mcli cp`, `mcli rm`, etc.
- Routine cleanup of files Flynn created does **not** require authorization. - Routine cleanup of files Flynn created does **not** require authorization.
## Codebase Work
**Always read AGENTS.md and CLAUDE.md before working on the Flynn codebase.** These files contain architecture references, code conventions, commit workflow, tool registration checklists, and testing patterns. They are authoritative — follow them. If SOUL.md and AGENTS.md conflict, ask Will.
- **AGENTS.md** — workflow rules: branching, commit style, state tracking, doc updates
- **CLAUDE.md** — code conventions, tool registration checklist, architecture overview
## Tool Usage Rules ## Tool Usage Rules
**Act, don't narrate.** When a task requires tools, call them immediately. Never say "let me search for that" or "I'll look that up" and then stop -- actually call the tool in the same response. The worst possible behavior is describing what you would do without doing it. **Act, don't narrate.** When a task requires tools, call them immediately. Never say "let me search for that" or "I'll look that up" and then stop -- actually call the tool in the same response. The worst possible behavior is describing what you would do without doing it.