fragments/policy

You can enforce design conventions by converting plain-text requirements into Fragments governance policy files. This process translates accessibility, consistency, and responsiveness rules into validated configurations automatically stored under `.fragments/policies/`.

UI accessibility rules are design constraints ensuring usable interfaces, enforced automatically by generating Fragments governance policies. These policies are validated via CLI checks using the governance engine to maintain UI consistency and responsiveness across your project.

Validate design governance rules by running `npx fragments govern check --cloud` after generating your policy files. This cloud-enabled validation confirms your UI accessibility and consistency constraints behave as expected within the Fragments config workflow.

Yes, generating Fragments design policies requires a `fragments.config.ts` file with policy glob configuration. This setup allows the governance engine library to correctly parse natural language input and write resulting policy definitions into the `.fragments/policies/` directory.

Yes, you can manage the full lifecycle of UI conventions after creating a Fragments policy. The workflow supports listing, editing, and deleting policy files within `.fragments/policies/` to keep design governance rules aligned with evolving accessibility and responsiveness needs.

The best way to fix UI constraint violations found during governance checks is to leverage generated fix recommendations. By updating Fragments policy definitions and re-running `npx fragments govern check --cloud`, you can iteratively resolve accessibility and responsiveness failures.