semantics

What problem does it solve?

It prevents semantic drift by ensuring names and signals in code, APIs, versions, tokens, UI labels, and typed concepts consistently encode the meaning they claim to represent.

Core Features & Use Cases

• Semantic naming audits: identify ambiguous, misleading, overly generic, or weasel-suffix identifiers (functions, variables, fields, files, database columns).
• Compatibility signaling: apply SemVer and Conventional Commits rules so version bumps and commit types match the real impact of changes.
• Contract correctness across surfaces: review HTTP status semantics, semantic design-token architecture, and semantic UI signifiers (including the never-color-alone rule).
• Typed semantic boundaries: use branded/semantic types and parse-don’t-validate guidance to avoid illegal states and meaning-mixing (e.g., IDs, money, email).
• Anti-pattern detection: catch cases where syntax is valid but the encoded meaning is wrong (e.g., misleading “200 with error body”, appearance-based token naming).

Quick Start

Ask an agent to audit your change for semantic correctness by checking naming truthfulness, version/commit impact alignment, and HTTP/status-token/UI signal meaning consistency.