ui-spec-linter

UI spec linting prevents inconsistent specifications from turning into implementation defects by checking cross-file completeness, vocabulary integrity, and state coverage. It catches vague language and missing interactive states like hover or disabled before any code is generated.

UI spec linting detects contradictions between your brief, blueprint, and component specifications while verifying non-goals compliance and acceptance criteria traceability. This cross-file consistency verification ensures that all interactive components include required states like hover, focus, disabled, loading, error, and empty.

UI spec linting produces a ranked lint report with suggested fixes without auto-fixing your files. You can run this as a final quality gate right before invoking code generation, or use it for post-redline verification after making spec edits.

UI spec linting requires a complete spec package including brief, blueprint, system, component-specs, and acceptance files with required Run Manifest sections. It serves as a pre-generation quality gate to ensure all required files are present and non-empty before code generation.