Skip to main content
MonoCSS is a CSS-architecture audit orchestrator over Monogram. It gathers static evidence about import order, !important debt, token coupling, raw colors, scrollbar ownership, and runtime inline-style bypasses, then tells the reviewer which claims still need live DOM geometry. Published contract: monocss 0.15.0, OpenCLIs build 2026-05-27-232227. The executing binary, OpenCLIs registry, and public CDN metadata agree on this release. Registry ownership: the canonical docs_url is this page, the public product homepage is https://monolex.ai, and MonoCSS pairs with Monogram for source proof, MonoSurf or Kernel CLI for runtime DOM proof, and Monoflow for temporal context. Repository ownership remains monolex/monolex; no public source URL is advertised while that repository is private.
Version 0.15.0 has root help, but no per-command help parser. Use bare monocss, monocss help, or root monocss --help. audit --help is an unknown audit option, summarize --help treats --help as an audit directory, and status --help still runs the status probe.

Quick Start

Read the generated SUMMARY.md first. Raw artifacts are supporting evidence, not the required starting point.

Complete Command Reference

Audit Artifacts

An audit run writes 00-monogram-stats.txt, then one raw artifact for each probe in registry order. Version 0.15.0 has 32 probes: The default output root is .niia/monocss-audit/<timestamp>.
The compact Writes section embedded in the installed 0.15.0 guide stops at artifact 06. The runtime registry and normalized report contain all 32 probes listed above; this public page records the complete release behavior.

Normalized Report Contract

With audit --json, stdout contains the same report written to monocss-report.json: Each finding carries id, artifact, executed command, success, headline, extra_lines, probe-specific metrics, report sections, and an optional dom_proof request. A raw subprocess artifact is evidence; the finding is the stable machine-facing interpretation.

Remediation Plan Thresholds

monocss plan <audit-dir> reads the normalized metrics and emits advice only. It never edits CSS. Version 0.15.0 gates these plan items: Thresholds are prioritization policy, not proof that a finding is safe to fix. Every suggested change must be re-audited and, where requested, verified in the live DOM.

Static and Runtime Proof Boundary

prove scrollbar explicitly asks for scrollbarGutter, left/right padding, clientWidth, offsetWidth, first-child edge gaps, overflow ownership, and inline-style ownership. A clean static trace cannot prove those live values. Use MonoSurf for browser DOM evidence, or the appropriate Tauri runtime inspector for application-only surfaces.