Agent Skill 目录与安装教程 — ClawHub、SkillsMP 与开源 Skill

vercel-react-view-transitions

io.github.vercel-labs/agent-skills/react-view-transitions

Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.

vercel-react-native-skills

io.github.vercel-labs/agent-skills/react-native-skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

vercel-react-best-practices

io.github.vercel-labs/agent-skills/react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

io.clawhub.ireact2code/ui-ux-pro-max-plus

Professional UI/UX design resource library with searchable design patterns, color palettes, font pairings, chart types, and UX guidelines.

io.github.runceel/ReactiveProperty/writing-mstest-tests

Best practices for writing new MSTest 3.x/4.x unit tests and implementing concrete fixes in existing MSTest code. Use when the user asks to write, create, implement, repair, or modernize tests (including fix-it prompts such as 'something seems off, fix issues'). Primary fit for direct code changes like correcting swapped Assert.AreEqual argument order, replacing outdated assertion patterns, and converting DynamicData from IEnumerable<object[]> to ValueTuple-based data sets. Covers modern assertions, data-driven tests, test lifecycle, MSTest.Sdk, sealed classes, Assert.Throws, DynamicData with ValueTuples, TestContext, and conditional execution. Do NOT use for broad test quality audits, flaky-test investigations, or test smell detection reports — use test-anti-patterns instead.

io.github.react/react/rust-port-status

Show the status of all Rust port plan documents and recent related commits. Use when you need to understand what's been done vs what remains.

io.github.react/react/plan-update

Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.

io.github.react/react/compiler-verify

Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.

io.github.react/react/compiler-port

Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.

io.github.react/react/compiler-orchestrator

Orchestrate the Rust compiler port end-to-end. Discovers the current frontier, fixes failing passes, ports new passes, reviews, and commits in a loop.

io.github.react/react/compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.

io.github.react/react/compiler-review

Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.

io.github.millionco/react-doctor/writing-guidelines

Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".

io.github.software-mansion/react-native-audio-api/writing-skills

How to write, structure, and maintain Claude skill files. Covers the three-level progressive disclosure model, all YAML frontmatter fields (context:fork, allowed-tools, disable-model-invocation, user-invocable, hooks, argument-hint), invocation control patterns, string substitutions ($ARGUMENTS, ${CLAUDE_SKILL_DIR}), shell preprocessing with backtick syntax, and the Maintenance section contract. Use when creating a new skill file, rewriting an existing one, or reviewing a skill for quality. Trigger phrases: "add a skill", "write a skill", "create a skill file", "update skill", "skill quality", "skill review", "context fork", "allowed-tools", "user-invocable".

io.github.marsidev/react-turnstile/nextjs-ssr

Integrate Turnstile with Next.js, handle SSR, hydration, and App Router. Activate when building Next.js applications with App Router or Pages Router, or when encountering SSR-related errors.

io.github.react/react/verify

Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

io.github.react/react/test

Use when you need to run tests for React core. Supports source, www, stable, and experimental channels.

io.github.react/react/flow

Use when you need to run Flow type checking, or when seeing Flow type errors in React code.

io.github.react/react/flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

io.github.react/react/fix

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

io.github.react/react/feature-flags

Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.

io.github.react/react/extract-errors

Use when adding new error messages to React, or seeing "unknown error code" warnings.