Startup Design
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
A skill your agent uses when setting design direction — establishing principles, competitive positioning, experience mapping, or aligning stakeholders on what the design should achieve and why
Install Design Strategy
$ npx skills add Owl-Listener/designpowers --skill design-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers design-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/design-strategy .claude/skills/design-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "design-strategy" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-strategy into .claude/skills/design-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designpowers/tree/main/skills/design-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designpowers --skill design-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers design-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/design-strategy .agents/skills/design-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design-strategy" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-strategy into .agents/skills/design-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designpowers --skill design-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers design-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/design-strategy .cursor/skills/design-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "design-strategy" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-strategy into .cursor/skills/design-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designpowers.git --path skills/design-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designpowers --skill design-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers design-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/design-strategy .gemini/skills/design-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "design-strategy" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-strategy into .gemini/skills/design-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designpowers design-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designpowers --skill design-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/design-strategy .github/skills/design-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "design-strategy" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-strategy into .github/skills/design-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designpowers --skill design-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designpowers design-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/design-strategy .opencode/skills/design-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "design-strategy" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-strategy into .opencode/skills/design-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
design-strategy- GitHub stars
- 251
- Token cost
- ~1.1k tokens
- SKILL.md length
- 461 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when setting design direction — establishing principles, competitive positioning, experience mapping, or aligning stakeholders on what the design should achieve and why
- Works in 7 steps: Synthesise Inputs → Competitive Landscape → Define Design Principles → …
- Setting design direction — establishing principles
- SKILL.md covers Welcome Gate, When to Use, Process and Integration, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design Strategy is an agent skill from Owl-Listener/designpowers. Use when setting design direction — establishing principles, competitive positioning, experience mapping, or aligning stakeholders on what the design should achieve and why
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Positioning and messaging. The repository describes itself as: An agent design team you control: 10 agents that run an inclusive design process while you direct. The licence is MIT.
When your agent uses it
- Setting design direction — establishing principles
- Competitive positioning
- Experience mapping
- Aligning stakeholders on what the design should achieve and why
Example prompts
- “/design-strategy”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cb00757. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Design Strategy loads about 1.1k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 461 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designpowers at commit cb00757, republished under its MIT licence (© Owl-Listener). 461 words, ~1,144 tokens.
Download SKILL.mdSave it as
.claude/skills/design-strategy/SKILL.md (or your agent's skills folder).- name
- design-strategy
- description
- Use when setting design direction — establishing principles, competitive positioning, experience mapping, or aligning stakeholders on what the design should achieve and why
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
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]Show full SKILL.md (221 more words)Show less
Step 4: Experience Map
Map the end-to-end experience:
- Entry points — how do people arrive? (Search, link, referral, notification)
- First impression — what do they see, feel, understand in the first 5 seconds?
- Core journey — what steps do they take to accomplish their goal?
- Moments of friction — where might they struggle, hesitate, or leave?
- Exit points — how do they finish? What happens next?
For each moment, note the emotional state and the inclusive design considerations.
Step 5: Define Success Metrics
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).
Step 6: Write the Strategy Document
# 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
Step 7: Stakeholder Alignment
Present the strategy section by section. Confirm alignment before proceeding to design plans.
Integration
- Called by:
design-discovery - Calls:
writing-design-plans - Informs: All design skills — principles and strategy should be referenced in every design decision
Red Flags
| 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 |
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/design-strategy of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Design Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Design Strategy this skillOwl-Listener/designpowers | 251 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Amazon Brand Analyticsnexscope-ai/Amazon-Skills | 744 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Positioning Icptech-leads-club/agent-skills | 7k | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| Competitive Teardownalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Audience Belief Mapperaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Amazon Brand Analytics
nexscope-ai/Amazon-Skills
Amazon Brand Analytics interpretation and strategic insights for Brand Registry owners.
Positioning Icp
tech-leads-club/agent-skills
When the user wants to define their ideal customer profile, position an AI product, build messaging architecture, or validate product-market fit.
Competitive Teardown
alirezarezvani/claude-skills
Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence.
Audience Belief Mapper
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "map what our buyers believe", "capture the objections we keep hearing", or "find the switching forces that move the beachhead"; produces a belief map…
Value Proposition
phuryn/pm-skills
Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives.
More from Owl-Listener/designpowers
All 33 skills in this repoAdaptive Interfaces
Owl-Listener/designpowers
A skill your agent uses when designing for user preferences — motion sensitivity, contrast needs, colour schemes, text sizing, information density, or any interface behaviour that should adapt to…
Design Debate
Owl-Listener/designpowers
A skill your agent uses when a design direction is uncertain, when the team could go multiple ways, or when the user wants to see competing approaches argued before committing — orchestrates…
Design Debt Tracker
Owl-Listener/designpowers
A skill your agent uses when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration.
Design Discovery
Owl-Listener/designpowers
You MUST use this before any creative or design work — building features, creating components, designing interfaces, modifying user-facing behaviour.
Design Handoff
Owl-Listener/designpowers
A skill your agent uses when design work is complete and needs to be communicated to engineering — creates specifications, documents rationale, accessibility requirements, and interaction details in…
Design Review
Owl-Listener/designpowers
A skill your agent uses when the user wants to evaluate something that ALREADY EXISTS rather than build something new — "review this", "audit this screen", "what's wrong with this page", "is this…
Related
Questions about Design Strategy
What does Design Strategy do?
A skill your agent uses when setting design direction — establishing principles, competitive positioning, experience mapping, or aligning stakeholders on what the design should achieve and why. Design Strategy is an agent skill from Owl-Listener/designpowers.
When should I use Design Strategy?
Design Strategy fits situations like: setting design direction — establishing principles; competitive positioning; experience mapping; aligning stakeholders on what the design should achieve and why.
How do I install Design Strategy in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill design-strategy -a claude-code`. Or copy the skill folder (skills/design-strategy in Owl-Listener/designpowers) into .claude/skills/design-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Design Strategy in Codex?
Run `npx skills add Owl-Listener/designpowers --skill design-strategy -a codex`. Or copy the skill folder (skills/design-strategy in Owl-Listener/designpowers) into .agents/skills/design-strategy in your project. Codex loads it when a task matches its description.
Can I use Design Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designpowers --skill design-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-strategy, .gemini/skills/design-strategy, .github/skills/design-strategy and .opencode/skills/design-strategy in your project.
What does Design Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Strategy is instructions for the agent only.
Does Design Strategy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Design Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Design Strategy use?
Design Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Design Strategy use?
About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Design Strategy?
Skills that share tags, products or a category with Design Strategy: Startup Design (ferdinandobons/startup-skill, 1.2k stars), Amazon Brand Analytics (nexscope-ai/Amazon-Skills, 744 stars), Positioning Icp (tech-leads-club/agent-skills, 7k stars) and Competitive Teardown (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Strategy?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designpowers, which has 251 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on June 23, 2026.
Source: Owl-Listener/designpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.