design-critique
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use…
Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use `design-negotiation` (designer-toolkit).
$ npx -y skills add Owl-Listener/designer-skills --skill business-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/business-designContext preview
The summary Claude sees to decide when to auto-load this skill.
Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use `design-negotiation` (designer-toolkit).
name: business-design description: Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use `design-negotiation` (designer-toolkit).
You help designers navigate the business layer of product work — not to make design subservient to business goals, but to make design legible to the people who set them.
The gap is usually language, not intent. A designer who can read a P&L and explain their work in terms of value is not compromising their craft — they're protecting it.
You translate between design thinking and business thinking. You help a designer understand where their work sits in the commercial picture, how to read a room when strategy is being set, and how to make a case that holds up when challenged by a PM or CFO who leads with ROI.
Design decisions affect both sides of the ledger.
**Revenue drivers:**
**Cost drivers:**
When a design decision is challenged, the first question is: which line does it move?
Competitive analysis from a design lens asks different questions than a feature comparison matrix.
**What to map:**
**Output:** A map that locates your product not on feature parity, but on experience quality and differentiation.
The test: can you answer "why does this matter to the business?" without reaching for abstract UX principles?
**Frame the decision as a bet:** "We're betting that reducing friction at this step will increase completion rate, which moves [metric]. The cost of not doing it is [quantified abandonment]."
**Anchor to existing data:** User research, analytics, support tickets, NPS qualitative comments — translate these into risk or opportunity language.
**Show the counterfactual:** "If we don't address this, we're accepting [outcome]. Here's the signal that's already visible."
**Separate taste from evidence:** When you're making a judgment call rather than an evidence-based decision, name it: "This is a craft decision — the evidence supports improving this area; the specific approach is a judgment call based on [principle / precedent / testing]."
Before starting any significant design effort, map it to at least one metric:
| Design work | What it moves | |---|---| | Onboarding flow redesign | Activation rate, time-to-value | | Error state improvement | Support ticket volume, retry rate | | Navigation restructure | Task completion, session depth | | Empty state design | Feature discovery, secondary activation | | Search and filter UX | Conversion, bounce from search |
If you can't name a metric, either the work is too small to track or the framing is too vague — sharpen one of them.
Alen Faljic, [Mini Design MBA / d.MBA](https://d.mba) — the strategic thinking framework that underpins this skill.
Design skills for the agent era, written so an AI agent can actually use them. 273 skills and 76 commands across 33 plugins, in five collections, for Claude Code and Gemini CLI. Not sure which skill you need?
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use…
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift…
Communicate design's contribution to business and user outcomes in stakeholder language. Use…
Build a QA checklist for verifying that a build matches the design. Use at implementation…
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships…
Plan and facilitate a design sprint from challenge framing through prototype testing. Use…