DOCUMENTATION
Use the smallest surface that solves the problem.
Start by auditing standard CSS. Typed authoring, manifests, repair, and migration are layered capabilities—not entry requirements.
Start04 entries
01Getting startedAudit first, compile when it adds value, and keep the browser contract ordinary.07InstallationInstall the CLI for any project, add the Rust crates only when typed authoring belongs in the application.08First auditRun a read-only CSS audit, inspect canonical findings, then decide whether transformation or policy is justified.09Editor setupUse the language server for diagnostics, completion, hover evidence, and catalog-aware authoring.Core05 entries
02Typed stylesStable 128-bit identities connect Rust source, emitted classes, manifests, and physical declarations.10Utility syntaxUtilities lower into semantic slots, conditions, and typed values before any CSS serialization occurs.11CompositionCompatible slots commute. Conflicting slots require an explicit branch-over-base operation.12Variants and conditionsEvery variant joins a typed condition path with deterministic normalization and specificity behavior.13Themes and tokensTOML themes and DTCG Resolver documents feed the same typed registry, identity, graph, and emitted variables.Standard CSS03 entries
03Audit and transformAnalyze standard CSS, enforce policy, and transform output without claiming ownership of authored source.14PoliciesCompatibility, accessibility, payload, package, route, and ownership policies turn expectations into reviewable inputs.15Cascade inspectionInspect authored CSS by element and longhand to see matching selectors, precedence, and the final winner.Evidence04 entries
04Evidence and provenanceArtifacts carry hashes, source lineage, graphs, findings, and receipts designed for replay.16Style manifestsManifest schema 5 connects source origins, semantic assignments, final selectors, physical declarations, and CSS ranges.17Control artifactsControlled builds stage related outputs, lock the destination, verify hashes, compensate failures, and expose one completed receipt.18Critical style evidenceJoin observed browser behavior to project topology and retained style identity without letting an observation silently authorize removal.Migration04 entries
05Controlled migrationInventory first, generate bounded plans, preserve originals, and detect drift immediately before publication.19Tailwind migrationRecover the real utility surface, classify supported roles, and keep unsupported framework behavior visible.20Sass migrationInventory variables, nesting, mixins, imports, and generated surfaces without pretending every Sass abstraction is a utility.21CSS Modules migrationDiscover module exports and usage while keeping application-owned component topology separate from CSS semantics.Tooling04 entries
22Command-line referenceCompile, inspect, audit, transform, explain, bundle, watch, migrate, format, plan, and verify with strict argument contracts.23Language serverThe LSP shares parser and catalog contracts with the CLI while bounding subprocess time and output.24Watch modePoll coherent snapshots, republish only valid groups, and retain the last valid output across transient edits.25Repair agentGenerate bounded repair proposals, bind authorization to source hashes, verify in staging, then publish receipts.Integrations03 entries
06PliegoRS integrationPliegoRS is the first native consumer, not the only target. It supplies topology; PliegoCSS supplies style identity and artifacts.26Plain HTMLUse PliegoCSS as a standards control layer around an ordinary stylesheet and static HTML build.27Generic build toolsVite, webpack, esbuild, CI systems, and custom pipelines consume explicit CSS, manifests, findings, maps, and asset plans.Reference02 entries
28ConfigurationTheme, target, format, manifests, reachability, pruning, and token selections are explicit, validated, and hash-bound.29DiagnosticsParser, source scanner, composition, policy, invocation, migration, and formatter failures share a canonical transport.