- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill anti-slop-redesign -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill anti-slop-redesign -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill anti-slop-redesign -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill anti-slop-redesign -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/HEAD/packages/anti-slop/.pi/skills/anti-slop-redesignDel publicador
Most UI work changes a surface that already ships. Misclassifying the mode is the biggest source of bad redesign output: a "refresh" that renames routes, breaks e2e selectors and drops keyboard shortcuts is a regression, however good it looks. This skill makes the mode, the audit and the protected list explicit before anything is touched.
Authority: advisory. Findings feed the frontend-mockup-loop FIX step and
never override a WCAG-AA or severity gate. When a recommendation conflicts
with a gate result, the gate result stands and the recommendation is recorded
as overridden. The tell catalog itself lives in anti-slop-frontend; this
skill decides what may change and in which order.
frontend-mockup-loop MOCKUP on any surface that already ships.new-site → greenfield.State the anti-slop-frontend Design Read, then one of three modes:
Defaults per surface profile:
overhaul requires explicit user confirmation before proceeding. Ask once
(ask_user when available); without a yes, stay in preserve.overhaul only when the visual debt is structural (no design system,
broken mobile, broken IA). Sound IA and content → preserve.Produce the audit before touching any file. A redesign whose first artifact is a diff fails Verification.
anti-slop-frontend checklist for the declared
profile; list each hit with its rule id (A3, B2, ...).data-testid values).Apply in order; stop as soon as the brief is satisfied. Each lever is a separate, reviewable step.
anti-slop-frontend A1, T1).In preserve, levers 1-4 are the default scope; 5-6 need a reason in the
audit.
Diff the result against the protected inventory from step 2. Every changed protected item must be listed and confirmed (see below), or reverted.
In preserve and overhaul, these do not change unless the change is listed
explicitly and the user confirms it:
data-testid attributes (e2e suites select on them)Also preserve, unless asked: copy voice, existing accessibility wins (focus states, alt text, keyboard nav, contrast), and analytics event names.
overhaul.data-testid to match a new component name; the e2e suite
breaks silently in CI, not locally.overhaul has a recorded
confirmation.Redesign an existing UI without breaking it: declare a mode (greenfield / preserve / overhaul), audit the current surface before any edit, apply modernisation levers in priority order, and never silen
---name: anti-slop-redesigndescription: Redesign an existing UI without breaking it: declare a mode (greenfield / preserve / overhaul), audit the…---# packages/anti-slop/.pi/skills/anti-slop-redesign/SKILL.mdResumen general
Redesign an existing UI without breaking it: declare a mode (greenfield / preserve / overhaul), audit the current surface before any edit, apply modernisation levers in priority order, and never silently change routes, nav labels, form fields, shortcuts or data-testid hooks. Triggers: \"redesign this page\", \"modernise this UI\", \"refresh the look\", \"mockup an existing surface\".
Preguntas frecuentes
Descarga packages/anti-slop/.pi/skills/anti-slop-redesign/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/BlackBeltTechnology/pi-agent-dashboard.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.