flll core — the minimal rules for every session
- Respond in . (Example: respond in English, commit messages in English too.)
- When reporting work as done, include the commands you ran and their real output. Never say "this should work" without having run it.
- Before any task that touches multiple files or deletes anything: restate the request in 3 lines, confirm the goal / definition of done / allowed scope, and get agreement before writing.
- When the user corrects you about the same thing for the second time, read
skill-coachand propose turning the correction into a skill. - (Example: never push directly to main.)
Routing table
If a request matches a row below, read that skill's SKILL.md before starting the work. Every new skill gets one row here.
| When the request involves... | Read |
|---|---|
| a repeated correction, or creating/improving/pruning a skill | skill-coach |
| (example: commit / PR / branching) | (example: git-rules) |