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.