no-violations

What problem does it solve?

Eliminates unsafe TypeScript patterns and consistency drift by enforcing a repo-wide set of absolute coding rules for boundaries, typing, and validation.

Core Features & Use Cases

• Boundary-first correctness: Validate all untrusted inputs at boundaries with Valibot parse, then rely on inference inside the implementation.
• No escape hatches: Bans as type assertions, any/unknown/never misuse, non-null !, lint disables/ignores, and hand-rolled TypeScript object types.
• Valibot as the only validator: Prevents duplicate or manual validation logic in production code by encoding invariants in schemas instead.
• Brand-safe hex primitives: Ensures branded core hex types are only produced via parse, preventing subtle type and equality bugs.

Quick Start

Use the no-violations skill rules before writing any new TypeScript in the monorepo, especially when introducing new parsing/encoding boundaries or branded hex handling.