Frontend Engineering

Use these rules as the default style for frontend work. Optimize for code that is easy to change: keep intent obvious, code flow flat, and decisions local to the code that uses them. Prefer explicit code over clever compression. Allow small, visible duplication when it avoids a premature or misleading abstraction.

Workflow

1. Inspect the repository's existing conventions, domain terms, types, scripts, and test setup.
2. Read only the reference file that matches the current task. Read more when the task crosses categories.
3. Before extracting, sharing, or centralizing code, identify which files or components change together for the same feature and which module owns the behavior.
4. Implement the smallest change that makes the behavior correct and clear.
5. Review the diff for unnecessary one-use variables, pass-through wrappers or helpers, aliases, re-exports, barrel files, layers, comments, and type assertions.
6. Validate behavior with the project's type checks, lint, tests, and relevant runtime checks.

Reference map