ui-interfaz-en-implementacion

Enforces interface documentation and Playwright E2E screenshots for every UI implementation pass.

Updated May 13, 2026
One-click install
npx skills add https://github.com/jcg-admin/kaupamex-ui --skill ui-interfaz-en-implementacion-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-interfaz-en-implementacion
Source: https://github.com/jcg-admin/kaupamex-ui/tree/main/.claude/skills/ui-interfaz-en-implementacion
Command: npx skills add https://github.com/jcg-admin/kaupamex-ui --skill ui-interfaz-en-implementacion-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? UI implementations often ship without documentation of the actual built interface, creating drift between code and docs. This Skill makes an interface spec document and a Playwright E2E screenshot a mandatory part of the Definition of Done for any visible UI change in the kaupamex-ui React frontend. ## Core Features & Use Cases - Interface documentation gate: Requires an interfaz-<slug>.rst file with ASCII mockup, element-to-contract spec table, states (loading/empty/error), accessibility attributes, and traceability hashes committed alongside the code. - E2E evidence requirement: Mandates a Playwright spec (e2e/<slug>.e2e.js) that navigates the view and captures a curated, versioned screenshot under docs evidence folders with a <vista>-<verbo>-<ISO> naming convention. - Scope rules: Defines when the rule does not apply (internal refactors, renames, trivial style token changes) so effort is not wasted. - Use Case: When adding a new admin page to the React storefront, invoke this Skill before writing the component so the mockup, spec table, and E2E screenshot are produced in the same pass rather than deferred. ## Quick Start Invoke this skill before implementing the new orders page so the interfaz RST document and Playwright screenshot are produced in the same pass.

Frequently Asked Questions about ui-interfaz-en-implementacion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a UI implementation in the same pass as the code?▼

Create an interfaz-<slug>.rst file containing the route location, an ASCII mockup of the implemented state, a spec table mapping each element to its contract, loading/empty/error states, and traceability hashes. Commit it together with the component code and the E2E evidence.

What must a Playwright E2E evidence screenshot include for UI sign-off?▼

The spec e2e/<slug>.e2e.js must navigate the view and capture a screenshot, with a curated copy versioned under docs evidence folders named <vista>-<verbo>-<ISO>.png. A screenshot showing an error state does not satisfy the evidence requirement.

When does the UI documentation rule not apply?▼

It does not apply to internal refactors without visible changes, renames, logic fixes that do not alter the interface, or trivial style changes like a color token. Those are recorded as progress notes instead of requiring a mockup.

Why are error-state screenshots preserved instead of overwritten?▼

Error captures are kept with their ISO timestamp so the failure history remains auditable. A later fix adds a new image with a new timestamp rather than replacing the old evidence.

Can I defer the interface documentation to a later improvement initiative?▼

No. The rule explicitly prohibits deferring documentation to a future initiative; without the RST document and E2E screenshot the task does not pass the backlog gate and cannot be closed.