Sponsor Suno AI Music arrow_forward
Plugin

Design Ops

Streamline design operations with critique frameworks, handoff specs, sprint planning, review processes, and team workflows.

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

What Design Ops is

Design Ops 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 Design Ops 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 Design Ops

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 design-ops@<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 Design Ops 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 design-ops/.claude-plugin/plugin.json, shared under the repository's MIT license. Read the full file on GitHub.

Streamline design operations with critique frameworks, handoff specs, sprint planning, review processes, and team workflows.

Skills (9)

  • design-critique — Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use heuristic-evaluation (prototyping-testing).
  • design-debt-audit — Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
  • design-impact-reporting — Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).
  • design-qa-checklist — Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use handoff-spec.
  • design-review-process — Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use design-critique.
  • design-sprint-plan — Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use team-workflow.
  • handoff-spec — Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
  • team-workflow — Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
  • version-control-strategy — Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).

Commands (3)

  • /handoff — Run the full handoff workflow — specs, measurements, assets, states, and a QA checklist — and output a developer-ready package.
  • /plan-sprint — Run a design sprint end to end — challenge framing, schedule, exercises, and prototype test plan.
  • /setup-workflow — Set up a team's operating rhythm end to end — rituals, task flow, tooling, review gates, and version control.

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 Design Ops?

Design Ops is a plugin for Claude Code and Claude Cowork from the Owl-Listener/designer-skills repository on GitHub. Streamline design operations with critique frameworks, handoff specs, sprint planning, review processes, and team workflows.

How do I install Design Ops in Claude Code?

Add the repository as a plugin marketplace: claude plugin marketplace add Owl-Listener/designer-skills Install the plugin: claude plugin install design-ops@<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 Design Ops in Claude Cowork?

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

Is Design Ops 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.