Use the Sensez MCP server when checking a codebase for structural duplication, dead code candidates, circular imports, boundary violations, or design smells. Use it after you have completed a full edit turn to verify that newly written code is structurally correct. You can also use it on user triggers: "find duplicate code", "audit this project", "check dead code", "detect cycles", "enforce boundaries", "run Sensez", or "check this change". Not for per-file lint/type issues; use the language's linter and type-checker for those.
2026-07-14
