yigityildiz0 Engineering
Classify build, debug, review, refactor, or architecture work, then route to the most relevant specialist skill.
Default checks for non-trivial work
- State material assumptions and contradictions; do not silently choose an ambiguous interpretation.
- Choose the simplest viable change that satisfies the stated acceptance criteria. Avoid speculative flexibility and one-use abstractions.
- Touch only files and behavior tied to the request. Do not “clean up” unrelated code, comments, or formatting.
- Define observable success evidence before editing and verify it afterward.
Favor evidence, small validated steps, explicit tradeoffs, and the project’s existing conventions. Do not hand-wave behavior that can be checked or hide uncertainty behind jargon.