2 378 design skills from 450 authors. They decide how things look — layout, type and interface behaviour. Half of them fit into 1 928 tokens or less — that is what one costs your context window when the agent loads it. 313 ship runnable scripts rather than instructions alone. 2 of them cannot work without an MCP server, most often rube. We also found 395 copies of these same skills sitting in other people's repositories — counted once here, not 395 times.
2 378 unique 450 authors 1 385 updated this month 178 from vendors
需求发现编排器。协调微需求检测、真需求验证、需求拆解、需求考古、好问题生成、Agent 边界设计、多元推荐改写、AI 产品三重平衡八个工具卡， 按顺序执行并输出完整的需求发现报告。自包含——八个工具卡的核心方法已内嵌。 基于《AI rebuild product needs》读者工具箱。
AI 产品三重平衡表。AI 产品设计需要在商业、人性、技术三个维度之间找到平衡。 这个 Skill 提供系统性的三重平衡评估框架。 基于《AI rebuild product needs》工具卡。
AI Native 产品方法论——价值发现循环的实操 Skill。 用户提供已上线或正在验证的 AI 产品，Skill 自动执行价值发现流程： 价值信号识别 → 伪价值排除 → 价值密度评估 → 市场测试设计 → 定价策略联动 → 方向修正建议 → 输出价值发现方案。 基于《AI Native 产品方法论》第22章。 '
AI Native 产品方法论——生产运行与循环回灌的实操 Skill。 用户提供产品已上线或即将上线，Skill 自动执行生产运行流程： 可观测性设计 → 指标体系搭建 → 失败与人工修正识别 → 反馈回灌 → 价值/商业/客户循环 → 输出生产运行方案。 基于《AI Native 产品方法论》第18-27章。 '
AI Native 产品方法论——AI Native 产品团队设计的实操 Skill。 用户提供产品阶段和团队现状，Skill 自动执行团队设计： 角色梳理 → 人机分工设计 → 能力缺口识别 → 团队协作流程 → 能力建设路径 → 输出 AI Native 团队方案。 基于《AI Native 产品方法论》第25章 AI Native 产品团队。 '
产品心理学——用户心理模型、行为设计、动机分析
AI Native 产品方法论——试验展开概述的实操 Skill。 用户提供 Direction Brief，Skill 自动执行试验展开框架设计： 资料准备评估 → 三层实验体系设计 → 评估Rubric建立 → 实验节奏规划 → 输出试验展开总体方案。 基于《AI Native 产品方法论》第06章（试验展开-概述）。 '
AI Native 产品方法论——产品形态探索的实操 Skill。 用户提供能力实验结论，Skill 自动执行产品形态探索： 能力边界分析 → 交互原型设计 → 工作流嵌入测试 → 产品形态判断 → 输出产品形态建议。 基于《AI Native 产品方法论》第07章（试验展开-产品形态探索）。 '
AI Native 产品方法论——流程重构与任务设计的实操 Skill。 用户提供产品形态建议，Skill 自动执行流程重构设计： 任务拆解 → 人机协作模式选择 → 工作流设计 → 节点标注 → 验证与迭代 → 输出流程重构方案。 基于《AI Native 产品方法论》第08章（试验展开-流程重构与任务设计）。 '
AI Native 产品方法论——记忆系统设计的实操 Skill。 用户提供产品场景，Skill 自动执行记忆系统设计流程： 记忆需求分析 → 记忆分类设计 → 权限与时效策略 → 存储与索引 → 人工修正与再沉淀 → 输出记忆系统方案。 基于《AI Native 产品方法论》第13章。 '
AI Native 产品方法论——影子验证的实操 Skill。 用户提供收敛决策结论，Skill 自动执行影子验证： 影子系统设计 → 并行运行方案 → 人工对比机制 → 失败模式沉淀 → 审计放行证据 → 输出影子验证报告。 基于《AI Native 产品方法论》第10章（试验展开-影子验证）。 '
AI Native 产品方法论——系统构建阶段的总论 Skill。 用户提供实验结论报告，Skill 自动执行系统构建流程： 实验证据输入 → 系统边界定义 → 能力模块设计 → 治理与观测补齐 → 输出系统构建方案。 基于《AI Native 产品方法论》第11章。 '
AI Native 商业模式设计 Skill。基于《AI确定性商业模式》方法论， 帮助用户设计以"确定性溢价"为核心的 AI 商业模式： 避开6种失效模式，选择4种确定性模型，构建可持续的收费逻辑。
仲裁者模式设计器。设计以"真相即服务"为核心的商业模式： 提供可验证的真实信息和判断，让用户相信每个数字都是真的。 基于《AI确定性商业模式》概念卡。
确定性溢价计算器。基于《AI确定性商业模式》核心公式， 帮助产品团队计算 AI 产品的确定性溢价，从而设计更高价值的收费模式。
保险模式设计器。设计以"结果担保"为核心的商业模式： 为 AI 的输出结果提供担保，出错则赔偿或免费。 基于《AI确定性商业模式》概念卡。
预测套利设计器。设计以"超越人类预测能力"为核心的商业模式： 在 AI 预测能力强于人类的领域进行套利，将预测优势转化为商业价值。 基于《AI确定性商业模式》概念卡。
意图预测营销设计器。基于《AI Native 营销与增长》意图预测营销概念卡， 帮助产品从"人群定向"升级为"个体预见"——在用户明确表达之前就提供相关内容。
AI Native 产品方法论——审计放行阶段的实操 Skill。 用户提供系统构建方案，Skill 自动执行审计放行流程： 设计证据 → 评估证据 → Shadow 证据 → 放行边界判断 → go/no-go 决策 → 输出放行方案。 基于《AI Native 产品方法论》第17章。 '
AI Native 产品方法论——客户循环的实操 Skill。 用户提供 AI 产品阶段和目标客户画像，Skill 自动执行客户循环设计： 早期客户筛选 → 共创边界设计 → 反馈收集机制 → 产品改进回路 → 客户扩张策略 → 方法论回流 → 输出客户循环方案。 基于《AI Native 产品方法论》第24章。 '
预测性留存设计器。基于《AI Native 营销与增长》预测性留存概念卡， 帮助产品从"流失后挽回"升级为"流失前阻止"——在用户流失之前主动干预。
AI Native 产品方法论——AI Native 用户体验设计的实操 Skill。 用户提供产品场景，Skill 自动执行 UX 设计流程： 任务分析 → 人机分工设计 → 状态可见性 → 纠偏机制 → 信任设计 → 反馈沉淀 → 输出 UX 方案。 基于《AI Native 产品方法论》第16章。 '
渐进式披露清单。基于《AI时代的用户体验》渐进式披露理论， 提供 AI 产品逐步展示功能和能力的设计清单，避免一次性向用户交付过多信息。
信任度分级设计器。基于《AI时代的用户体验》信任分级理论， 设计 AI 产品的信任度分级体系，让用户渐进式地建立对 AI 的信任。
Elite UI/UX Design Lead & Frontend Architect. Generates distinctive, non-templated interfaces with opinionated aesthetics, deliberate typography, and exact UX copy. Triggers on UI design, frontend styling, or layout creation.
Elite UI/UX Design Lead & Frontend Architect. Generates distinctive, non-templated interfaces with opinionated aesthetics, deliberate typography, and exact UX copy. Triggers on UI design, frontend styling, or layout creation.
Custom Instructions: HTML5 & CSS3 Responsive Design Expert
Analyze user/customer feedback into a Feedback Analysis Pack (taxonomy, themes, recommendations). See also: conducting-user-interviews (collect new), designing-surveys (quantitative).
Build or evolve a design system: charter, token model, component inventory, governance plan.
备份策略设计
Converts UX/design intent into testable design specifications that feed requirements. Use when defining user flows, accessibility, or design constraints.
>- Test for WCAG 2.2 AA compliance with axe-core + Playwright, keyboard navigation audits, screen reader testing, ARIA pattern validation, and legal compliance mapping (ADA, EAA, Section 508). Automated tools catch 30-40% of issues — this skill covers automated and "keyboard navigation," "ARIA," "ADA compliance." regression — use visual-testing.
Launch and operate a local Codex drawing workspace: a lightweight vector board where the user and Codex share editable scene state through a browser UI, workspace-backed JSON, local API mutations, and SVG export. Use when the user wants to draw, edit, inspect, generate, refine, or export simple vector artifacts such as logos, icons, diagrams, badges, layout sketches, SVG assets, or visual scratchpad scenes.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
>- The moi workspace — the web UI the user chats from, extended with agent-authored applets (widgets, views) plus theme & config. Read this FIRST in two cases. (a) A message carries a hidden nothing else says so. (b) The user uses moi vocab — workspace, applet, widget, view, scratchpad, dashboard, or a `moi` command — or asks to build, edit, customize, or theme the workspace UI or its layout.
Use this agent when you need to verify that a UI implementation matches its Figma design specifications. This agent should be called after code has been written to implement a design, particularly after HTML/CSS/React components have been created or modified. The agent will visually compare the live implementation against the Figma design and provide detailed feedback on discrepancies.\\n\\nExamples:\\n- <example>\\n Context: The user has just implemented a new component based on a Figma design.\\n user: \"I've finished implementing the hero section based on the Figma design\"\\n assistant: \"I'll review how well your implementation matches the Figma design.\"\\n <commentary>\\n Since UI implementation has been completed, use the design-implementation-reviewer agent to compare the live version with Figma.\\n </commentary>\\n </example>\\n- <example>\\n Context: After the general code agent has implemented design changes.\\n user: \"Update the button styles to match the new design system\"\\n assistant: \"I've updated the butto...
Use this agent PROACTIVELY when design work isn't coming together on the first attempt. If you've made 1-2 design changes and the result still feels off, suggest using this agent with 5x or 10x iterations for deeper refinement. This agent takes screenshots, analyzes what's not working, implements improvements, and repeats N times to systematically fix design issues. Perfect when colors feel wrong, layouts aren't balanced, or the overall aesthetic needs work that single changes can't achieve. <example>Context: User asks to change button color but result still looks off. user: \"Change the button to blue\" assistant: [makes change, takes screenshot] \"The button is now blue, but I notice the overall color balance still feels off. Would you like me to use the design-iterator agent with 5 iterations to systematically improve the color harmony and visual balance?\" <commentary>PROACTIVE USE: After a simple change doesn't fully resolve the design issue, suggest the design-iterator to do deeper work.</commentary></ex...
Use this agent when you need to synchronize a web implementation with its Figma design by automatically detecting and fixing visual differences. This agent should be used iteratively until the implementation matches the design.\\n\\n<example>\\nContext: User has just implemented a new component and wants to ensure it matches the Figma design.\\nuser: \\\"I've just finished implementing the hero section component. Can you check if it matches the Figma design at https://figma.com/file/abc123/design?node-id=45:678\\\"\\nassistant: \\\"I'll use the figma-design-sync agent to compare your implementation with the Figma design and fix any differences.\\\"\\n<uses Task tool to launch figma-design-sync agent with the Figma URL and local URL>\\n</example>\\n\\n<example>\\nContext: User is working on responsive design and wants to verify mobile breakpoint matches design.\\nuser: \\\"The mobile view doesn't look quite right. Here's the Figma: https://figma.com/file/xyz789/mobile?node-id=12:34\\\"\\nassistant: \\\"Let me use the figma-design-sy...
This skill should be used when creating distinctive, production-grade frontend interfaces with high design quality. It applies when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Create distinctive, production-grade terminal user interfaces with high design quality. Use this skill when the user asks to build CLI tools, TUI applications, or terminal-based interfaces. Generates creative, polished code that avoids generic terminal aesthetics.
Use when designing or reviewing web UI, implementing forms/buttons/inputs, fixing visual hierarchy issues, creating color systems, building layouts, or when interface feels cluttered, hard to read, or users don't know what to click.
Decode garbled Russian/English wrong-keyboard-layout text (ЙЦУКЕН/QWERTY).
> Inspect, build, or extend Figma design systems — and optionally sync them to component scoring, detached instance detection, handoff docs) and build mode (creating components with variable bindings, slot-based composition, structured descriptions, validation, and optional export of tokens.css + AI rules to the user's codebase). Use when the user says 'audit my design system', 'check component quality', 'create design system', 'build DS in Figma', 'generate component library', 'add slots to my components', 'sync design tokens from code', 'find detached instances', 'check WCAG compliance', 'export tokens to code', 'generate CLAUDE.md for design system', or wants to push a design system from code to Figma or back. The skill auto-detects the mode from request, or asks if unclear. After inspect, ALWAYS pauses and waits for explicit user decision before any build action. Phase 6 (sync to code) is OFF by default — only triggers on explicit user request. Does NOT implement Figma designs as code — use figma-implement-design for that. Does NOT create individual screens — use figma-generate-design for that.
Comprehensive SwiftUI accessibility audit against Apple HIG. Checks VoiceOver labels, Reduce Motion, Dynamic Type, color contrast, and accessible controls. Use before App Store submission or when adding new UI.
Audit for performance and battery - layout thrash, heavy animations, timers, background tasks. Identifies hotspots affecting smoothness and power consumption. Use before releases or when users report lag/battery drain.
HIG-first visual design audit for SwiftUI. Covers color systems, contrast, typography, spacing, icons, and accessibility visuals.
Conduct accessibility audits against WCAG 2.2 guidelines. Evaluate pages, components, and flows for conformance at A, AA, and AAA levels. Identify issues, assess severity, provide code fixes, and generate audit reports. Covers automated testing, manual testing, keyboard navigation, screen reader compatibility, color contrast, and semantic HTML.
Evaluate UI designs against usability heuristics, UX laws, interaction patterns, interaction design principles, information architecture, and content quality. Conduct heuristic evaluations, structured design critiques, pattern-based reviews, posture analysis, excise audits, IA evaluations, and UX writing reviews. Provides specific, actionable feedback grounded in established principles rather than subjective opinion.