From designpowers
Establishes design direction via principles, competitive analysis, experience mapping, and stakeholder alignment. Use after research, before detailed design; emphasizes accessibility.
npx claudepluginhub owl-listener/designpowers --plugin designpowersThis skill uses the workspace's default tool permissions.
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.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
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.
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.
Gather everything from previous phases:
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.
Write 3-5 design principles that will guide every decision. Good principles are:
Example format:
### [Principle Name]
**The principle:** [One sentence]
**What this means in practice:** [How this guides decisions]
**What this means we will NOT do:** [What this rules out]
Map the end-to-end experience:
For each moment, note the emotional state and the inclusive design considerations.
How will we know the design is working?
| Metric | What It Measures | Target | How to Measure |
|---|---|---|---|
| [Metric] | [What aspect of the experience] | [Goal] | [Method] |
Include at least one accessibility metric (e.g., task completion rate with assistive technology, WCAG compliance level, cognitive load score).
# Design Strategy: [Project Name]
## Design Principles
[3-5 principles]
## Competitive Position
[Where we differentiate]
## Experience Map
[End-to-end journey with emotional states]
## Success Metrics
[How we measure impact]
## Constraints and Trade-offs
[What we are choosing NOT to optimise for, and why]
Save to: docs/designpowers/strategy/YYYY-MM-DD-<project>-strategy.md
Present the strategy section by section. Confirm alignment before proceeding to design plans.
design-discoverywriting-design-plans| Flag | Response |
|---|---|
| Principles that nobody could disagree with ("Make it easy to use") | Rewrite. If everyone agrees, it is not guiding decisions |
| No accessibility principle | Add one. Inclusive design is a strategic advantage, not a compliance checkbox |
| Strategy without constraints | Every strategy involves trade-offs. Name them explicitly |