Pui Contract

---
name: pui-contract
description: Create or update a readable Proto UI legacy-contract projection for explanation or an explicitly accepted uncataloged gap. Use for internal contract prose, migration banners, rationale, or synchronized readable projections. Do not use when an applicable spec entity already owns the rule or when semantics are unsettled.
---

# Maintain a readable contract

1. Read `AGENTS.md`, `internal/contracts/README.md`, the applicable spec entities, and the complete `pui-trace` map.
2. Build a coverage map that separates governed entity facts, explanatory material, and any uncataloged gap already fixed by current authority.
3. State the current authority and migration status in the document. Link exact entities that supersede or constrain the prose.
4. Keep explanations readable without copying a second normative rule set.
5. Preserve source and locale relationships required by the contract area.
6. When stabilized uncataloged semantics need cataloging, record `pui-spec` as the proposed next leaf; do not let the readable contract become permanent shadow authority.
7. Record public projection and validation work as separate handoffs. Do not load or execute those skills inside this transition.

Route an uncataloged gap or new semantic owner that current authority does not decide to an attended product-direction decision. Never let readable prose override an entity, and do not rewrite dated history to match current direction.

## Explicit handoff

Do not load or execute another skill. Return exactly one handoff conforming to `internal/agent-operations/schemas/skill-handoff.schema.json`. Carry required prior artifacts by reference, include every artifact this leaf produces according to `skills.yaml`, and set `nextSkillId` to one eligible registered leaf or `null`.

Communicate with the user in the user's current language. Keep repository artifacts in their governed language.