Designer Skills plugin for Grok Build

Community Claude Code plugin, installs in GrokPluginDesign

Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery.

How to install Designer Skills in Grok Build

1. Add this repo as a plugin marketplace in Grok Build (once per computer):

grok plugin marketplace add Owl-Listener/designer-skills

2. Install the plugin:

grok plugin install design-research@Owl-Listener/designer-skills --trust
✓ Install-checked in Grok Buildchecked Oct 18, 2026

Review before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.

This repo's marketplace has 33 plugins; we checked design-research, design-systems, ux-strategy. Install another the same way: grok plugin install <name>@Owl-Listener/designer-skills --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Inside Grok Build: type /plugins, open the Marketplace tab, press a and add Owl-Listener/designer-skills, then select design-research and press i.

Command format: Grok Build's plugin guide

What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 47 skills, 10 slash commands. That's an install check only: we haven't run it in a live Grok session.

What it contains

Skills (40)

  • affinity-diagram — Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
  • behavioural-analytics — Read funnels, retention curves, and event data as a designer — separating a design problem from a tracking artefact. Use when handed product data you did not design and asked why people drop off. For choosing what to measure, use `metrics-d
  • card-sort-analysis — Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).
  • diary-study-plan — Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use `usability-test-plan`.
  • empathy-map — Build a Says, Thinks, Does, Feels map for one user or segment. Use when sharing user understanding quickly. For a composite archetype with goals and behaviours use `user-persona`; for cross-session themes use `affinity-diagram`.
  • interview-script — Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use `summarize-interview`.
  • jobs-to-be-done — Map functional, emotional, and social jobs with outcome expectations. Use when reframing decisions around motivation rather than features. For who the user is, use `user-persona`.
  • journey-map — Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flo
  • qual-quant-triangulation — Reconcile what the numbers say with what users say, and design the study that settles it rather than restates it. Use when behavioural data and research findings point different ways. For reading the data on its own, use `behavioural-analyt
  • research-repository — Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use `affinity-diagram`.
  • summarize-interview — Turn one interview transcript into themes, supporting quotes, and action items. Use immediately after a session. For synthesising many sessions at once, use `affinity-diagram`.
  • survey-design — Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use `a-b-test-design` (prototyping-testing).
  • usability-test-plan — Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use `test-scenario` (prototyping-testing).
  • user-persona — Build research-grounded personas with goals, frustrations, and behavioural patterns. Use when decisions need a consistent user reference. For one session's emotional snapshot use `empathy-map`; for motivation framing use `jobs-to-be-done`.
  • discover — Run a full user research cycle — persona creation, empathy mapping, and journey mapping for a product or feature.
  • interview — Prepare an interview script or summarize an interview transcript into structured insights.
  • synthesize — Synthesize research data into affinity diagrams, themes, and actionable insights.
  • test-plan — Run the full usability study workflow — research questions, participant criteria, tasks, metrics, and facilitation guide.
  • accessibility-audit — Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibili
  • component-spec — Specify one component — props, states, variants, accessibility, and usage rules. Use when defining a library component. For the reusable doc scaffold use `documentation-template`; for a problem-solution pattern use `pattern-library`.
  • design-system-governance — Define how the system evolves — contribution model, versioning, deprecation, and change management. Use when multiple teams contribute. For driving uptake use `design-system-adoption` (designer-toolkit); for design file history use `version
  • design-token — Define and organise tokens for colour, spacing, type, and elevation with naming and usage rules. Use when establishing the token layer. For auditing existing usage use `design-token-audit` (designer-toolkit); for multi-brand mapping use `th
  • documentation-template — Generate a reusable documentation scaffold for components, patterns, or guidelines. Use when standardising how the system is documented. For the content of one component's spec, use `component-spec`.
  • icon-system — Specify an icon system — grid, sizing, stroke weight, naming, categories, and implementation. Use when standardising iconography. For broader illustration, use `illustration-style` (ui-design).
  • localization-design — Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use `ux-writing` (designer-toolkit).
  • motion-system — Define motion tokens — durations, easing vocabulary, and reduced-motion handling — for consistency product-wide. Use when standardising motion across a system. For crafting one specific animation, use `animation-principles` (interaction-des
  • naming-convention — Establish naming rules for components, tokens, and layers with patterns and worked examples. Use when names are inconsistent or being set. For what the tokens actually contain, use `design-token`.
  • pattern-library — Structure a pattern entry — problem context, solution, usage examples, and related patterns. Use when documenting a recurring solution rather than a component. For a single component's API, use `component-spec`.
  • theming-system — Design theming architecture — brand variants, dark mode, and high-contrast — mapped through token layers. Use when one system must serve multiple themes. For a single palette use `color-system` (ui-design); for dark mode craft use `dark-mod
  • audit-system — Run a comprehensive audit of an existing design system for consistency, completeness, and accessibility.
  • create-component — Scaffold a full component specification end to end — props, states, variants, accessibility, and documentation.
  • tokenize — Extract tokens from an existing design or stylesheet and organise them — naming, structure, and theme mapping.
  • business-design — 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).
  • competitive-analysis — Compare UX patterns, features, strengths, and gaps across rival products. Use when you need to know what others actually do. For deliberately adopting their conventions, use `jakobs-law` (interaction-design).
  • content-strategy — Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use `ux-writing` (designer-toolkit); for structural hierarchy use `information-architecture`.
  • design-brief — Write a project brief — problem space, constraints, audience, and success criteria. Use at kickoff for one specific project. For long-horizon aspiration use `north-star-vision`; for reusable decision rules use `design-principles`.
  • design-principles — Define actionable principles that resolve trade-offs when the team disagrees. Use when the same decisions keep getting relitigated. For a single project's framing, use `design-brief`.
  • experience-map — Map the full ecosystem of touchpoints, channels, and relationships across a service. Use when the experience spans more than one product. For one persona's linear journey use `journey-map` (design-research); for backstage operations use `se
  • information-architecture — Design content structure, hierarchy, labelling, and the navigation model. Use when organising what exists. For the UI that exposes it use `navigation-patterns` (interaction-design); for user-generated grouping evidence use `card-sort-analys
  • metrics-definition — Define UX metrics and KPIs that connect design decisions to measurable outcomes. Use when choosing what to measure. For presenting the results afterwards, use `design-impact-reporting` (design-ops).

Plugins in this marketplace (33)

  • design-research — User research skills for designers: personas, empathy maps, journey maps, interview scripts, usability testing, card sorting, behavioural analytics, and reconciling data with research.
  • design-systems — Design system skills: component specs, design tokens, naming conventions, spacing and grid systems, accessibility standards, and documentation.
  • ux-strategy — UX strategy skills: information architecture, content strategy, navigation patterns, user flows, task analysis, and competitive UX audits.
  • ui-design — UI design skills: color palettes, typography systems, layout grids, responsive breakpoints, dark mode specs, visual hierarchy, and brand alignment.
  • interaction-design — Interaction design skills: micro-interactions, animation principles, state machines, gesture patterns, error handling UX, and feedback patterns.
  • prototyping-testing — Prototyping and testing skills: wireframe specs, usability heuristics, heuristic evaluations, accessibility audits, A/B test design, and benchmark analysis.
  • design-ops — Design operations skills: handoff specs, design critique facilitation, design sprint planning, team workflows, QA checklists, and design debt audits.
  • designer-toolkit — Designer utility skills: design rationale, case study structure, design presentations, UX writing, design system adoption, and design negotiation — plus the /start-here router.
  • visual-critique — Visual critique skills: hierarchy analysis, brand consistency checks against mood/voice/tokens, composition evaluation, and typography audits — with a /critique-screen command that compiles a prioritised fix list.
  • program-planning — Plan and scope UX programs: roadmaps, dependency maps, capacity planning, prioritisation.
  • stakeholder-comms — Stakeholder mapping, status reporting, executive updates, alignment workshops, escalation.
  • delivery-execution — Cycle orchestration, risk registers, blocker triage, launch readiness, retrospectives.
  • cross-functional-alignment — Intake, decision logs, working agreements, RACI, and OKR linkage across functions.
  • measurement-ops — Program health: KPIs, dashboards, research ops, design ops metrics, impact reporting.
  • process-design — How the team works: workflows, governance, rituals, scaling playbooks, retrospectives.
  • people-management — 1:1s, feedback, growth plans, performance reviews, career ladders, difficult conversations.
  • team-building — Hiring loops, job specs, portfolio review, onboarding, team topology, psychological safety.
  • design-strategy — Design vision, strategy docs, org-level principles, investment cases, portfolio prioritisation.
  • org-influence — Executive narrative, influence mapping, advocacy, securing resources, managing up.
  • operating-cadence — Design reviews at scale, planning cadence, decision frameworks, delegation, operating rhythm.
  • leadership-craft — Self-leadership, change leadership, conflict resolution, mentorship, leadership ethics.
  • model-interaction-design — Interaction patterns for AI products: mixed-initiative flow, handoff protocols, error personality.
  • ai-alignment-reasoning — Alignment reasoning and harm anticipation translated into practitioner design skills.
  • system-behavior-shaping — Shape system behaviour: defaults, guardrails, refusals, and behavioural contracts.
  • evaluation — Evaluate agentic experiences: behaviour evals, trust calibration, failure analysis.
  • design-agent-orchestration — Design how agents collaborate, hand off, and stay legible to people.
  • prompt-architecture — Structure prompts and context as a design material, not an afterthought.
  • cognitive-accessibility — Design for how people actually think: cognitive load, plain language, wayfinding, focus, memory, error recovery.
  • inclusive-interaction — Multi-modal interactions that adapt to how people move, perceive, and communicate.
  • accessible-content — Structure content that works for screen readers, cognitive differences, and diverse literacy levels.
  • inclusive-personas — User stories, personas, and scenarios that include disability from the start.
  • adaptive-interfaces — Design systems that respect user preferences and adapt to individual needs.
  • accessibility-decisions — Document, communicate, and maintain accessibility decisions across teams and time.

About this listing

Designer Skills is a community plugin on GitHub by Owl-Listener, written as a Claude Code plugin that Grok Build installs. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 40 skills, 33 plugins in this marketplaces. Its license is MIT. We checked commit 9a6930cf84a8. It's one of 144 listings in the Design category on GrokStacks.

Stacks Weekly: every new Grok Build and Codex plugin, every Tuesday.

One short email for GrokStacks and CodexStacks readers, with each new plugin's install line and what it ships. Subscribe and get the free starter list: 20 Grok Build plugins worth installing first.

You'll get a confirmation email first. Unsubscribe anytime.

Designer Skills FAQ

How do I install Designer Skills in Grok Build?

Add the repo as a marketplace with grok plugin marketplace add Owl-Listener/designer-skills, then run grok plugin install design-research@Owl-Listener/designer-skills --trust. This repo's marketplace has 33 plugins; we checked design-research, design-systems, ux-strategy. Install another the same way: grok plugin install <name>@Owl-Listener/designer-skills --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Is Designer Skills an official Grok Build plugin?

No. Designer Skills is a community plugin on GitHub by Owl-Listener, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.

What does Designer Skills include?

According to what Grok loaded in our install check, Designer Skills includes 40 skills, 33 plugins in this marketplaces: affinity-diagram, behavioural-analytics, card-sort-analysis, diary-study-plan, empathy-map, interview-script….

Details

Type
Plugin
Category
Design
Source
Community Claude Code plugin, installs in Grok
License
MIT
Author
Owl-Listener
Keywords
agentic, agentic-ai, ai, ai-tools, claude-code, design-system, design-systems, prompt-engineering, skills, ux-design
Source repo
https://github.com/Owl-Listener/designer-skills
Checked commit
9a6930cf84a8
Checked by GrokStacks
Install-checked in Grok Build on Oct 18, 2026; not run in a live session

Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.

For maintainers: badge and embeds

Maintain Designer Skills? Add the badge; it links to this page.

Listed on GrokStacks

Markdown

[![Listed on GrokStacks](https://grokstacks.com/badge.svg)](https://grokstacks.com/p/designer-skills/)

HTML

<a href="https://grokstacks.com/p/designer-skills/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>

Embed card (static HTML and inline CSS, no JavaScript). Preview:

<a href="https://grokstacks.com/p/designer-skills/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">Designer Skills</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 40 skills, 33 plugins in this marketplaces</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI…</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[Designer Skills on GrokStacks](https://grokstacks.com/p/designer-skills/)**: Community plugin for Grok Build with 40 skills, 33 plugins in this marketplaces. Install: `grok plugin install design-research@Owl-Listener/designer-skills --trust` (after `grok plugin marketplace add Owl-Listener/designer-skills`)

More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.

Also in Design

3dicon

One prompt in, a looping animated 3D icon out — with real transparency. A Claude Code skill.

Community Claude Code plugin, installs in GrokPluginDesign

3dviz Pro Max

Agent skill for creative 3D visualization: turn an idea into a Three.js/Blender scene worth exploring. Claude Code + Codex plugin, 223 recipes, 440 knowledge records, 22 proved kits, 37 runnable studies.

Community Claude Code plugin, installs in GrokPluginDesign

Adobe Premiere Pro MCP

Adobe Premiere Pro MCP. Tools for AI-driven video editing via MCP, for Codex, Claude, and other MCP clients.

Community Claude Code plugin, installs in GrokPluginDesign

Agent Sprite Forge

Agent Skill for generating 2D sprite sheets and map, transparent PNG frames, and animated GIFs from prompts.

Community Claude Code plugin, installs in GrokPluginDesign

Agent Storyboard

本地优先的 Agent 视频分镜工作台:让 Codex、Claude Code 通过 MCP 写分镜、生成图片/视频素材和配音,并自动回填。Local-first storyboard workbench for AI agents (Codex, Claude Code).

Community Claude Code plugin, installs in GrokPluginDesign

AI Business Skills

138 bilingual AI marketing skills (69 VN + 69 Global) for Claude Code, OpenCode, Codex, VS Code. Four role SOP packs — content, design, performance, leader ops — plus strategy, personal brand, AI avatar, dropshipping, design master, knowledge library. 4 regions (US/EU/SEA/LATAM) + Vietnam 2025-2026. Companion: opa-kit.

Community Claude Code plugin, installs in GrokPluginDesignNeeds sign-in

All 144 design listings →