Published on

AI-Skills

Authors

Skill 规范

agentskills - SKILL 的统一规范

Skill 编写

add-skill

一个用于为编码智能体(如 OpenCode、Claude Code、Codex 和 Cursor)安装技能的命令行工具。技能通过包含 YAML 前言的 SKILL.md 文件定义,可扩展智能体的功能,例如生成发布说明或集成外部工具。工具支持从 GitHub、GitLab 等源码安装,并提供全局或项目级安装选项。

Skill_Seekers - 制作 skill 的工具

claude-skills - 生成 skill 的 skill - 元 skill

skill-prompt-generator - 基于 Claude Code Skills 的智能提示词生成系统

Skill 广场

skills.sh
Vercel - 技能是 AI 代理可重复使用的能力。通过单一命令安装,即可为您的代理增强程序性知识的访问能力。

skillshunt

前端 Skills

dev-browser 一个 Claude 技能,赋予您的代理使用网页浏览器的能力。

react-best-practices
来自 Vercel Engineering 的 React 与 Next.js 性能优化综合指南,包含 8 大类、40 多条按影响优先级排序的规则,旨在为编写、审查和重构代码提供最佳实践

ui-ux-pro-max-skill

编程 Skills

rewrite
OpenRewrite 是一个开源自动化代码重构生态系统,旨在帮助开发者高效消除技术债务,其商业平台 Moderne 支持大规模、跨仓库的代码转换与协作。

openskills
OpenSkills 是一个开源工具,旨在将 Anthropic(Claude Code)的技能系统推广到所有 AI 编程代理(如 Cursor、Windsurf、Aider)。

oai-skills ChatGPT 代码解释器环境中/home/oai/skills 目录的内容

anthropics-skills

awesome-claude-skills

claudekit-skills - gemini mcp sub-agent

Agent-Skills-for-Context-Engineering

pg-aiguide
pg-aiguide 是一个专为 AI 编程助手优化的 PostgreSQL 专业知识工具,旨在帮助 AI 工具生成更高质量、更符合现代最佳实践的 PostgreSQL 代码。它通过语义搜索官方文档和提供 AI 优化的“技能”来实现这一目标。

awesome-agent-skills

planning-with-files Claude 代码技能实现 Manus 式持久化 Markdown 规划——这一工作流模式曾促成 20 亿美元收购案。

whenwords
whenwords 是一个无代码的开源库,提供相对时间格式化的功能,支持多种编程语言。它通过详细的规范文档和通用测试用例,让开发者能借助 AI 工具快速生成符合要求的本地化实现。

agent37-skills-collection
Claude AI 实用技能和指令集锦

everything-claude-code
这是一个由 Anthropic 黑客松获奖者整理的完整 Claude Code 配置集合,包含经过实战检验的代理、技能、钩子、命令、规则和 MCP 配置。

编程 SDD(Specification Driven Development)

compound-engineering-plugin
官方 Claude 代码复合工程插件

superpowers
一个行之有效的智能技能框架与软件开发方法论。

spec-kit
💫 助你开启规范驱动开发之旅的工具包

通用科学 Skill

claude-scientific-skills - 即用型科学技能

通用技能 Skill

Humanizer-zh: AI 写作去痕工具(中文版)

ceo-skill

个人 skill 收集

antfu/skills

GuDaStudio-skills

UI Skills

https://www.ui-skills.com/

---
name: ui-skills
description: Opinionated constraints for building better interfaces with agents.
---

# UI Skills

Opinionated constraints for building better interfaces with agents.

## Stack

- MUST use Tailwind CSS defaults (spacing, radius, shadows) before custom values
- MUST use `motion/react` (formerly `framer-motion`) when JavaScript animation is required
- SHOULD use `tw-animate-css` for entrance and micro-animations in Tailwind CSS
- MUST use `cn` utility (`clsx` + `tailwind-merge`) for class logic

## Components

- MUST use accessible component primitives for anything with keyboard or focus behavior (`Base UI`, `React Aria`, `Radix`)
- MUST use the project’s existing component primitives first
- NEVER mix primitive systems within the same interaction surface
- SHOULD prefer [`Base UI`](https://base-ui.com/react/components) for new primitives if compatible with the stack
- MUST add an `aria-label` to icon-only buttons
- NEVER rebuild keyboard or focus behavior by hand unless explicitly requested

## Interaction

- MUST use an `AlertDialog` for destructive or irreversible actions
- SHOULD use structural skeletons for loading states
- NEVER use `h-screen`, use `h-dvh`
- MUST respect `safe-area-inset` for fixed elements
- MUST show errors next to where the action happens
- NEVER block paste in `input` or `textarea` elements

## Animation

- NEVER add animation unless it is explicitly requested
- MUST animate only compositor props (`transform`, `opacity`)
- NEVER animate layout properties (`width`, `height`, `top`, `left`, `margin`, `padding`)
- SHOULD avoid animating paint properties (`background`, `color`) except for small, local UI (text, icons)
- SHOULD use `ease-out` on entrance
- NEVER exceed `200ms` for interaction feedback
- MUST pause looping animations when off-screen
- MUST respect `prefers-reduced-motion`
- NEVER introduce custom easing curves unless explicitly requested
- SHOULD avoid animating large images or full-screen surfaces

## Typography

- MUST use `text-balance` for headings and `text-pretty` for body/paragraphs
- MUST use `tabular-nums` for data
- SHOULD use `truncate` or `line-clamp` for dense UI
- NEVER modify `letter-spacing` (`tracking-`) unless explicitly requested

## Layout

- MUST use a fixed `z-index` scale (no arbitrary `z-x`)
- SHOULD use `size-x` for square elements instead of `w-x` + `h-x`

## Performance

- NEVER animate large `blur()` or `backdrop-filter` surfaces
- NEVER apply `will-change` outside an active animation
- NEVER use `useEffect` for anything that can be expressed as render logic

## Design

- NEVER use gradients unless explicitly requested
- NEVER use purple or multicolor gradients
- NEVER use glow effects as primary affordances
- SHOULD use Tailwind CSS default shadow scale unless explicitly requested
- MUST give empty states one clear next action
- SHOULD limit accent color usage to one per view
- SHOULD use existing theme or Tailwind CSS color tokens before introducing new ones