byte-code-ruleslisted

# Byte Code Rules This is the Byte OS engineering guardrail layer. It adapts the MIT-licensed Karpathy-inspired coding guidelines from `forrestchang/andrej-karpathy-skills` into the Your ByteDance workflow. ## Core Rules 1. Think before coding. - Inspect the relevant project files before editing. - State assumptions only when they affect the implementation or product decision. - If multiple interpretations would produce different code, ask or present the tradeoff before committing. - Push back when a simpler or safer approach better serves the product goal. 2. Simplicity first. - Build the smallest thing that satisfies the plan, acceptance criteria, and user request. - Do not add speculative features, generic frameworks, unused configuration, or single-use abstractions. - If the implementation becomes much larger than the problem, simplify before continuing. - Prefer existing project patterns, dependencies, and local helpers. 3. Surgical changes. - Keep every changed line traceable to the user request, current plan, or verification need. - Match the surrounding style instead of restyling adjacent code. - Do not refactor, reformat, rename, or delete unrelated code. - Clean up only unused imports, variables, files, or comments created by the current change. - Mention unrelated dead code or design debt in logs or review notes instead of silently removing it. 4. Goal-driven execution. - Turn each coding task into concrete success cr