Plain language, not linter configs
A rule is a sentence your team already says in review: “HTTP calls go through our internal client — it handles retry, timeout and tracing.” If a senior reviewer can judge it on a diff, Normik can enforce it. No AST, no custom DSL.
Scoped, tagged, versioned
Each rule carries glob scopes (src/**, apps/api/**), free-form tags for filtering, a severity (info, warning, error), and a 10-version history with one-click restore. Your standards evolve without losing their trail.
Global rules, client workspaces
Organization-wide rules apply everywhere; workspace rules add client- or project-specific conventions on top. Agencies keep one playbook per client without duplicating the common base.
Bootstrap from the code you already have
Starting from zero is the hard part. Point your coding agent at the repo and Normik derives a first set of specific, verifiable rules from your existing conventions — delivered to a review queue, never auto-activated.
Export for agents without MCP
One click generates an AGENTS.md or CLAUDE.md from your active rules, so even tools that don't speak MCP ship with your standards in their context.
Governed, not scattered
AI-proposed rules are always flagged and wait for human approval. Every change lands in the audit log: who created, edited, approved or deleted what, and when.