Cody skill library

Best Frontend & Design Agent Skills

Skills for distinctive interfaces, accessible reviews, scalable React architecture, and programmatic video.

Frontend & Design

anthropics/skills

frontend-design

Gives an agent a stronger visual point of view before it starts writing interface code. Best for new landing pages, dashboards, prototypes, and redesigns where the brief needs a distinctive visual direction.

844K installs173K
Read the review
Frontend & Design

vercel-labs/agent-skills

vercel-react-best-practices

A prioritized React and Next.js performance checklist maintained by Vercel Engineering. Best for react and Next.js teams that want performance guidance applied consistently while code is being written.

682K installs31K
Read the review
Frontend & Design

vercel-labs/agent-skills

web-design-guidelines

Reviews interface code against a maintained set of usability, interaction, and accessibility checks. Best for a final UI review after implementation, particularly for keyboard behavior, hierarchy, controls, and content states.

599K installs31K
Read the review
Frontend & Design

remotion-dev/skills

remotion-best-practices

Routes an agent through the right Remotion guidance for building video in React. Best for react developers creating repeatable product videos, explainers, social clips, or data-driven motion graphics.

505K installs4K
Read the review
Frontend & Design

vercel-labs/agent-skills

vercel-composition-patterns

Helps agents design React component APIs that remain flexible as a product grows. Best for design systems, shared component libraries, and refactors where component APIs have become hard to reason about.

317K installs31K
Read the review

How the list was made

A smaller catalog, chosen for real work.

Cody's editors selected a focused set of agent skills that solve recognizable jobs, come from inspectable GitHub repositories, and show meaningful adoption or active maintenance.

5 of 5 have 5K+ installs
  1. 1

    Prefer focused skills that encode a repeatable workflow or a maintained domain playbook.

  2. 2

    Favor clear ownership, active repositories, and meaningful adoption, then use community experience as a supporting signal.

  3. 3

    Explain what each skill does, who it helps, and what to review before installing it.

  4. 4

    Keep the collection small enough that users can install only what matches their work.

Skills shape the workflow. Prompts shape the brief.

Browse the rebuilt prompt library for detailed, model-aware templates designed for GPT-5.6 and Claude Fable 5.1.

Explore prompt templates