Sponsor Suno AI Music arrow_forward
Plugin

Designer Toolkit

Essential designer utilities for writing rationale, building presentations, crafting case studies, UX writing, and driving adoption.

Type
Plugin
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 5, 2026
Version
1.0.0
Author
MC Dean

What Designer Toolkit is

Designer Toolkit is a plugin published in the Owl-Listener/designer-skills repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery.”

A plugin is a package that bundles skills, slash commands, subagents, hooks, and MCP connectors so they install together. Plugins are plain files with a manifest at .claude-plugin/plugin.json, and they work in both Claude Code and Claude Cowork.

Installing Designer Toolkit adds everything it ships in one step. Connectors inside a plugin still need to be connected separately, and hooks and subagents only run in Cowork and Claude Code, not in regular chat.

How to install Designer Toolkit

Claude Code

  1. Add the repository as a plugin marketplace: claude plugin marketplace add Owl-Listener/designer-skills
  2. Install the plugin: claude plugin install designer-toolkit@<marketplace-name>, using the marketplace name from the repository's .claude-plugin/marketplace.json.
  3. Restart the session if the new skills or commands don't appear straight away.

Claude Cowork

  1. Open Customize → Plugins and choose Add marketplace.
  2. Enter Owl-Listener/designer-skills (the owner/repo shorthand works for GitHub).
  3. Find Designer Toolkit in the list, click Install, then connect any connectors it needs from its Connectors tab.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from designer-toolkit/.claude-plugin/plugin.json, shared under the repository's MIT license. Read the full file on GitHub.

Essential designer utilities for writing rationale, building presentations, crafting case studies, UX writing, and driving adoption.

Skills (7)

  • case-study — Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use presentation-deck.
  • design-negotiation — 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-rationale — Write rationale connecting decisions to user needs, business goals, and principles. Use when a decision needs defending in writing. For a live conversation, use design-negotiation.
  • design-system-adoption — Create adoption strategy and enablement materials to drive design system usage. Use when the system exists but teams ignore it. For contribution and versioning rules, use design-system-governance (design-systems).
  • design-token-audit — Audit token usage across a product for coverage, drift, and hard-coded values. Use when tokens exist and you suspect they are being bypassed. For defining tokens in the first place, use design-token (design-systems).
  • presentation-deck — Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.
  • ux-writing — Write interface copy — microcopy, error messages, empty states, and CTAs. Use when the words are the deliverable. For content structure and ownership, use content-strategy (ux-strategy).

Commands (4)

  • /build-presentation — Build a design presentation end to end — audience framing, narrative structure, and supporting rationale.
  • /start-here — Find where to start in the collection — name what you're working on and get routed to one command, the two that follow it, and the stages you can skip.
  • /write-case-study — Build a portfolio case study end to end — project framing, process narrative, outcomes, and visuals.
  • /write-rationale — Write design rationale for a set of decisions, linking each to user needs, business goals, and principles.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Designer Toolkit?

Designer Toolkit is a plugin for Claude Code and Claude Cowork from the Owl-Listener/designer-skills repository on GitHub. Essential designer utilities for writing rationale, building presentations, crafting case studies, UX writing, and driving adoption.

How do I install Designer Toolkit in Claude Code?

Add the repository as a plugin marketplace: claude plugin marketplace add Owl-Listener/designer-skills Install the plugin: claude plugin install designer-toolkit@<marketplace-name>, using the marketplace name from the repository's .claude-plugin/marketplace.json. Restart the session if the new skills or commands don't appear straight away.

Can I use Designer Toolkit in Claude Cowork?

Open Customize → Plugins and choose Add marketplace. Enter Owl-Listener/designer-skills (the owner/repo shorthand works for GitHub). Find Designer Toolkit in the list, click Install, then connect any connectors it needs from its Connectors tab.

Is Designer Toolkit safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.