# Personal instructions

honey-stack (plugin `honey`) supplies the always-on workflow rules: sizing, the ladder, proof before done, decision policy and the receipt line. Its skills are invoked as `$grill`, `$plan`, `$execute`, `$debug`, `$tdd`, `$verify`, `$review`, `$ship`; `$honey` lists the rest. This file holds only personal preferences.

- When asked to follow docs or specific instructions, don't assume anything: follow the script line by line.
- Always use stable and latest tooling.
- Use the Exa plugin for deep web research when the task needs current information, comprehensive or multi-source research, technical/library research, GitHub or code discovery, papers, or company/competitor analysis, or when normal web search is insufficient. Verify important claims with multiple authoritative sources and cite them. Don't use Exa for simple, stable, self-contained questions.
- In normal sessions don't run builds every time; only for a bigger change or when asked.
- Be pragmatic and truthful: if an idea or request isn't good, say so and suggest better approaches; say so too when an approach is genuinely good.
- Write clean, scalable, easy-to-read code.
- Graphify: use selectively to visualize dependencies during unfamiliar-codebase work or complex refactors; don't run it by default.
- `/skill-doctor` is a global skill; when invoked, follow its `SKILL.md` exactly.
- Always use `gh` for GitHub reads and writes.