## KriUiRegistry Consumer Contract When implementing or changing frontend UI, use this order: 1. Reuse an existing shared component in the project when it already meets the requirement. 2. Prefer an approved component from KriUiRegistry. 3. Otherwise, prefer a suitable shadcn/ui component. 4. Create a custom component only when the preceding options cannot meet the requirement safely. ### Required Shared References Before each related task, read the current contents of every matching reference, even if it was read earlier in the session. | Task scope | Required reference | |---|---| | Installing, upgrading, adapting, or verifying a registry component | `.agent-harness/references/kri-ui-registry/installation-and-adaptation.md` | | KriEditor HTML, image-map, sanitizer, or WYSIWYG compatibility | `.agent-harness/references/kri-ui-registry/editor-html-compatibility.md` | If a task spans multiple scopes, read every matching reference. Generated files under `.agent-harness/references/` are read-only copies; edit KriUiRegistry's `.agent/consumer.md` or `.agent/consumer-references/` and recompose instead.