coding-standards

Apply a rule set covering anti-pattern bans, strict typing, and a pre-delivery gate running Biome checks, type checking, and tests. This skill encodes those rules with concrete bad/good examples so violations are caught during code review or generation.

Key anti-patterns include unbounded in-memory maps without TTL, secrets in URL query parameters, non-idempotent write endpoints, silent error swallowing, N+1 query loops, and wildcard event subscriptions. Each causes memory leaks, credential leaks, duplicate writes, or message storms.

Include a sender ID in message envelopes and filter out self-emitted events, or segregate ingest channels from broadcast channels. Publishers must never process their own events without explicit loopback deduplication.

Yes, the anti-pattern invariants apply universally across languages, frameworks, and transport protocols including REST, WebSockets, Pub/Sub, and gRPC. Language-specific rules like zero `any` and union literals target TypeScript specifically.

The standard bans `class`, `this`, and `constructor` in favor of pure functions, closures, and factory functions. This reduces hidden state, simplifies testing, and makes dependencies explicit through function parameters rather than implicit instance state.