PliegoCSS is an experimental standards-first CSS compiler and verifier for humans and agents. It accepts compact typed Rust authoring today, but that is one frontend rather than the product category: standard-CSS audit, policy, explainability, and deterministic receipts are the controlling direction. The current workspace has compile-time syntax and conflict validation, typed semantic IR, deterministic CSS, typed configurable themes, responsive and interactive variants, conditional composition, and an explicit build CLI. Rust 1.85 is the minimum supported version.
Gate A and Gate B are closed as conditional GO decisions over their frozen fixtures. Those results
validate continued development; they do not declare the compiler production-ready or close the
PliegoRS integration and developer-experience phases. The current PliegoRS evidence is a pinned
local cross-repository SSR/SSG gate plus a resumability-markup seam with declarative, explicitly
owned route bundles. pliego-cssc watch only regenerates artifacts; composed with the pinned
pliego dev, the certified local path performs a PliegoRS-owned full-page browser reload. The CLI
accepts an adapter-owned, exact-range reachability sidecar and projects it into
opt-in manifest schema 4 without inferring framework semantics. Schema 5 additionally reconciles
that semantic graph with exact rules, declarations, and UTF-8 byte ranges in the final CSS.
Explicit bundle builds can also emit a framework-neutral asset load plan with exact CSS/manifest
hashes and independent route/island bundle selections. Schema-5 builds can additionally emit one
portable Project Index joining source sites to semantic, token, component, and physical CSS IDs.
- Installation
- First standard-CSS audit
- First compile
- PliegoRS + PliegoCSS from an empty project
- Project structure
- Editor setup for VS Code and Neovim
- Mental model
- Themes and tokens
- Configure custom breakpoints
- Use typed container queries
- Use typed ARIA and data variants
- Use typed writing modes
- Use typed cascade layers
- Configure CSS budgets
- Configure package ownership and route composition
- Configure accessibility policies
- Audit CSS usage with reachability and observation evidence
- PliegoRS development reload loop
- Theme troubleshooting
- Ownership sidecar troubleshooting
- Accessibility audit troubleshooting
- Usage-evidence troubleshooting
- LSP troubleshooting
- PliegoRS integration boundary
- Syntax contract
- Implemented utility reference
- Generated utility and seed-token catalog
- Theme schema
- DTCG 2025.10 exchange bridge
- Canonical token graph schema 1
- Token-usage report schema 1
- Critical-style evidence schema 1
- Command-line compiler
- Language Server Protocol transport
- Shared compiler engine
- LSP diagnostic corpus schema 2
- Public API candidate
- Declarative bundle-plan schema
- Asset load-plan schemas 1 and 2
- Ownership sidecar schema 1
- Project Index schemas 1 and 2
- Provenance manifest schema 4
- Physical provenance manifest schema 5
- Reachability sidecar schema 1
- Usage analysis schemas 1 and 2
- Usage observation schema 1
- Usage retention sidecar schema 1
- CLI diagnostic JSON schema
- Canonical finding schema 1.0.0
- Control manifest and build receipt schema 1.0.0
- Canonical CSS Source Map v3 contract
- Standard CSS audit command
- Bounded standard-CSS classifier corpus
- Bounded cascade explanation command
- Repair proposal, plan, dry-run, and Change Receipt schemas 1.0.0
- Repair check policy and Verification Receipt schemas 1.4.0
- Migration inventory schema 1
- Migration project inventory schema 1
- Reversible migration plan schema 1
- CSS budget policy schema 1
- Accessibility policy schema 1
- Standards and third-party provenance schema 1
- StyleId binary format 2
- Semantic IR binary format 2
- Historical semantic IR binary format 1
- Compatibility candidate contract
- Compatibility policy schema 2
- Frozen adapter support policy for 0.1.x
- Initial utility catalog (F0 plan)
- Glossary
- Research-derived product requirements and alpha gates
- Strategic CSS/Rust/AI product contract and R0-R3 gates
- Product maturity map
- Representative applications and selected gaps
- R0 unified manifest and receipt design
- Typed IR
- Conflict model
- CSS emission
- Composition and conditional styles
- Architecture decisions
- 0.1.0 release readiness — current generated view
- 0.1.0 release readiness — schema-4 machine authority
- 0.1.0-rc.2 hardening report — historical
- 0.1.0-rc.3 candidate release notes
- Historical evidence archive
- F0 verification
- F1 parser and IR
- F2 semantic compiler
- F3 deterministic CSS pipeline
- F4 variants and composition
- F5 native PliegoRS integration
- F6 developer experience
- F7 measured optimization and reachability
- Reachability-pruning benchmark
- Repair authority conformance corpus
- Migration bridge contract corpus
- Reviewed public migration role corpus
- Portability contract
- Packaging contract
- Gate A status
- Gate A benchmark
- Historical Gate B complete-fixture benchmark
- Tailwind Benchmark Authority v2
- Generated competitive matrix against Tailwind CSS v4.3.3
- Representative application 1: plain HTML audit-first
- Representative application 2: Vite/Tailwind inventory-first
- Representative application 3: CSS Modules consumer
- Representative application 4: typed Rust controlled build
- Representative application 5: framework-neutral multiroute bundles
- Adjacent media-query merge benchmark
- Rust check baseline
- Frozen machine snapshots
- Browser validation
- Browser/output certification v1
- Hosted browser/OS evidence matrix
- PliegoRS development-loop latency and browser reload
- Migration inventory and plan adoption latency
- WASM runtime overhead
- Brand system
- Contributing
- Governance
- Security
- Support
- Community code of conduct
- Trademark policy
- Property, parallel, and fuzz testing
- Release process and checklist
- Changelog
- Apache-2.0 license
Each reference page's explicit status controls. Pages marked implemented describe behavior in the current workspace; pages marked as a frozen contract remain non-integration specifications until their listed implementation gates pass.