intent-engineering

intent-engineering lens for framework architecture (Rails today). Detects structural anti-patterns (fat models, God objects, fat controllers, misused service objects, callback hell), classifies design-pattern instances against a catalog, raises unidentified patterns, and enforces the project's allow/block/approved pattern policy. Heuristic-first; optionally enriched by reek/flog/brakeman when installed.

intent-engineering lens. Reviews code and plans for convention adherence — reinvented conventions, config where convention exists, non-idiomatic structure/naming, and one-off patterns that fight the repo or framework. Reads repo CLAUDE.md/AGENTS.md FIRST; local conventions override community defaults.

intent-engineering lens for user-facing surfaces. Reviews UI/UX code and plans for missing interaction states, inconsistent look-and-feel, broken keyboard/focus/back-button, accessibility gaps, weak information architecture, and AI-slop design (HIG, look-and-feel, UX).

Always-on intent-engineering lens. Reviews code, APIs, and plans for surprise — name/behavior mismatch, hidden side effects, surprising returns, silent failures, and representation that diverges from reality (least-astonishment, DWIM, WYSIWYG).

Always-on intent-engineering lens. Reviews code and plans for needless complexity — abstractions with one use, speculative generality, knobs nobody sets, layers that don't earn their keep (Occam, KISS, YAGNI). Guards the flip side: doesn't oversimplify away real requirements.

Audit a whole codebase, subsystem, or feature against the intent-engineering lenses (predictability, convention, simplicity, experience, and architecture on supported frameworks) and produce a posture report — per-dimension 0-10 scores plus the top surprise/convention/complexity/UX/structural gaps. Use to assess an existing codebase or area, not a specific diff. Sampling-aware for large targets.

Scaffold Intent Engineering project config into a repo's .intense/ directory — ways-of-working, pattern policy (allow/block/approved), and architecture thresholds — so the team can tune the lenses and commit the settings. Stack-aware menu; idempotent (never clobbers existing config without confirmation). Use to set up or extend a project's .intense/ config.

Inject intent-engineering principles into the planning phase — surface the least-astonishment, convention, simplicity, and UX considerations relevant to the work being planned, as a tailored advisory checklist. Lightweight and non-blocking; use while drafting a plan or thinking through an approach, before a full plan doc exists. For validating a finished plan, use ie-validate-plan instead.

Review code changes through the intent-engineering lenses (predictability, convention, simplicity, experience, and architecture on supported frameworks) — surfacing surprise, non-idiomatic patterns, needless complexity, UX gaps, and structural anti-patterns. Default (interactive) mode applies safe, verified fixes and commits on a clean tree (never pushes); mode:agent reports JSON only. Use on a PR, branch, or local changes before merging.

Validate a plan, spec, or requirements document against the four intent-engineering lenses before implementation — surfacing surprising designs, non-idiomatic or reinvented approaches, needless complexity/scope, and missing UX decisions (states, flows, IA, accessibility). Returns dimensional 0-10 ratings and the gaps to resolve first. Use when a plan or spec doc exists.