Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Mit Google anmelden, um Bewertungen zu schreiben.Prototyp · alle 30 Min. aktualisiert
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

designer-skills Skill

Repository ↗

von Owl-Listener★ 3.420 (whole repo)107 Skills

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 107 skills; it is a curated list of skills from many sources

  • Connects Instruction files the AI reads
  • Account or key No key found in README or SKILL.md
  • Category Design und Web
Maker’s original description
Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery.
Für Anbieter: Badge ins README

Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.

[![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)

Zusammen nutzen mit

MCP-Server, die die KI für dieselbe Arbeit mit Diensten verbinden

Next AI Draw.io

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

von DayuanJiangWeit verbreitet↓ 21.676/Wo.★ 37.054 Sterne des ganzen ReposAktualisiert vor 5 Tagen

MCP · Verbindet einen DienstLäuft auf deinem Computer

Pascal 3D Editor

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

von pascalorgWeit verbreitet↓ 1037/Wo.★ 25.617 Sterne des ganzen ReposAktualisiert gestern

MCP · Verbindet einen DienstComputer oder Cloud✓ vom Dienst · pascal.app

Semiotic

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

von nteractWeit verbreitet↓ 8456/Wo.★ 2717Aktualisiert heute

MCP · Verbindet einen DienstComputer oder Cloud

Ähnliche Skills

Gleiche Art Arbeit, sortiert wie die Skill-Liste

Im Vergleich mit ähnlichen
Dieser
designer-skills
impeccablediagram-designfrontend-slidesguizang-ppt-skill
AnbieterOwl-Listenerpbakauscathrynlaveryzarazhangruiop7418
Skills1071111
GitHub-Sterne3.420113.04268.29632.57930.091
Letzte Codeänderung5. Sept. 202619. Nov. 202619. Nov. 202624. Juni 202630. Okt. 2026
LizenzMITApache-2.0MITMITAGPL-3.0

107 Skills (Anweisungssammlungen) von Owl-Listener, die eine KI liest und befolgt · kein MCP-Server

Pick the skill to install

Install only the ones you use. Open a skill to see how to install it

This set has 107 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below

Showing 30 of 107 See all on 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).

Was einen Skill von MCP unterscheidet

MCP = die Hände

Verbindet die KI mit einem externen Dienst oder Daten, etwa Notion lesen oder eine Rechnung erstellen. Ein Programm oder Server muss laufen.

Skill = das Handbuch

Eine Textdatei, die der KI zeigt, wie eine Aufgabe geht. Sie verbindet sich mit nichts.

Manches überschneidet sich: Einige Skills starten Skripte mit Werkzeugen, einige MCP-Server liefern nur Wissen. Geh von der Aufgabe aus.

Funktioniert mit

Claude CodeGemini CLI

Laut README des Anbieters und den Ordnern im Repo

Installieren

Pick a skill first

This repo has 107 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP

Let the AI install it
Upload to claude.ai

Go to the skill list ↑

The maker’s command installs the whole set of 107
/plugin marketplace add Owl-Listener/designer-skills
/plugin install ux-strategy@designer-skills

Aus dem README des Anbieters; lädt den Code des Anbieters herunter und führt ihn aus

Diskussion

Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.

Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.

Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.

Anmelden, um zu posten

Von GitHub

GitHub-Sterne
3.420
Stars are for the whole repo, not each skill
Anbieter
Owl-Listener
Lizenz
MIT
Letzte Codeänderung
5. Sept. 2026
SKILL.md-Dateien im Repo (mit Übersetzungen und Vorlagen)
30
Themen
agentic, agentic-ai, ai, ai-tools, claude-code, design-system, design-systems, prompt-engineering, skills, ux-design