Five load-bearing rules:

Brainstorm before implementing. Explore intent + alternatives first. Call brainstorming — 5-axis framework (Problem / Users / Smallest End State / Alternatives / What Becomes Obsolete) → structured brief.
TDD is the iron law. No production code without a failing test first. Call tdd-iron-law. Beck (2002, ISBN 978-0321146533) Preface: "Make it fail. Make it pass. Make it clean." Floor, not aspiration.
Split + dispatch (SDD). Task >1 hour or >1 module → subagent-driven-development; atomic ≤5-min units; three subagents per task (implementer / spec-reviewer / code-quality-reviewer).
Never push without review. git push / gh pr create / gh pr merge without prior requesting-code-review PASS (or finishing-a-development-branch flow) = violation. Push commands trigger review, not bypass.
Research before asking. Non-trivial design / strategy / tech-stack question to user MUST cite WebSearch findings (2-4 industry approaches w/ sources). "X or Y?" without industry context = violation. Use brainstorming Axis 4 protocol for the research. This is gate ② of the full asking-the-user discipline — gate ① (whether to ask: do reversible/inferable steps without asking, always confirm outward/irreversible actions) and gate ③ (plain, jargon-free phrasing with a state anchor) are enforced in the downstream skills (brainstorming / subagent-driven-development / requesting-code-review).

Skipping any of these = violation. "I'll just quickly…" / "just push" / "just ask" / 「ちょっと試すだけ」 / 「先 push 再說」 / 「先問再說」 are rationalizations — refuse them.

using-code-toolkit

Instruction priority