- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill anti-slop-image-direction -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill anti-slop-image-direction -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill anti-slop-image-direction -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill anti-slop-image-direction -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/HEAD/packages/anti-slop/.pi/skills/anti-slop-image-directionVom Herausgeber
Generated reference images break a model out of its default layouts (centered hero over dark mesh, three equal cards). They are also paid, slow, and full of the same tells we ban. This skill keeps the benefit and drops the risk: images are an opt-in direction aid, distilled into a written brief, and the mockup loop's gates still decide.
Authority: advisory. Findings feed the frontend-mockup-loop FIX step and never override a WCAG-AA or severity gate. The direction brief is one input to GROUND; documented public rules and the WCAG gates still win over anything an image suggests.
All of these must hold, otherwise generate nothing:
anti-slop-frontend Design Read) is marketing or
new-site.Image direction is forbidden for product-ui. When asked for a dashboard,
admin panel, editor or any app screen, refuse image generation, say that image
direction does not apply to product UI, and offer a text-only direction brief
instead.
The text-only brief (see Fallback) is the primary, always-available path.
Images are an experimental extra. pi-nano-banana ships as a TypeScript bin:
a global npm / pi install copy does not run as a plain command
(ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING). Resolve the runner like this:
Probe: run $NB with no arguments; it prints a usage: pi-nano-banana ...
line. No usage line → the backend is unavailable → Fallback.
Never run an unpinned npx tsx outside the monorepo: npx would fetch
whatever tsx the registry serves and execute it with your permissions.
Backends: gemini (default, needs GEMINI_API_KEY in the environment or a
.env) or pi (--backend pi, an OpenRouter credential inside pi; a
different bill).
<mockupDir> the same way the mockup loop's MOCKUP step does: in the
pi-agent-dashboard repo, openspec/changes/<name>/mockups/ when a change
exists, else mockups/<slug>/; elsewhere, the loop's mockup directory.
References go in <mockupDir>/refs/.ask_user, stating: the image count, the backend (gemini or
pi), and that generation is paid. No confirmation → generate nothing.ask_user tool is
in your tool list. If it is absent (subagent, CI, headless run), the run is
headless: generate nothing and write the text-only brief.One image per planned section, using only the backend named in the confirmed plan:
$NB "<prompt>" --output <mockupDir>/refs/<nn>-<section>.png # gemini
$NB "<prompt>" --output <mockupDir>/refs/<nn>-<section>.png --backend pi
A backend change requires a new confirmation. If the confirmed backend fails (e.g. Gemini key missing) and the other one is available, stop, re-plan naming the new backend, and ask again. Never switch the backend silently.
Re-generating an image, or adding images beyond the confirmed count, also needs a new confirmation.
Every prompt carries its section's variation axes and the Part A bans: no purple/violet glow, no neon gradient, no div-style fake dashboard, no stock "Jane Doe" faces, no em-dashes in any rendered text.
Describe copy, never quote it: "a short two-line headline about release speed", not the headline itself.
refs/direction.mdRead every image and write <mockupDir>/refs/direction.md with, per section
and for the set:
direction.md becomes one input to frontend-mockup-loop step 1 (GROUND),
next to the shipped UI and the documented public rules. Where the direction
conflicts with a cited rule or a WCAG gate, the rule and the gate win.
Pick one value per axis per section; vary across the page. This section is also the text-only brief when no image is generated.
anti-slop-frontend A2).When the runner is not resolvable, the probe prints no usage line, or the
backend has no usable credentials: report the reason in one line, write
<mockupDir>/refs/direction.md text-only from the variation axes section
above, and continue. Do not fail the task. The same text-only brief is the
output of a headless run and of a declined confirmation.
product-ui, ever, even when asked twice.marketing or new-site; the request was explicit.refs/ holds exactly the confirmed number of images, one per section.refs/direction.md lists layout family, rhythm, palette hex, type
character and observed tells; no image text appears verbatim in the mockup.Opt-in, paid reference images for marketing or new-site work: plan one image per section, confirm count, backend and cost, generate with pi-nano-banana, then distill a written direction brief for the
---name: anti-slop-image-directiondescription: Opt-in, paid reference images for marketing or new-site work: plan one image per section, confirm count…---# packages/anti-slop/.pi/skills/anti-slop-image-direction/SKILL.mdÜbersicht
Opt-in, paid reference images for marketing or new-site work: plan one image per section, confirm count, backend and cost, generate with pi-nano-banana, then distill a written direction brief for the mockup loop. Images are direction, never source. Never for product UI. Triggers: \"generate design references\", \"image direction for this page\", \"show me visual directions\".
FAQ
Laden Sie packages/anti-slop/.pi/skills/anti-slop-image-direction/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/BlackBeltTechnology/pi-agent-dashboard.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.