Operation Rules
Operation Rules
Section titled “Operation Rules”Governance
Section titled “Governance”| Change Type | Required Review |
|---|---|
| Token value change | Design and development |
| Component API change | Development and QA |
| New component | Planning, design, development, QA |
| Documentation-only change | Owner of affected area |
Contribution Flow
Section titled “Contribution Flow”- Describe the user problem.
- Check whether an existing token or component solves it.
- Add or update documentation first.
- Add code and Storybook examples.
- Run verification.
- Record migration impact when behavior changes.
Version Policy
Section titled “Version Policy”| Version | Meaning |
|---|---|
| Patch | Documentation or non-breaking visual refinement |
| Minor | New token, component, variant, or guide |
| Major | Breaking component API, token rename, or behavioral contract change |
Verification
Section titled “Verification”Run the default project checks before claiming the system is ready:
pnpm agent:verifypnpm typecheckpnpm lint