Agent skill

Design System Lead

by borghei in borghei/Claude-Skills

Design systems leadership across component libraries, design tokens, and design-dev collaboration.

MITAuto-check passedFrontend & Design

Install Design System Lead

skills CLI
$ npx skills add borghei/Claude-Skills --skill design-system-lead -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills design-system-lead --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/product-team/design-system-lead .claude/skills/design-system-lead && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
design-system-lead
GitHub stars
886
Token cost
~3.6k tokens
SKILL.md length
965 words
Files
4 (incl. scripts)
Skills in repo
354
Repo updated
First seen
Licence
MIT

At a glance

Design systems leadership across component libraries, design tokens, and design-dev collaboration.

  • Works in 6 steps: Assess maturity - Evaluate current… → Define token architecture - Build a… → Build component library - Design and… → …
  • Architecting a token system
  • SKILL.md covers Clarify First, Workflow, Design System Maturity Model and Token Architecture, plus 9 more sections
  • Runs Python scripts from its folder; calls python

What it does

Design System Lead is an agent skill from borghei/Claude-Skills. Design systems leadership across component libraries, design tokens, and design-dev collaboration. Use when architecting a token system, building a component library, defining governance, or generating cross-platform tokens.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/adoption_analyzer.py`, `scripts/component_scaffold.py` and `scripts/token_gen.py`).

It sits in Frontend & Design, covering Design systems. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Architecting a token system
  • Building a component library
  • Defining governance
  • Generating cross-platform tokens

Example prompts

  • “/design-system-lead”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Assess maturity - Evaluate current design system maturity (Emerging, Defined, Managed, or Optimized). Audit existing patterns…
  2. Define token architecture - Build a three-tier token structure: primitive (raw values), semantic (purpose-based aliases), and component…
  3. Build component library - Design and implement components starting with primitives (Button, Input, Icon), then composites (Card, Modal…
  4. Document everything - Create usage guidelines, code examples, do/don't rules, and accessibility notes for every component. Checkpoint…
  5. Establish governance - Define the RFC-to-release contribution process. Set versioning strategy (SemVer). Checkpoint: contribution process…
  6. Measure adoption - Track coverage (% of products using DS), consistency (token compliance rate), efficiency (time to build), and quality…

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Design System Lead loads about 3.6k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 965 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 965 words, ~3,614 tokens.

Download SKILL.mdSave it as .claude/skills/design-system-lead/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
design-system-lead
description
Design systems leadership across component libraries, design tokens, and design-dev collaboration. Use when architecting a token system, building a component library, defining governance, or generating cross-platform tokens.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
product-design
metadata.domain
design-systems
metadata.updated
2026-03-31
metadata.tags
design-systems, components, tokens, documentation, figma

Design System Lead

The agent operates as a senior design system lead, delivering scalable component libraries, token architectures, governance processes, and adoption strategies for cross-functional product teams.

Clarify First

Before generating the design system, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Brand color and any existing tokens — the primitive values to build from (drives the three-tier token architecture)
  • Current maturity level — Emerging, Defined, Managed, or Optimized (decides whether you establish foundations or optimize governance)
  • Target platforms — web (CSS/SCSS), iOS, Android (drives token export formats and Style Dictionary config)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Workflow

  1. Assess maturity - Evaluate current design system maturity (Emerging, Defined, Managed, or Optimized). Audit existing patterns, inconsistencies, and custom components. Checkpoint: maturity level is documented with evidence.
  2. Define token architecture - Build a three-tier token structure: primitive (raw values), semantic (purpose-based aliases), and component (scoped to specific UI elements). Checkpoint: every semantic token references a primitive; no hardcoded values remain.
  3. Build component library - Design and implement components starting with primitives (Button, Input, Icon), then composites (Card, Modal, Dropdown), then patterns (Forms, Navigation, Tables). Checkpoint: each component has variants, sizes, states, props table, and accessibility requirements.
  4. Document everything - Create usage guidelines, code examples, do/don't rules, and accessibility notes for every component. Checkpoint: documentation covers installation, basic usage, all variants, and at least one accessibility note.
  5. Establish governance - Define the RFC-to-release contribution process. Set versioning strategy (SemVer). Checkpoint: contribution process is published and reviewed by both design and engineering leads.
  6. Measure adoption - Track coverage (% of products using DS), consistency (token compliance rate), efficiency (time to build), and quality (a11y score, bug reports). Checkpoint: adoption dashboard is updated monthly.

Design System Maturity Model

LevelCharacteristicsFocus
1: EmergingAd-hoc styles, no standardsEstablish foundations
2: DefinedDocumented guidelinesComponent library
3: ManagedShared component libraryAdoption, governance
4: OptimizedAutomated, measuredContinuous improvement

Token Architecture

Three-tier token system (primitive -> semantic -> component):

json
{
  "color": {
    "primitive": {
      "blue": {
        "50": {"value": "#eff6ff"},
        "500": {"value": "#3b82f6"},
        "600": {"value": "#2563eb"},
        "900": {"value": "#1e3a8a"}
      }
    },
    "semantic": {
      "primary": {"value": "{color.primitive.blue.600}"},
      "primary-hover": {"value": "{color.primitive.blue.700}"},
      "background": {"value": "{color.primitive.gray.50}"},
      "text": {"value": "{color.primitive.gray.900}"}
    },
    "component": {
      "button-primary-bg": {"value": "{color.semantic.primary}"},
      "button-primary-text": {"value": "#ffffff"}
    }
  },
  "spacing": {
    "primitive": {"1": {"value": "4px"}, "2": {"value": "8px"}, "4": {"value": "16px"}, "8": {"value": "32px"}},
    "semantic": {"component-padding": {"value": "{spacing.primitive.4}"}, "section-gap": {"value": "{spacing.primitive.8}"}}
  },
  "typography": {
    "fontFamily": {"sans": {"value": "Inter, system-ui, sans-serif"}, "mono": {"value": "JetBrains Mono, monospace"}},
    "fontSize": {"sm": {"value": "14px"}, "base": {"value": "16px"}, "lg": {"value": "18px"}, "xl": {"value": "20px"}}
  }
}

Example: Cross-Platform Token Generation

javascript
// style-dictionary.config.js
module.exports = {
  source: ['tokens/**/*.json'],
  platforms: {
    css: {
      transformGroup: 'css',
      buildPath: 'dist/css/',
      files: [{ destination: 'variables.css', format: 'css/variables' }]
    },
    scss: {
      transformGroup: 'scss',
      buildPath: 'dist/scss/',
      files: [{ destination: '_variables.scss', format: 'scss/variables' }]
    },
    ios: {
      transformGroup: 'ios',
      buildPath: 'dist/ios/',
      files: [{ destination: 'StyleDictionaryColor.swift', format: 'ios-swift/class.swift' }]
    },
    android: {
      transformGroup: 'android',
      buildPath: 'dist/android/',
      files: [{ destination: 'colors.xml', format: 'android/colors' }]
    }
  }
};

Component Library Structure

design-system/
+-- foundations/     (colors, typography, spacing, elevation, motion, grid)
+-- components/
|   +-- primitives/  (Button, Input, Icon)
|   +-- composites/  (Card, Modal, Dropdown)
|   +-- patterns/    (Forms, Navigation, Tables)
+-- layouts/         (page templates, content layouts)
+-- documentation/   (getting-started, design guidelines, code guidelines)
+-- assets/          (icons, illustrations, logos)
Component Specification: Button
markdown
## Variants
- Primary: main action
- Secondary: supporting action
- Tertiary: low-emphasis action
- Destructive: dangerous/irreversible action

## Sizes
- Small: 32px height, 8px/12px padding
- Medium: 40px height (default), 10px/16px padding
- Large: 48px height, 12px/24px padding

## States
Default -> Hover -> Active -> Focus -> Disabled -> Loading

## Props
| Prop      | Type        | Default   | Description      |
|-----------|-------------|-----------|------------------|
| variant   | string      | 'primary' | Visual style     |
| size      | string      | 'medium'  | Button size      |
| disabled  | boolean     | false     | Disabled state   |
| loading   | boolean     | false     | Loading state    |
| leftIcon  | ReactNode   | -         | Leading icon     |
| onClick   | function    | -         | Click handler    |

## Accessibility
- Minimum touch target: 44x44px
- Visible focus ring on keyboard navigation
- aria-label required for icon-only buttons
- aria-busy="true" when loading
Example: Button Implementation (React + CVA)
typescript
import { cva, type VariantProps } from 'class-variance-authority';

const buttonVariants = cva(
  'inline-flex items-center justify-center rounded-md font-medium transition-colors focus-visible:outline-none focus-visible:ring-2 disabled:pointer-events-none disabled:opacity-50',
  {
    variants: {
      variant: {
        primary: 'bg-primary text-primary-foreground hover:bg-primary/90',
        secondary: 'bg-secondary text-secondary-foreground hover:bg-secondary/80',
        destructive: 'bg-destructive text-destructive-foreground hover:bg-destructive/90',
      },
      size: {
        sm: 'h-8 px-3 text-sm',
        md: 'h-10 px-4 text-sm',
        lg: 'h-12 px-6 text-base',
      },
    },
    defaultVariants: { variant: 'primary', size: 'md' },
  }
);

Governance: Contribution Process

1. REQUEST  - Create RFC describing problem and proposed component/change
2. REVIEW   - Design review + engineering review + accessibility review
3. BUILD    - Figma component + code implementation + unit tests + visual regression
4. DOCUMENT - API docs + usage guidelines + Storybook stories
5. RELEASE  - SemVer bump + changelog + announcement
Versioning Strategy
Change TypeVersion BumpExamples
BreakingMAJORComponent API change, token rename
New featureMINORNew component, new variant, new token
Bug fixPATCHStyle fix, docs update, perf improvement

Adoption Metrics Dashboard

Design System Health
  Adoption: 82% (12/15 products)
  Component Usage: 78% (45 components)
  Token Compliance: 95%
  Overrides: 23 (down from 38)

  Efficiency
  Avg time to build new feature: 3.2 days (was 5.1)
  Custom components created this quarter: 4 (was 12)

Tool Reference

token_gen.py

Generates a three-tier design token system (primitive, semantic, component) from a brand color. Supports CSS, SCSS, and JSON output. Includes WCAG contrast ratio checking.

FlagTypeDefaultDescription
--color, -cstring#0066CCBrand color in hex
--format, -fchoicesummaryOutput format: json, css, scss, summary
--tiers, -tchoiceallToken tiers: all, primitive, semantic, component
--output, -ostring(stdout)Output directory for generated files
--jsonflagFalseShortcut for --format json
bash
python scripts/token_gen.py --color "#0066CC"
python scripts/token_gen.py --color "#0066CC" --format css --output dist/
python scripts/token_gen.py --color "#8B4513" --tiers primitive --json
component_scaffold.py

Generates component documentation scaffolds with props tables, variants, states, accessibility requirements, anatomy, usage guidelines, and code examples.

FlagTypeDefaultDescription
--name, -nstring(required)Component name in PascalCase
--category, -cchoice(required)Category: primitive, composite, pattern
--variants, -vstring(category default)Comma-separated variant names
--sizes, -sstringsm,md,lgComma-separated size names
--jsonflagFalseOutput as JSON
bash
python scripts/component_scaffold.py --name Button --category primitive
python scripts/component_scaffold.py --name DataTable --category pattern --variants "default,compact,striped"
python scripts/component_scaffold.py --name Modal --category composite --json
adoption_analyzer.py

Analyzes design system adoption across products by evaluating component coverage, token compliance, custom overrides, and accessibility scores. Produces a health dashboard with per-product and portfolio-level analysis.

FlagTypeDefaultDescription
inputpositional(required)CSV file with adoption data or "sample"
--threshold, -tint75Health score threshold for flagging
--jsonflagFalseOutput as JSON

CSV columns: product, total_components, ds_components, total_tokens, ds_tokens, custom_overrides, a11y_score, last_audit

bash
python scripts/adoption_analyzer.py sample
python scripts/adoption_analyzer.py adoption_data.csv
python scripts/adoption_analyzer.py adoption_data.csv --threshold 80 --json

Show full SKILL.md (366 more words)Show less

Troubleshooting

ProblemCauseSolution
Token overrides in productionTeams bypassing design systemRun adoption_analyzer monthly; add lint rules for hardcoded values
Inconsistent component behavior across productsVersion driftEnforce SemVer; automate DS dependency updates in CI
Low adoption in older productsMigration cost perceived as too highPrioritize high-traffic pages; create migration guides per product
Token naming conflictsNo naming convention enforcedAdopt CTI (Category-Type-Item) naming; document in governance
Component API breaking changesInsufficient versioning disciplineUse codemods for migration; deprecation period of 2 minor versions
Designers and developers out of syncFigma/code token driftUse Tokens Studio plugin; sync on every release
Contribution bottleneckRFC review queue backed upSet SLA for reviews (48h); rotate reviewers weekly

Success Criteria

CriterionTargetHow to Measure
Component coverage>80% across all productsadoption_analyzer component coverage metric
Token compliance>90% (no hardcoded values)adoption_analyzer token compliance metric
Custom overridesTrending downward quarter-over-quarterTrack total overrides in adoption report
Time to build new feature30%+ reduction vs pre-DS baselineCompare sprint velocity before/after DS adoption
Accessibility score>85% across all productsadoption_analyzer a11y score
Contribution rate2+ external contributions per quarterTrack merged RFCs from non-core-team members
Design-dev handoff time<1 day for standard componentsMeasure time from design approval to code PR

Scope & Limitations

In scope:

  • Three-tier token architecture design and generation
  • Component library structure and documentation scaffolding
  • Adoption tracking and health reporting
  • Cross-platform token export (CSS, SCSS, JSON)
  • Governance process definition
  • WCAG contrast ratio validation

Out of scope:

  • Visual regression testing execution (use Chromatic, Percy, or BackstopJS)
  • Figma plugin development (use Tokens Studio for token sync)
  • Runtime theme switching implementation (framework-specific)
  • Icon library creation and SVG optimization
  • Motion design and animation library
  • Component implementation code (scaffold generates docs, not runtime code)

Integration Points

Tool / PlatformIntegration MethodUse Case
Figma / Tokens StudioImport token_gen JSON outputSync design tokens between design and code
Style DictionaryUse token_gen JSON as sourceBuild multi-platform tokens (iOS, Android, web)
Storybookcomponent_scaffold output as stories templateAuto-generate component documentation
Chromatic / PercyPair with component_scaffold test checklistVisual regression testing pipeline
CI/CDadoption_analyzer --json in pipelineAutomated adoption health checks on PRs
Tailwind / CSS-in-JStoken_gen CSS/JSON exportTheme configuration from design tokens

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in product-team/design-system-lead of borghei/Claude-Skills.

  • SKILL.md
  • scripts/adoption_analyzer.py
  • scripts/component_scaffold.py
  • scripts/token_gen.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Design System Lead next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Design System Lead compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Design System Lead this skillborghei/Claude-Skills886—~3.6kAutomated safety check: PassMIT
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
UI StylingOhh-889/skyroc79513 repos~2.5kAutomated safety check: PassMIT
Shadcnsupabase/evals14342 repos~4.5kAutomated safety check: PassApache-2.0

Similar skills

  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • UI Styling

    Ohh-889/skyroc

    Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.

    795 GitHub starsUsed in 13 repos~2.5k tokens
    Frontend & DesignAuto-check passed
  • Shadcn

    supabase/evals

    Official

    Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI.

    143 GitHub starsUsed in 42 repos~4.5k tokens
    Frontend & DesignAuto-check passed
  • Design System

    Ohh-889/skyroc

    Token architecture, component specifications, and slide generation.

    795 GitHub starsUsed in 11 repos~1.7k tokens
    Frontend & DesignAuto-check passed

More from borghei/Claude-Skills

All 354 skills in this repo
  • Agent Harness

    borghei/Claude-Skills

    Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.

    886 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    886 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    886 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    886 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    886 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    886 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

Questions about Design System Lead

What does Design System Lead do?

Design systems leadership across component libraries, design tokens, and design-dev collaboration. Design System Lead is an agent skill from borghei/Claude-Skills. Design systems leadership across component libraries, design tokens, and design-dev collaboration.

When should I use Design System Lead?

Design System Lead fits situations like: architecting a token system; building a component library; defining governance; generating cross-platform tokens.

How do I install Design System Lead in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill design-system-lead -a claude-code`. Or copy the skill folder (product-team/design-system-lead in borghei/Claude-Skills) into .claude/skills/design-system-lead in your project. Claude Code loads it when a task matches its description.

How do I install Design System Lead in Codex?

Run `npx skills add borghei/Claude-Skills --skill design-system-lead -a codex`. Or copy the skill folder (product-team/design-system-lead in borghei/Claude-Skills) into .agents/skills/design-system-lead in your project. Codex loads it when a task matches its description.

Can I use Design System Lead in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill design-system-lead -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-system-lead, .gemini/skills/design-system-lead, .github/skills/design-system-lead and .opencode/skills/design-system-lead in your project.

What does Design System Lead need to run?

Going by SKILL.md and its folder, Design System Lead needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Design System Lead access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Design System Lead safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Design System Lead use?

Design System Lead is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Design System Lead use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Design System Lead?

Skills that share tags, products or a category with Design System Lead: Impeccable (bestofjs/bestofjs, 3.1k stars), Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars) and UI Styling (Ohh-889/skyroc, 795 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Design System Lead?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.