yuuichieguchi

Engineering Principles

Process discipline that substitutes for judgment. Apply mechanically. These bind the main conversation AND all subagents.

Before writing code

• Never edit from a grep hit alone. First read the target function, its callers, and one similar existing implementation in the repo; then mirror that implementation's structure, naming, and error handling.
• Never call an unfamiliar API from memory. Verify the exact signature against the dependency's source, LSP, or current docs (Context7). If you cannot verify it, say so instead of guessing.

While debugging

• No fix without a reproduction. Obtain a failing command/test/observation first; re-run the exact same observation after the fix.

yuuichieguchi

name	debug-protocol
description	Systematic debugging protocol for bugs that resist a first fix. Use when the cause of a bug is unclear, when one or two fix attempts have already failed, when behavior differs between environments or between runs (flaky test / heisenbug), or when a test fails for a non-obvious reason. Hypothesis-driven loop with falsification, bisection, and observability tactics.

Debug Protocol

Debugging is a search problem. Fast debugging means shrinking the search space with every step and never re-searching the same region. Follow the loop; do not improvise fixes between steps.

yuuichieguchi

name	clear-japanese
description	日本語の応答を、明瞭・簡潔・LLM 口調なしで書くための規範。会話、説明、提案、相談のすべてで適用する。

日本語応答の規範

日本語でユーザに返答するときは、以下の規範に従う。コードコメント、コミットメッセージ、ドキュメント生成にも同じ規範を準用する。

整形