akarachen/global
Eric's always-on working rules: finding the right repository, issue and sub-issue hygiene, open-source conduct, and plan grilling.
Stress-test product, technical, and domain-modeling plans. Use when the user asks to grill, challenge, or sharpen a plan, especially when terminology, boundaries, or assumptions are unclear.
Keep one outcome per issue and organize independently deliverable parts as sub-issues. Use when creating or splitting GitHub issues, linking or detaching sub-issues and dependencies with gh, or reading back issue hierarchy.
Minimize maintainer disturbance when contributing to open-source projects Eric does not lead.
Find the right repository before working. Check ~/Developer first, then GitHub personal repos, then organization repos. Clone into Developer by default, or /tmp when the user says it is one-off.