Reimagine It Audit
Kayforkind/reimagine-it
Design Health — runs 19 deterministic quality checks on HTML output.
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals.
Install Design Negotiation
$ npx skills add Owl-Listener/designer-skills --skill design-negotiation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills design-negotiation --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/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/designer-toolkit/skills/design-negotiation .claude/skills/design-negotiation && 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-negotiation" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/designer-toolkit/skills/design-negotiation into .claude/skills/design-negotiation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-negotiation", 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/designer-skills/tree/main/designer-toolkit/skills/design-negotiationType 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/designer-skills --skill design-negotiation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills design-negotiation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/designer-toolkit/skills/design-negotiation .agents/skills/design-negotiation && 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-negotiation" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/designer-toolkit/skills/design-negotiation into .agents/skills/design-negotiation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-negotiation", 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/designer-skills --skill design-negotiation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills design-negotiation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/designer-toolkit/skills/design-negotiation .cursor/skills/design-negotiation && 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-negotiation" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/designer-toolkit/skills/design-negotiation into .cursor/skills/design-negotiation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-negotiation", 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/designer-skills.git --path designer-toolkit/skills/design-negotiation--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/designer-skills --skill design-negotiation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills design-negotiation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/designer-toolkit/skills/design-negotiation .gemini/skills/design-negotiation && 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-negotiation" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/designer-toolkit/skills/design-negotiation into .gemini/skills/design-negotiation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-negotiation", 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/designer-skills design-negotiationInstalls 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/designer-skills --skill design-negotiation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/designer-toolkit/skills/design-negotiation .github/skills/design-negotiation && 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-negotiation" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/designer-toolkit/skills/design-negotiation into .github/skills/design-negotiation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-negotiation", 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/designer-skills --skill design-negotiation -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/designer-skills design-negotiation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/designer-toolkit/skills/design-negotiation .opencode/skills/design-negotiation && 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-negotiation" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/designer-toolkit/skills/design-negotiation into .opencode/skills/design-negotiation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-negotiation", 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-negotiation- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~1.4k tokens
- SKILL.md length
- 754 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals.
- Tasks that involve Design review and critique
- SKILL.md covers What You Do, What Design Negotiation…, Common Negotiation Contexts and Evidence-Based Advocacy, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design Negotiation is an agent skill from Owl-Listener/designer-skills. Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
Its SKILL.md is about 1.4k 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 Media & Creative, covering Design review and critique. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- Tasks that involve Design review and critique
Example prompts
- “/design-negotiation”
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. 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.
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 Negotiation loads about 1.4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 754 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/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 754 words, ~1,393 tokens.
Download SKILL.mdSave it as
.claude/skills/design-negotiation/SKILL.md (or your agent's skills folder).- name
- design-negotiation
- description
- Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use `business-design` (ux-strategy).
Design Negotiation
You are an expert in advocating for design quality and investment in cross-functional environments.
What You Do
You help designers navigate the situations where design quality is at risk from scope compression, timeline pressure, or organizational under-investment — and translate design needs into terms that resonate with PMs, engineers, and leadership.
What Design Negotiation Actually Is
Design negotiation is not about winning arguments. It is about finding the overlap between what users need, what the business wants, and what design believes is necessary — and making that overlap visible to decision-makers. The goal is shared understanding and informed trade-offs, not the designer getting their preferred outcome at any cost.
Common Negotiation Contexts
Timeline Compression
"We need this shipped in two weeks, not four." Approach:
- Clarify what "done" means: shipped vs. right vs. defensible
- Scope with evidence: "We can ship [X] in two weeks. To do that, we drop [Y] and accept [Z] risk."
- Name the debt: "Shipping without testing creates this specific risk for users."
- Offer a phased path: "Ship the essential flow now; we address [Y] in the next sprint."
Scope Reduction Without Design Review
"Engineering already started building. Design just needs to clean it up." Approach:
- Don't relitigate what's built — focus on what can still be influenced
- Identify the specific user experience risks in the current implementation
- Prioritize the 2–3 highest-impact changes; accept the rest as debt to document
- Establish a process agreement for next time
Stakeholder Override of Design Decisions
"The CEO wants the button to be red." Approach:
- Separate the request from the reasoning: "What outcome is this trying to achieve?"
- Validate the goal; present alternatives: "If the goal is urgency, here are three ways to achieve it — one of which is red."
- Bring data: user testing, accessibility, precedent in the design system
- Document the decision either way: what was decided, who made it, what the trade-off was
Headcount and Resource Requests
"We need a third designer on this project." Approach:
- Quantify current scope vs capacity: "We have X design dependencies for Y delivery date; current capacity covers Z."
- Translate to business risk: "Without the additional resource, we ship [specific feature] without design, or we push [milestone] by X weeks."
- Propose alternatives if headcount isn't available: scope reduction, phased delivery, design system acceleration
Evidence-Based Advocacy
Design negotiation is strongest when grounded in evidence:
- User research: "We tested this flow with 8 users; 6 couldn't complete the task."
- Metrics: "The current pattern has a 34% drop-off at step 3."
- Competitive context: "Every comparable product in this space supports X."
- Accessibility and legal: "This pattern fails WCAG 1.4.3; that's a compliance risk."
- Design system precedent: "The system already solves this — deviating creates maintenance debt." Avoid arguments based on taste ("this looks better") or authority ("I'm the designer") — they don't land with non-designers and they shouldn't have to.
Show full SKILL.md (285 more words)Show less
Negotiation Principles
Start with the user problem, not the design solution
"Users are confused at this step" is more compelling than "this layout is unclear." Lead with the problem; the solution follows.
Acknowledge constraints
Engineers have technical constraints; PMs have delivery pressure; leadership has business goals. Dismissing these weakens your position. Name them first: "I understand we need this by Q3…"
Make trade-offs explicit
Decision-makers often don't know they're making a trade-off. Naming it — "if we ship without this, we accept X risk" — gives them agency and creates accountability.
Pick your battles
Not every design decision is worth negotiating. Reserve your credibility for the things that genuinely affect users. Let go of things that won't.
Document outcomes
When a decision goes against design's recommendation, write it down: what was decided, why, and what the expected impact is. This creates accountability and builds the evidence base for future conversations.
Building Long-Term Influence
Negotiation outcomes depend heavily on the relationships and credibility you've built before the negotiation:
- Deliver consistently: teams trust designers who ship; trust opens room for pushback
- Speak the business language: designers who understand revenue, cost, and risk are taken more seriously in strategic conversations
- Bring data habitually: teams that routinely hear research in design reviews start expecting it everywhere
- Celebrate shared wins: when design investment leads to measurable outcomes, make sure the team knows — publicly and with specifics
Best Practices
- Prepare for high-stakes conversations in advance: know the data, anticipate objections, have alternatives ready
- Never go into a negotiation without a fallback position — what's the minimum acceptable outcome?
- Ask questions before proposing solutions; understand the other party's constraints before defending yours
- Follow up in writing after verbal agreements — misremembers are common under deadline pressure
© 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 designer-toolkit/skills/design-negotiation of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Design Negotiation 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 Negotiation this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Reimagine It AuditKayforkind/reimagine-it | 205 | — | ~756 | Automated safety check: Pass | MIT | |
| Design Reviewtsubotax/melta-ui | 201 | — | ~504 | Automated safety check: Pass | MIT | |
| Canva Design Feedbackcanva-sdks/canva-skills | 119 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Design Critiquepaperclipai/paperclip | 99k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Design CritiqueWrongStack/WrongStack | 371 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Design Review
tsubotax/melta-ui
HTMLファイルをmelta UIデザインシステムに照らしてレビューし、違反を検出・分類・修正提案する。トリガー: 「デザインレビュー」「DSチェック」「禁止パターンチェック」「design review」「check compliance」「DS準拠確認」。対象ファイルのパスを引数で受け取る。
Canva Design Feedback
canva-sdks/canva-skills
Read a Canva design and return structured, actionable design feedback — visual hierarchy, copy/messaging, layout & spacing, consistency, readability, and accessibility.
Design Critique
paperclipai/paperclip
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
Design Critique
WrongStack/WrongStack
A skill your agent uses to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states…
Steve Jobs Design Review
wondelai/skills
Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Design Negotiation
What does Design Negotiation do?
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Design Negotiation is an agent skill from Owl-Listener/designer-skills. Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals.
When should I use Design Negotiation?
Design Negotiation fits situations like: tasks that involve Design review and critique.
How do I install Design Negotiation in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill design-negotiation -a claude-code`. Or copy the skill folder (designer-toolkit/skills/design-negotiation in Owl-Listener/designer-skills) into .claude/skills/design-negotiation in your project. Claude Code loads it when a task matches its description.
How do I install Design Negotiation in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill design-negotiation -a codex`. Or copy the skill folder (designer-toolkit/skills/design-negotiation in Owl-Listener/designer-skills) into .agents/skills/design-negotiation in your project. Codex loads it when a task matches its description.
Can I use Design Negotiation 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/designer-skills --skill design-negotiation -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-negotiation, .gemini/skills/design-negotiation, .github/skills/design-negotiation and .opencode/skills/design-negotiation in your project.
What does Design Negotiation need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Negotiation is instructions for the agent only.
Does Design Negotiation 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 Negotiation 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 Negotiation use?
Design Negotiation 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 Negotiation use?
About 1.4k tokens (SKILL.md is roughly 5.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 Negotiation?
Skills that share tags, products or a category with Design Negotiation: Reimagine It Audit (Kayforkind/reimagine-it, 205 stars), Design Review (tsubotax/melta-ui, 201 stars), Canva Design Feedback (canva-sdks/canva-skills, 119 stars) and Design Critique (paperclipai/paperclip, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Negotiation?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.