原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

designer-skills Skill

代码仓库 ↗

作者:Owl-Listener★ 3,420 (整个仓库)107 个 skill

★ 星标是整个仓库的,不是每个 Skill 的

选择要安装的 Skill

能做什么

此仓库是合集,包含 107 个 Skill;它是汇总多个来源 Skill 的清单

  • 连接方式 供 AI 读取的指令文件
  • 账号或密钥 README 和 SKILL.md 中未发现密钥
  • 分类 设计与网页
作者的原始说明
Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery.
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/owl-listener-designer-skills.svg)](https://mcp.popnx.com/en/skills/owl-listener-designer-skills)

可搭配使用

在同一工作中把 AI 连到服务的 MCP

Next AI Draw.io

draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand

作者:DayuanJiang广泛使用↓ 2.2万/周★ 3.7万 整个仓库的星标6天前更新

MCP · 连接服务在你的电脑上运行

Pascal 3D Editor

Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.

作者:pascalorg广泛使用↓ 1037/周★ 2.6万 整个仓库的星标前天更新

MCP · 连接服务电脑或云端✓ 服务方 · pascal.app

Semiotic

Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.

作者:nteract广泛使用↓ 8456/周★ 2717昨天更新

MCP · 连接服务电脑或云端

相似的 Skill

同类工作,排序与 Skill 列表相同

与相似项目对比
本项
designer-skills
impeccablediagram-designfrontend-slidesguizang-ppt-skill
作者Owl-Listenerpbakauscathrynlaveryzarazhangruiop7418
Skill 数1071111
GitHub 星标3,420113,04268,29632,57930,091
最近代码更新2026年9月5日2026年11月19日2026年11月19日2026年6月24日2026年10月30日
许可证MITApache-2.0MITMITAGPL-3.0

Owl-Listener 提供的 107 个 Skill(指令集),AI 读取后照做 · 不是 MCP server

选择要安装的 Skill

只安装你真正会用的。点开名称查看该 Skill 的安装方法

这个合集有 107 个 Skill,太多了不适合全部安装:每个 Skill 的说明都会载入每次对话,AI 更容易选错。请从下方列表只选你会用的

显示 107 个中的 30 个 在 GitHub 查看全部

  • 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 `accessibility-test-plan` (prototyping-testing).

  • 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`.

  • 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).

  • 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-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`.

  • 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-control-strategy` (design-ops).

  • 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 `theming-system`.

  • 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`.

  • 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`.

  • 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`.

  • 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).

  • 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).

  • 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-flow-diagram` (prototyping-testing).

  • layout-grid

    Define a responsive grid — columns, gutters, margins, and breakpoint behaviour. Use when establishing page structure. For the spacing scale inside components use `spacing-system`; for cross-device behaviour use `responsive-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-design).

  • 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).

  • 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`.

  • 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`.

  • 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).

Skill 和 MCP 有什么不同

MCP = 手

把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。

Skill = 手册

教 AI 怎么做某项工作的文本文件,不连接任何服务。

有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。

适用的应用

Claude CodeGemini CLI

依据开发者 README 和 repo 中的文件夹

安装

请先选择 Skill

此仓库有 107 个 Skill。请从上方列表选一个,该 Skill 的页面有完整安装方法,包括让 AI 安装和 ZIP 文件

让 AI 帮你安装
上传到 claude.ai

前往 Skill 列表 ↑

作者的命令会安装整套 107 个
/plugin marketplace add Owl-Listener/designer-skills
/plugin install ux-strategy@designer-skills

摘自开发者 README,会下载并运行开发者的代码

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

来自 GitHub

GitHub 星标
3,420
星标是整个仓库的,不是每个 Skill 的
开发者
Owl-Listener
许可证
MIT
最近代码更新
2026年9月5日
repo 中的 SKILL.md 文件(含译本和模板)
30
主题
agentic, agentic-ai, ai, ai-tools, claude-code, design-system, design-systems, prompt-engineering, skills, ux-design