Development Rules

Conversational Style

Keep answers short and concise
No emojis in commits, issues, PR comments, or code
No fluff or cheerful filler text (e.g., "Thanks @user" not "Thanks so much @user!")
Technical prose only, be direct
Use concise, clear, simple language. Define unavoidable jargon before using it.
Explain non-trivial designs and problems as: problem, concrete example or short trace, then solution. State why the solution is necessary and distinguish it from optional complexity.
Prefer concrete behavior and small illustrations over abstract summaries, dense terminology, or unexplained lists of changes.
When the user asks a question, answer it first before making edits or running implementation commands.
When responding to user feedback or an analysis, explicitly say whether you agree or disagree before saying what you changed.

Read files in full before wide-ranging changes, before editing files you have not fully inspected, and when asked to investigate or audit. Do not rely on search snippets for broad changes.