Skip to content
cccskills
FreePublished on GitHub

pui-contract

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.9 KB
  • agents/openai.yaml260 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Implement one governed Proto UI Adapter-profile realization slice. Use when target and runtime range, supported or omitted Module role, Host Capability fidelity, lifecycle translation, failure behavior, compatibility boundary, and evidence scope are fixed by current authority. Use pui-adapter-assess for research or readiness assessment and pui-regression first for a governed failing behavior.

The English summary is being prepared. Showing the original description.

Proto-UI/Proto-UI36Updated Oct 20, 2026

Assess one bounded Proto UI Adapter question without changing repository or external state. Use for new-Adapter research, target compatibility, catalog readiness, reviewed Module support or omission evidence, Host Capability fidelity, lifecycle translation, dependency risk, or implementation readiness. Do not catalog, implement, repair, or approve the Adapter slice.

The English summary is being prepared. Showing the original description.

Proto-UI/Proto-UI36Updated Oct 20, 2026

Measure the active Agent model with pinned offline ModelTrace sampling and return an unsigned closed-set attribution record. Use before Agent-originated commits, Issue/PR creation or material updates, comments, reviews, and current collaboration writes in either execution mode. Do not treat a fingerprint, declared model label, or record reference as authenticated identity, permission, independent review, or acceptance.

The English summary is being prepared. Showing the original description.

Proto-UI/Proto-UI36Updated Oct 20, 2026

Run Proto UI's dynamic comprehension assessment and derive an unsigned local task-fit result. Use when an Agent needs review calibration or a fresh autonomous task and review ceiling. Do not use a self-result as identity, permission, or acceptance evidence.

The English summary is being prepared. Showing the original description.

Proto-UI/Proto-UI36Updated Oct 20, 2026

Investigate a bounded Proto UI Contract, Prototype, Module, Host Capability, Adapter, schema, or ownership question and turn a genuinely unresolved direction into one semantic decision packet. Use for spec brainstorming, admission questions, competing semantic models, uncataloged behavior, or unresolved cross-layer boundaries.

The English summary is being prepared. Showing the original description.

Proto-UI/Proto-UI36Updated Oct 20, 2026

pui-ci

Free

Diagnose one bounded Proto UI Actions or CI failure from an exact workflow run and revision, then route the exact repair, validation, or recheck transition. Use to locate the owning failure and distinguish infrastructure from change failures. This leaf remains read-only.

The English summary is being prepared. Showing the original description.

Proto-UI/Proto-UI36Updated Oct 20, 2026

See all skills by Proto-UI

Report a problem with this skill