coding-guidelines

Prohibits ad-hoc mutable stateful objects and enforces stateless functions or established patterns (Factory/Builder) when state is unavoidable. Use when designing data structures or reviewing code that introduces new class instances or mutable singletons. Do not use to prohibit all state — only uncontrolled, arbitrarily created mutable objects.

Prohibits Tailwind arbitrary values (e.g. w-[17px]) to enforce design system token consistency. Use when writing or reviewing Tailwind class lists. Do not use when a value is intentionally one-off and cannot be expressed by any existing token (e.g. a pixel-perfect third-party embed constraint).

Minimizes reliance on full component mount tests by extracting testable logic and mocking child components when rendering is necessary. Use when writing tests for frontend components. Do not use to prohibit all rendering tests — snapshot or integration tests for critical UI flows are still acceptable with justification.

Prohibits package-level mutable variables and init() functions for state management in Go, enforcing dependency injection instead. Use when writing or reviewing Go packages that need configuration or shared resources. Do not use for package-level constants or type registrations that are genuinely immutable.

Prevents N+1 query problems by enforcing eager loading (JOINs) or query batching when fetching related data. Use when writing or reviewing code that fetches a list and then queries related data per item. Do not use when the secondary queries are intentionally lazy-loaded for performance reasons and the number of items is provably small.