design-debate

design-debate is a skill for Claude Code from Owl-Listener/designpowers. It costs 44 tokens per session (1,827 once invoked), scanned A, original, MIT.

A structured design discussion in which agents argue for different visual or interaction approaches and explain their trade-offs.

In plain words
What is it for?
Use it to compare options for navigation, layout, or interaction patterns before making a design decision. The user chooses the direction.
Why use it?
It helps when several design directions could work and prevents the team from choosing the first idea simply because everyone agrees.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the designpowers plugin — 36 skills, 10 agents, 1 hook shipped together

Good fit Use it to compare options for navigation, layout, or interaction patterns before making a design decision. The user chooses the direction.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/designpowers/design-debate
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Owl-Listener/designpowers --skill design-debate
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designpowers

Made for: Claude Code.

Or install designpowers, the plugin that ships this one along with the rest of its 36 skills, 10 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-debate

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designpowers/design-debate/github.svg)](https://agentmods.dev/skills/owl-listener/designpowers/design-debate)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designpowers/design-debate"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/design-debate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-debate

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/designpowers/design-debate"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/design-debate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,827 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01827
Opus 5 $0.00022 $0.00914
Sonnet 5 $0.00009 $0.00365
Haiku 4.5 $0.00004 $0.00183

Measured 9d ago against content hash 4d1cc049d556, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

design-debate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/design-debate/SKILL.md · 200 lines

How it starts

The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Debate

Good design decisions come from tension, not consensus. When agents converge too quickly, they optimise for agreement instead of the best answer. This skill creates productive conflict — agents argue for competing directions with real trade-offs, and the user decides.

When to Use

  • When the design-strategist identifies multiple viable directions
  • When the design-lead proposes a visual direction and alternatives exist
  • When the user says "I'm not sure which way to go" or "what are my options?"
  • When the design-critic recommends "rethink" — a debate can surface the better path
  • When a decision has significant downstream consequences (navigation pattern, layout model, interaction paradigm)
  • When the user explicitly asks for a debate: "debate this", "argue both sides", "what are the trade-offs?"

Do Not Use When

  • The decision is trivial (icon choice, exact padding value)
  • Accessibility requirements dictate the answer — there is nothing to debate
  • The user has already made up their mind — respect their direction
  • The brief clearly specifies the approach — follow it

Process

Step 1: Frame the Question

Define the design question precisely. A debate without a clear question produces noise.

Format:

DESIGN QUESTION: [Specific, answerable question]
CONTEXT: [Brief context from design-state.md]
CONSTRAINTS: [Non-negotiable requirements from brief, accessibility, taste profile]
STAKES: [Why this decision matters — what it affects downstream]

Example:

DESIGN QUESTION: Should the onboarding flow use a multi-step wizard or a single scrollable page?
CONTEXT: App for first-time pet owners, ages 25-45. Primary persona has mild anxiety about "doing it right."
CONSTRAINTS: Must be completable in under 3 minutes. Must work on mobile. Must not require account creation upfront.
STAKES: Sets the interaction pattern for all future multi-step flows in the app.

Step 2: Assign Advocates

Select 2-3 agents to argue for different directions. Each agent argues FOR their assigned position — they are advocates, not neutral analysts.

Read the full file on GitHub · 200 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 200 lines · 44 tokens per session scan A 4d1cc049d556

Subscribe to this mod's changes

design-debate is a skill published in the GitHub repository Owl-Listener/designpowers (243 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,827 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

accessibility-a11y

Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.

BlackBeltTechnology/pi-agent-dashboard · 44 tokens

tailwind-shadcn

Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.

BlackBeltTechnology/pi-agent-dashboard · 50 tokens

anti-slop-frontend

A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…

BlackBeltTechnology/pi-agent-dashboard · 147 tokens

frontend-mockup-loop

Plan, build, and iterate UX-friendly frontend mockups via a ground→contract→mockup→test→fix→learn loop, acting as an expert UX designer who grounds every decision in externally documented public design rules (Nielsen heuristics, Laws of UX, WCAG, GOV.UK/USWDS/Material). Uses the bundled servemockup, scoremockup, and…

BlackBeltTechnology/pi-agent-dashboard · 185 tokens

frontend-mockup-loop-dashboard

Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard…

BlackBeltTechnology/pi-agent-dashboard · 83 tokens

goga-define-experience

Define the user experience required to achieve the established product goals and solve the identified problem.

qarium/goga · 6 tokens