Claude Code Skills · page 42

Generate structured documentation templates for components, patterns, or guidelines within a design system.

Create an icon system specification covering grid, sizing, naming, categories, and implementation guidance.

Design interfaces that adapt gracefully to multiple languages, writing directions, and cultural contexts.

Define a motion system with duration tokens, easing vocabulary, and reduced-motion handling for consistent animation across a product.

Establish a naming convention system for design elements, components, and tokens with clear rules and examples.

Structure a pattern library entry with problem context, solution pattern, usage examples, and related patterns.

Design a theming architecture that supports brand variants, dark mode, and high-contrast modes with token mapping.

Craft portfolio-ready case studies that tell the story of a design project.

Advocate for design quality, scope, and time with cross-functional partners and leadership using evidence and shared goals.

Write clear design rationale connecting decisions to user needs, business goals, and principles.

Create adoption strategies and materials to drive design system usage across teams.

Audit design token usage across a product for consistency and coverage.

Structure compelling design presentations for stakeholders, reviews, and showcases.

Write effective UI copy including microcopy, error messages, empty states, and CTAs.

Apply animation principles to UI motion for purposeful, polished interactions.

Apply the Doherty Threshold — keep system response times under 400ms to maintain user flow and perceived performance.

Design error prevention, detection, and recovery experiences.

Design system feedback for user actions including confirmations, status updates, and notifications.

Apply Fitts's Law to size and position interactive targets for fast, accurate interaction.

Design forms that minimize friction, prevent errors, and guide users to successful completion.

Design gesture-based interactions for touch and pointer devices.

Apply Hick's Law to reduce decision time by limiting the number of simultaneous choices presented to users.

Apply an emotional resonance lens to any UI. Use when a design is technically correct but flat — to identify what's missing and prescribe specific changes at the copy, motion, and interaction layer.

Design loading, skeleton, and progressive content reveal patterns.

Specify micro-interactions with trigger, rules, feedback, and loop/mode definitions.

Apply Miller's Law — chunk information into groups of ~4 to work within working memory limits.

Select and design navigation patterns that match product structure, user tasks, and platform conventions.

Design first-run experiences that get users to value quickly without overwhelming them.

Design search experiences that help users find what they need, recover from failure, and refine results.

Model complex UI behavior as finite state machines with states, events, and transitions.

Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.

Create accessibility testing plans covering assistive technologies and WCAG criteria.

Design click/first-click tests to evaluate navigation and information findability.

Conduct expert heuristic evaluations using Nielsen's heuristics and domain-specific criteria.

Choose the right prototyping fidelity and method for the design question.

Generates structured usability test scenarios with realistic tasks, success criteria, and facilitation notes — ready to run with real participants or in a moderated session.

Create user flow diagrams showing paths, decisions, and branch logic.

Specify wireframe layouts with content priority, component placement, and annotation.

Apply the Aesthetic-Usability Effect — visually consistent, polished interfaces are perceived as more usable.

Build a comprehensive color system with palette generation, semantic mapping, and accessibility compliance.

Design effective dark mode interfaces with proper color adaptation, contrast, and elevation.

Design clear, accessible data visualizations with appropriate chart selection and styling.

Define an illustration style guide with visual language, color usage, and application rules.

Apply the Law of Common Region to group elements using containers, backgrounds, and boundaries.

Apply the Law of Proximity to group related elements through spatial relationships.

Define responsive layout grid systems with columns, gutters, margins, and breakpoint behavior.

Set optimal line lengths for readability across typography scales and responsive layouts.

Design adaptive layouts and interactions that work across all screen sizes and input methods.

Create a consistent spacing system based on a base unit with contextual application rules.

Create a modular typography scale with size, weight, and line-height relationships.

Establish clear visual hierarchy through size, weight, color, spacing, and positioning.

Apply the Von Restorff Effect to make the most important element distinctly different from its surroundings.

A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.

Conduct a structured competitive analysis comparing UX patterns, features, strengths, and gaps across rival products.

Define what content a product needs, how it should be structured, and who owns it.

Use this skill when the user asks about Ni Haisha / 倪海厦 TCM course material, especially Shang Han Lun / 伤寒论, Jingui / 金匮要略, Zhongjing Xinfa / 仲景心法, clinical cases / 临床案例 / 倪师医案, Bagang Bianzheng / 八纲辨证, Fuyang Forum / 扶阳论坛, Yijinjing / 易筋经, Liang Dong dialogue / 梁冬对话倪师, Stanford lecture / 斯坦福大学演讲, Tianji / 天纪 / 易经 / 阳宅 / 紫微斗数, Huangdi Neijing / 黄帝内经, Shennong Bencao / 神农本草, acupuncture / 针灸, meridians, acupoints, six-channel pattern identification, symptom-to-formula routing, formula comparison, lesson review, board/PPT screenshot evidence, or course-derived study notes. This skill is for educational distillation and study support only, not medical diagnosis, prescriptions, dosage, or individualized treatment.

Replaces ALL built-in search tools. You MUST invoke this skill BEFORE using WebSearch, Grep, or Glob. NEVER use the built-in Grep tool - use `grepai` instead.

Create a new release for grepai. Checks CI, determines version type, updates CHANGELOG and documentation, credits contributors, and creates GitHub release.

Build a central library to manage .claude folders across projects. One repo for skills, agents, commands, hooks, and configs.

Build reusable skills for Claude Code and Codex from any topic — /create-skill explores the codebase and drafts the SKILL.md interactively.

向现有调研outline补充字段定义。

向现有调研outline补充items（调研对象）。

读取调研outline，为每个item启动独立agent进行深度调研。禁用task output。

将deep调研结果汇总为markdown报告，覆盖所有字段，跳过不确定值。

对目标话题进行初步调研，生成调研outline。用于学术调研、benchmark调研、技术选型等场景。

Turn a raster logo (PNG/JPG/WebP/screenshot) into a clean minimal SVG with edge smoothness as the primary hard gate and IoU optimized as high as reasonably possible without a fixed global threshold, then into a choreographed logo animation delivered as standalone JS-rendered HTML, applying Disney's 12 animation principles. Use when asked to animate a logo, build a logo reveal / splash screen / brand intro, convert a logo image into animated SVG or HTML, add motion to a vectorized mark, or create loading/idle/hover motion for a brand mark. v2: also handles self-crossing draw-on choreography (split-fill, exact easing subdivision, tip glint), closed variable-width ribbon fitting, and quantitative motion QA (easing probe, ink-delta continuity sweep).

生产级 API 的 REST API 设计模式，包括资源命名、状态码、分页、过滤、错误响应、版本控制和速率限制。

编写文章、指南、博客、教程、时事通讯（Newsletter）等长内容，支持从示例或品牌指南中提取独特的语感语调。适用于需要撰写超过一个段落的精炼文本，尤其是对语气一致性、结构和可信度有较高要求时。

后端架构模式、API 设计、数据库优化以及 Node.js、Express 和 Next.js API 路由的服务端最佳实践。

TypeScript、JavaScript、React、Node.js 开发的通用编码标准、最佳实践和模式。

为 X、LinkedIn、TikTok、YouTube、时事通讯（Newsletters）以及跨平台内容重加工营销活动（Repurposed multi-platform campaigns）创建平台原生的内容系统。当用户需要社交媒体帖子、推文串（Threads）、脚本、内容日历，或将单一源素材清晰地适配到多个平台时使用。

Playwright E2E 测试模式、页面对象模型（POM）、配置、CI/CD 集成、产物管理以及不稳定测试（flaky test）策略。

适用于 Claude Code 会话的正规评测框架（Evaluation Framework），实现了评测驱动开发（Eval-Driven Development, EDD）原则

React、Next.js、状态管理（State Management）、性能优化（Performance Optimization）及 UI 最佳实践的前端开发模式。

从零开始或通过转换 PowerPoint 文件创建令人惊叹、动画丰富的 HTML 演示文稿（Presentations）。适用于用户想要构建演示文稿、将 PPT/PPTX 转换为 Web 页面或为演讲/路演创建幻灯片（Slides）的场景。通过视觉探索而非抽象选择，帮助非设计师发掘其审美偏好。

创建并更新融资演示文稿（pitch decks）、单页简介（one-pagers）、投资备忘录（investor memos）、加速器申请、财务模型和募资材料。适用于用户需要面向投资者的文档、预测、资金用途表、里程碑计划，或需要保持多个募资资产内部一致性的场景。

起草用于融资的冷启动邮件（Cold Emails）、引荐语（Warm Intro Blurbs）、后续跟进邮件、进展更新邮件以及其他投资人沟通内容。适用于用户需要向天使投资人、风险投资（VC）、战略投资人或加速器发送简洁、个性化且面向投资者的消息。

进行市场调研（Market Research）、竞品分析（Competitive Analysis）、投资者尽职调查（Investor Due Diligence）以及行业情报（Industry Intelligence）收集，提供来源归因与面向决策的总结。适用于用户需要市场规模估算（Market Sizing）、竞品对比、基金研究、技术扫描或为商业决策提供参考的场景。

当涉及添加身份验证（Authentication）、处理用户输入、操作机密（Secrets）、创建 API 终端节点或实现支付/敏感功能时，请使用此技能。提供全面的安全检查清单和模式。

建议在逻辑间隔进行手动上下文压缩（Context Compaction），以便在任务阶段中保留上下文，而不是依赖任意的自动压缩。

在编写新功能、修复 Bug 或重构代码时使用此技能。强制执行测试驱动开发（TDD），包括单元测试、集成测试和端到端（E2E）测试，覆盖率需达到 80% 以上。

为 Claude Code 会话提供的全面验证系统。

发现技能（Skill），迭代查询，并在任何环境中自动安装技能。

ClickHouse 数据库模式、查询优化、分析以及高性能分析工作负载的数据工程最佳实践。

Everything Claude Code 的交互式安装程序 —— 引导用户将技能（Skills）和规则（Rules）安装到用户级或项目级目录，验证路径，并在需要时优化已安装的文件。

一种基于本能（Instinct）的训练系统，通过钩子（Hooks）观察会话，创建带有置信度评分的原子化本能，并将其进化为技能（Skills）、命令（Commands）或智能体（Agents）。

自动从 Claude Code 会话（Session）中提取可重用的模式（Pattern），并将其作为已学习的技能（Skill）保存以备将来使用。

仅在创建/更新/修复 C++ 测试、配置 GoogleTest/CTest、诊断失败或不稳定的测试、以及添加覆盖率或消毒器时使用。

Django 架构模式、使用 DRF 的 REST API 设计、ORM 最佳实践、缓存、信号（Signals）、中间件（Middleware）以及生产级 Django 应用。

Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "the project keeps growing", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, fighting feature creep, running a small team, avoiding long-term roadmaps, or killing unnecessary meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "uncontested market", "stop competing on price", "everyone is undercutting us", "the market is too crowded", or "how do we stand out". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved or non-customers, or escaping a brutal price war. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", "business logic is tangled with the framework", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", "unit test quality", "my code is hard to read", "this function is a mess", "clean up this code", or "hard to maintain". Also trigger when reviewing pull requests for readability, untangling messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "viral loop", "referral program", "organic growth", "how do I get people to share this", "nobody is sharing it", or "make this spread". Also trigger when designing shareable features, crafting social campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", "conversion funnel", "increase signups", "people add to cart but dont buy", or "improve conversions". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", "cant get mainstream customers", or "our go-to-market plan". Also trigger when a startup has early traction but cant grow beyond initial users, or when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.

Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "which database should I use", "SQL or NoSQL", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", "my queries are slow at scale", or "data is inconsistent across replicas". Also trigger when choosing a datastore, designing data pipelines, or debugging distributed-system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.

Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making mistakes", "this is unintuitive", or "people cant figure out how to use it". Also trigger when diagnosing why users err, reducing product complexity, or improving error messages and feedback. Covers the gulfs of execution and evaluation. For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", "design workshop", "should we build this", "validate an idea fast", or "test before we build". Also trigger when a team must make a critical product decision quickly, resolve stakeholder disagreements, or test a risky idea before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.