design-strategy

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

A framework for deciding what a product’s design should achieve and how it should stand out. It turns research, business goals, and constraints into shared design principles.

In plain words
What is it for?
Use it after discovery or research to set design principles, compare competitors, map the experience, define a product’s distinctiveness, and align stakeholders.
Why use it?
It reduces disagreement and prevents detailed design work from starting without a clear direction. Teams can judge design decisions against the same goals.

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 after discovery or research to set design principles, compare competitors, map the experience, define a product’s distinctiveness, and align stakeholders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/designpowers/design-strategy
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-strategy
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-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designpowers/design-strategy/github.svg)](https://agentmods.dev/skills/owl-listener/designpowers/design-strategy)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designpowers/design-strategy"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/design-strategy/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-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/designpowers/design-strategy"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/design-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 961 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Anti-Refusal · line 125
    Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.
    Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
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.00030 $0.00961
Opus 5 $0.00015 $0.00481
Sonnet 5 $0.00006 $0.00192
Haiku 4.5 $0.00003 $0.00096

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

Security

Grade A, and why

design-strategy 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-strategy/SKILL.md · 126 lines

How it starts

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

Design Strategy

Strategy is the bridge between understanding and making. It takes what you learned in discovery and research and turns it into a clear direction that every design decision can be measured against.

Welcome Gate

BEFORE running strategy, check whether the Designpowers welcome sequence has been shown this session. If the user has not yet seen the welcome (the bird, the greeting, and the walkthrough offer), you MUST invoke the using-designpowers skill FIRST and complete the welcome sequence before returning here. The bird must appear before any work begins. No exceptions.

When to Use

  • After discovery and/or research, before detailed design work
  • When stakeholders disagree about direction
  • When the team needs shared design principles
  • When positioning against competitors
  • When defining what makes this experience distinctive

Process

Step 1: Synthesise Inputs

Gather everything from previous phases:

  • Design brief (from design-discovery)
  • Research findings (if research-planning was used)
  • Personas (from inclusive-personas)
  • Existing design system or brand guidelines
  • Business objectives and constraints

Step 2: Competitive Landscape

If relevant, map the competitive landscape:

## Competitive Analysis

| Competitor | Strengths | Weaknesses | Accessibility | Differentiation Opportunity |
|-----------|-----------|------------|---------------|---------------------------|
| [Name] | [What works] | [What fails] | [WCAG compliance, inclusive design quality] | [Where we can do better] |

Pay specific attention to where competitors fail on accessibility — this is often the largest opportunity for differentiation.

Step 3: Define Design Principles

Write 3-5 design principles that will guide every decision. Good principles are:

  • Opinionated — they take a position, not state the obvious
  • Actionable — a designer can use them to make a decision
  • Testable — you can evaluate a design against them
  • Inclusive — at least one principle explicitly addresses accessibility

Read the full file on GitHub · 126 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 · 126 lines · 30 tokens per session scan A 6d72bf134eb1

Subscribe to this mod's changes

design-strategy is a skill published in the GitHub repository Owl-Listener/designpowers (243 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 961 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