Skip to content
cccskills
FreePublished on GitHub

pui-regression

Reproduce and repair a bounded Proto UI regression whose expected behavior and owning layer are already governed. Use this before domain implementation skills whenever work starts from a reproducible failure, including bug fixes, drift repairs, broken exports, Runtime failures, Adapter parity defects, Prototype defects, or public-projection regressions. Do not use when expected semantics or ownership is unresolved.

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

See how to install

Files included (2)

  • SKILL.md2.4 KB
  • agents/openai.yaml243 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Repair a governed regression

For event ordering, input attribution, CSS ownership or a suspect fixture, read internal/agent-operations/testing-method.md before designing the red case. Separate injected facts from observations and retain meaningful assertions when correcting an older test.

  1. Require a minimal reproduction, pui-trace map, fixed expected behavior, affected surfaces, and explicit exclusions.
  2. Classify the owning layer before editing. Keep the regression transition primary even when the owning layer is an Adapter, Module, Host Capability, or Prototype; propose a domain leaf later only if a separately governed artifact must change.
  3. Add or identify evidence that fails for the governed reason before the fix.
  4. Repair the smallest owning layer. Preserve unrelated behavior and avoid opportunistic refactoring.
  5. Update T-* mapping only to the extent the executable evidence proves.
  6. Record another domain leaf in the handoff only when its governed artifact genuinely must change; do not load it here.
  7. Record the focused failure/pass evidence, affected integration checks, and broader validation boundary for a later pui-validate transition.

When the repair would change a normative criterion, owner, public API, compatibility promise, or lifecycle, continue only if current authority already fixes that transition; otherwise route the smallest product-direction decision. Do not edit the spec merely to make the implementation pass, hide a lower-layer defect in a Prototype or stylesheet, or treat screenshots as sole protocol evidence.

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 technical identifiers canonical.

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 18, 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 18, 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 18, 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 18, 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 18, 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 18, 2026

See all skills by Proto-UI

Report a problem with this skill