See CLAUDE.md for Claude Code-specific instructions and quick orientation.

The authoritative spec is: spec/PRD_BUILD_SPEC.md For document hierarchy and conflict resolution, see: spec/AUTHORITY.md

The canonical reading order for all project documents is defined in spec/AUTHORITY.md.

Modern CSS review tool + LLM context pack: configurable rulebook, selective safe fixes, LLM-friendly formatting, inline fix comments, and prompt export for complex refactors.

The app lets users paste CSS and get:

• errors / warnings / info based on a detailed rulebook
• selective safe fixes (user chooses what to apply)
• LLM-friendly formatting (structure-first, token-aware)
• optional inline comments showing what changed + old values
• one-click copy output with or without those comments
• LLM prompt export for tricky rules that shouldn’t be auto-fixed
• mobile-friendly UI

v1: all rule settings are session-only (no saved project profiles yet).

This repo contains both:

1. Spec / context pack (source of truth)
2. Implementation code (to be added/updated over time)

Source of truth: spec/PRD_BUILD_SPEC.md

See CLAUDE.md for a detailed file structure overview.

• Modern CSS recognition: don’t flag new properties/functions as invalid.
• Explainability: show WHAT / WHY / WHEN SAFE for each rule.
• User control: fixes are opt-in and reversible.
• LLM formatting: structured output by default (not minified).
• Token reduction happens via explicit rules (tabs→spaces, shorthands, etc.).

Start with CLAUDE.md for quick orientation, then follow the canonical reading order above.

Feed files in order from spec/AUTHORITY.md (see "Canonical Reading Order").

If documents conflict, higher-ranked document wins. See spec/AUTHORITY.md for the full hierarchy.

All open questions have been decided. See spec/DECISIONS.md for the full decision log.

• ✅ Spec v1.2 complete
• ✅ Documentation and LLM guidance complete
• ✅ All open questions resolved (2026-01-30)
• ✅ App scaffolding not created yet
• ✅ Rule engine + UI implementation pending

See prompts/IMPLEMENTATION_CHECKLIST.md for phased implementation plan.

• Keep spec/ clean and stable.
• Don’t change requirement IDs lightly (FR-, AC-, C-*).
• If behavior changes, update the spec first.

TBD