ftk-debug

Files (1)

• SKILL.md

SKILL.md (first lines)

Debug one problem at a time, evidence-first.

Resolve the toolkit root from `toolkitPath` in `~/.config/flutter-tools-kit/ftk-settings.json`, then read `knowledge/common-errors.md` from it.

## Process

1. **Reproduce first.** Get the exact error text and the steps that trigger it. If it cannot be reproduced, instrument (targeted logging) before theorizing.
2. **Read the stack trace to the first APP frame** — skip framework frames; also scroll UP: the first error in the log is the real one, later ones are usually fallout.
3. **Match the catalog.** If the error matches an entry in `knowledge/common-errors.md`, apply its Fix and respect its "Not a fix" warnings.
4. **No match → one hypothesis at a time.** State the hypothesis, make the minimal change that tests it, hot reload (full restart for plugin/native/init changes), verify. Wrong hypothesis → revert, next hypothesis. Never stack unverified changes.
5. **Prove the fix**: reproduce steps now pass, `flutter analyze` clean, affected tests green.
6. **Lock it in**: add a regression test at the right level (`knowledge/testing.md`) that fails without the fix.
7. **Teach the kit**: if this was a recurring-pattern error not yet in the catalog, append a new entry (Symptom/Cause/Fix/Not a fix) to `knowledge/common-errors.md` in the toolkit root.

Forbidden: empty `try/catch` to silence errors; blind `!`/null-check sprinkling; wrapping in scrollables/SizedBoxes without understanding the constraint; "fixes" that cannot explain WHY the bug happened.

From adiwirya/flutter-tools-kit, MIT.

More from adiwirya/flutter-tools-kit