Agent skill

UI Design System

by borghei in borghei/Claude-Skills

UI design system toolkit covering design tokens, component documentation, responsive calculations, and developer handoff.

MITAuto-check passedFrontend & Design

Install UI Design System

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

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

GitHub CLI
$ gh skill install borghei/Claude-Skills ui-design-system --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/ui-design-system .claude/skills/ui-design-system && 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
ui-design-system
GitHub stars
874
Token cost
~3.8k tokens
SKILL.md length
1,388 words
Files
6 (incl. scripts, references)
Skills in repo
364
Repo updated
First seen
Licence
MIT

At a glance

UI design system toolkit covering design tokens, component documentation, responsive calculations, and developer handoff.

  • Works in 5 steps: Identify brand color and style → Generate tokens using script → Review generated categories → …
  • Creating design systems
  • SKILL.md covers Table of Contents, Trigger Terms, Clarify First and Workflows, plus 8 more sections
  • Runs Python scripts from its folder; calls python

What it does

UI Design System is an agent skill from borghei/Claude-Skills. UI design system toolkit covering design tokens, component documentation, responsive calculations, and developer handoff. Use for creating design systems, maintaining visual consistency, or facilitating design-dev handoff.

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/component-architecture.md`, `references/developer-handoff.md` and `references/responsive-calculations.md`).

It sits in Frontend & Design, covering UI design, Design tokens and 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

  • Creating design systems
  • Maintaining visual consistency
  • Facilitating design-dev handoff

Example prompts

  • “/ui-design-system”

Requirements

  • Python 3

Workflow steps

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

  1. Identify brand color and style
  2. Generate tokens using script
  3. Review generated categories
  4. Export in target format
  5. Validate accessibility

What it can do on your machine

Read from SKILL.md and the folder at commit c9a1487. 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 1 file 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

UI Design System loads about 3.8k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 1,388 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

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 c9a1487, republished under its MIT licence (© borghei). 1,388 words, ~3,753 tokens.

Download SKILL.mdSave it as .claude/skills/ui-design-system/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
ui-design-system
description
UI design system toolkit covering design tokens, component documentation, responsive calculations, and developer handoff. Use for creating design systems, maintaining visual consistency, or facilitating design-dev handoff.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
product
metadata.domain
design-systems
metadata.updated
2026-03-31
metadata.tags
design-system, components, tokens, ui-patterns

UI Design System

Generate design tokens, create color palettes, calculate typography scales, build component systems, and prepare developer handoff documentation.


Table of Contents


Trigger Terms

Use this skill when you need to:

  • "generate design tokens"
  • "create color palette"
  • "build typography scale"
  • "calculate spacing system"
  • "create design system"
  • "generate CSS variables"
  • "export SCSS tokens"
  • "set up component architecture"
  • "document component library"
  • "calculate responsive breakpoints"
  • "prepare developer handoff"
  • "convert brand color to palette"
  • "check WCAG contrast"
  • "build 8pt grid system"

Clarify First

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

  • Brand primary color (hex) — the seed for the full palette (drives the color scale and WCAG contrast checks)
  • Style preset — modern, classic, or playful (sets fonts, border radius, and shadow style)
  • Output format and framework — CSS, SCSS, or JSON for Tailwind/styled-components/Figma (drives export and developer handoff)

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.

Workflows

Workflow 1: Generate Design Tokens

Situation: You have a brand color and need a complete design token system.

Steps:

  1. Identify brand color and style

    • Brand primary color (hex format)
    • Style preference: modern | classic | playful
  2. Generate tokens using script

    bash
    python scripts/design_token_generator.py "#0066CC" modern json
  3. Review generated categories

    • Colors: primary, secondary, neutral, semantic, surface
    • Typography: fontFamily, fontSize, fontWeight, lineHeight
    • Spacing: 8pt grid-based scale (0-64)
    • Borders: radius, width
    • Shadows: none through 2xl
    • Animation: duration, easing
    • Breakpoints: xs through 2xl
  4. Export in target format

    bash
    # CSS custom properties
    python scripts/design_token_generator.py "#0066CC" modern css > design-tokens.css
    
    # SCSS variables
    python scripts/design_token_generator.py "#0066CC" modern scss > _design-tokens.scss
    
    # JSON for Figma/tooling
    python scripts/design_token_generator.py "#0066CC" modern json > design-tokens.json
  5. Validate accessibility

    • Check color contrast meets WCAG AA (4.5:1 normal, 3:1 large text)
    • Verify semantic colors have contrast colors defined

Workflow 2: Create Component System

Situation: You need to structure a component library using design tokens.

Steps:

  1. Define component hierarchy

    • Atoms: Button, Input, Icon, Label, Badge
    • Molecules: FormField, SearchBar, Card, ListItem
    • Organisms: Header, Footer, DataTable, Modal
    • Templates: DashboardLayout, AuthLayout
  2. Map tokens to components

    ComponentTokens Used
    Buttoncolors, sizing, borders, shadows, typography
    Inputcolors, sizing, borders, spacing
    Cardcolors, borders, shadows, spacing
    Modalcolors, shadows, spacing, z-index, animation
  3. Define variant patterns

    Size variants:

    sm: height 32px, paddingX 12px, fontSize 14px
    md: height 40px, paddingX 16px, fontSize 16px
    lg: height 48px, paddingX 20px, fontSize 18px

    Color variants:

    primary: background primary-500, text white
    secondary: background neutral-100, text neutral-900
    ghost: background transparent, text neutral-700
  4. Document component API

    • Props interface with types
    • Variant options
    • State handling (hover, active, focus, disabled)
    • Accessibility requirements
  5. Reference: See references/component-architecture.md


Workflow 3: Responsive Design

Situation: You need breakpoints, fluid typography, or responsive spacing.

Steps:

  1. Define breakpoints

    NameWidthTarget
    xs0Small phones
    sm480pxLarge phones
    md640pxTablets
    lg768pxSmall laptops
    xl1024pxDesktops
    2xl1280pxLarge screens
  2. Calculate fluid typography

    Formula: clamp(min, preferred, max)

    css
    /* 16px to 24px between 320px and 1200px viewport */
    font-size: clamp(1rem, 0.5rem + 2vw, 1.5rem);

    Pre-calculated scales:

    css
    --fluid-h1: clamp(2rem, 1rem + 3.6vw, 4rem);
    --fluid-h2: clamp(1.75rem, 1rem + 2.3vw, 3rem);
    --fluid-h3: clamp(1.5rem, 1rem + 1.4vw, 2.25rem);
    --fluid-body: clamp(1rem, 0.95rem + 0.2vw, 1.125rem);
  3. Set up responsive spacing

    TokenMobileTabletDesktop
    --space-md12px16px16px
    --space-lg16px24px32px
    --space-xl24px32px48px
    --space-section48px80px120px
  4. Reference: See references/responsive-calculations.md


Workflow 4: Developer Handoff

Situation: You need to hand off design tokens to development team.

Steps:

  1. Export tokens in required formats

    bash
    # For CSS projects
    python scripts/design_token_generator.py "#0066CC" modern css
    
    # For SCSS projects
    python scripts/design_token_generator.py "#0066CC" modern scss
    
    # For JavaScript/TypeScript
    python scripts/design_token_generator.py "#0066CC" modern json
  2. Prepare framework integration

    React + CSS Variables:

    tsx
    import './design-tokens.css';
    
    <button className="btn btn-primary">Click</button>

    Tailwind Config:

    javascript
    const tokens = require('./design-tokens.json');
    
    module.exports = {
      theme: {
        colors: tokens.colors,
        fontFamily: tokens.typography.fontFamily
      }
    };

    styled-components:

    typescript
    import tokens from './design-tokens.json';
    
    const Button = styled.button`
      background: ${tokens.colors.primary['500']};
      padding: ${tokens.spacing['2']} ${tokens.spacing['4']};
    `;
  3. Sync with Figma

    • Install Tokens Studio plugin
    • Import design-tokens.json
    • Tokens sync automatically with Figma styles
  4. Handoff checklist

    • Token files added to project
    • Build pipeline configured
    • Theme/CSS variables imported
    • Component library aligned
    • Documentation generated
  5. Reference: See references/developer-handoff.md


Tool Reference

design_token_generator.py

Generates complete design token system from brand color.

ArgumentValuesDefaultDescription
brand_colorHex color#0066CCPrimary brand color
stylemodern, classic, playfulmodernDesign style preset
formatjson, css, scss, summaryjsonOutput format

Examples:

bash
# Generate JSON tokens (default)
python scripts/design_token_generator.py "#0066CC"

# Classic style with CSS output
python scripts/design_token_generator.py "#8B4513" classic css

# Playful style summary view
python scripts/design_token_generator.py "#FF6B6B" playful summary

Output Categories:

CategoryDescriptionKey Values
colorsColor palettesprimary, secondary, neutral, semantic, surface
typographyFont systemfontFamily, fontSize, fontWeight, lineHeight
spacing8pt grid0-64 scale, semantic (xs-3xl)
sizingComponent sizescontainer, button, input, icon
bordersBorder valuesradius (per style), width
shadowsShadow stylesnone through 2xl, inner
animationMotion tokensduration, easing, keyframes
breakpointsResponsivexs, sm, md, lg, xl, 2xl
z-indexLayer systembase through notification

Quick Reference Tables

Color Scale Generation
StepBrightnessSaturationUse Case
5095% fixed30%Subtle backgrounds
10095% fixed38%Light backgrounds
20095% fixed46%Hover states
30095% fixed54%Borders
40095% fixed62%Disabled states
500Original70%Base/default color
600Original × 0.878%Hover (dark)
700Original × 0.686%Active states
800Original × 0.494%Text
900Original × 0.2100%Headings
Typography Scale (1.25x Ratio)
SizeValueCalculation
xs10px16 ÷ 1.25²
sm13px16 ÷ 1.25¹
base16pxBase
lg20px16 × 1.25¹
xl25px16 × 1.25²
2xl31px16 × 1.25³
3xl39px16 × 1.25⁴
4xl49px16 × 1.25⁵
5xl61px16 × 1.25⁶
Show full SKILL.md (616 more words)Show less
WCAG Contrast Requirements
LevelNormal TextLarge Text
AA4.5:13:1
AAA7:14.5:1

Large text: ≥18pt regular or ≥14pt bold

Style Presets
AspectModernClassicPlayful
Font SansInterHelveticaPoppins
Font MonoFira CodeCourierSource Code Pro
Radius Default8px4px16px
ShadowsLayered, subtleSingle layerSoft, pronounced

Knowledge Base

Detailed reference guides in references/:

FileContent
token-generation.mdColor algorithms, HSV space, WCAG contrast, type scales
component-architecture.mdAtomic design, naming conventions, props patterns
responsive-calculations.mdBreakpoints, fluid typography, grid systems
developer-handoff.mdExport formats, framework setup, Figma sync

Validation Checklist

Token Generation
  • Brand color provided in hex format
  • Style matches project requirements
  • All token categories generated
  • Semantic colors include contrast values
Component System
  • All sizes implemented (sm, md, lg)
  • All variants implemented (primary, secondary, ghost)
  • All states working (hover, active, focus, disabled)
  • Uses only design tokens (no hardcoded values)
Accessibility
  • Color contrast meets WCAG AA
  • Focus indicators visible
  • Touch targets ≥ 44×44px
  • Semantic HTML elements used
Developer Handoff
  • Tokens exported in required format
  • Framework integration documented
  • Design tool synced
  • Component documentation complete

Troubleshooting

ProblemCauseSolution
Generated colors fail WCAG contrastBrand color too light or too saturatedUse darker shades (600+) for text on light backgrounds; check with contrast tool
Token export has incorrect valuesWrong format argument or color syntaxEnsure hex color is quoted (e.g. "#0066CC"); verify format is json, css, or scss
Typography scale too large/smallDefault 1.25x ratio doesn't fit designModify type_scale_ratio in DesignTokenGenerator class (1.125 for tighter, 1.333 for looser)
SCSS variables conflict with existingToken naming collisionPrefix all tokens with project namespace (edit export function)
Design tools show different colorsHex rounding in color scale generationUse JSON export as source of truth; sync with Tokens Studio plugin
Spacing values don't align with gridCustom spacing mixed with 8pt gridUse only values from the generated spacing system; avoid arbitrary pixel values
Shadow tokens look wrong in dark modeShadows designed for light backgroundsCreate separate dark-mode shadow tokens with lighter opacity values

Success Criteria

CriterionTargetHow to Measure
Token consistencyZero hardcoded color/spacing values in codebaseLint rule violations count
WCAG AA complianceAll text colors meet 4.5:1 contrast ratioAutomated contrast checker or manual audit
Export format coverageCSS, SCSS, and JSON all generate correctlyRun generator with each format; validate output
Design-dev sync<24h between token update and code deploymentTime from Figma change to production
Component token coverage100% of components use design tokensAudit component styles for hardcoded values
Typography consistencyAll text uses design system type scaleVisual audit across all pages
Responsive behaviorFluid typography works across all breakpointsTest at xs, sm, md, lg, xl, 2xl widths

Scope & Limitations

In scope:

  • Complete design token generation from brand color
  • Color palette generation (primary, secondary, neutral, semantic)
  • Typography system with modular scale
  • 8pt grid-based spacing system
  • Component sizing, border, shadow, animation tokens
  • Export to CSS custom properties, SCSS variables, and JSON
  • Responsive breakpoint definitions
  • WCAG contrast reference tables

Out of scope:

  • Dark mode token generation (requires separate palette mapping)
  • Animation/motion design library
  • Icon system generation
  • Runtime theme switching implementation
  • Figma plugin or API integration (use Tokens Studio)
  • Visual regression testing
  • Design-to-code conversion (use Figma Dev Mode or Locofy)

Integration Points

Tool / PlatformIntegration MethodUse Case
Figma / Tokens StudioImport JSON output as token sourceSync design tool with code tokens
Tailwind CSSJSON tokens as tailwind.config.js themeConfigure Tailwind from design system
styled-components / EmotionImport JSON tokens in theme providerCSS-in-JS theming
Style DictionaryUse JSON output as source tokensMulti-platform token build (iOS, Android, web)
StorybookPair tokens with component storiesDocument component visual variations
CI/CDToken generation in build pipelineAutomated token updates on brand change

© 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 5 other files (scripts, references) in product-team/ui-design-system of borghei/Claude-Skills.

  • SKILL.md
  • references/component-architecture.md
  • references/developer-handoff.md
  • references/responsive-calculations.md
  • references/token-generation.md
  • scripts/design_token_generator.py

Open the folder on GitHubat commit c9a1487

Compare with similar skills

UI Design System 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.

UI Design System compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
UI Design System this skillborghei/Claude-Skills874—~3.8kAutomated safety check: PassMIT
Design Dnazanwei/design-dna1.9k1 repos~2.1kAutomated safety check: PassMIT
Website Design Taste Extractorsenlindesign/taste-skill381—~5.3kAutomated safety check: PassNone
Material Design 3 UI/UX Guideskydashnet/material-design-3-ui-skill130—~3kAutomated safety check: PassMIT
UI Component Spec Designerplugin87/ux-ui-agent-skills1.5k—~2.8kAutomated safety check: PassMIT
UI Design Systemtry-works/role-model117—~5kAutomated safety check: PassMIT

Similar skills

  • Design Dna

    zanwei/design-dna

    Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects…

    1.9k GitHub starsUsed in 1 repo~2.1k tokens
    Frontend & DesignAuto-check passed
  • Website Design Taste Extractor

    senlindesign/taste-skill

    Reverse-engineers a website's design from its URL into a Markdown and JSON pair holding concrete tokens and the trade-offs behind the look.

    381 GitHub stars~5.3k tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • Material Design 3 UI/UX Guide

    skydashnet/material-design-3-ui-skill

    Guides designing, reviewing or implementing interfaces that follow Google's Material Design 3 system: semantic tokens, component states, adaptive layout and accessibility.

    130 GitHub stars~3k tokensUpdated 7 days ago
    Frontend & DesignAuto-check passed
  • UI Component Spec Designer

    plugin87/ux-ui-agent-skills

    Writes a complete UI component spec with anatomy, variants, sizes, eight interaction states, design-token mapping and accessibility notes before or alongside code.

    1.5k GitHub stars~2.8k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • UI Design System

    try-works/role-model

    React UI component systems with TailwindCSS + Radix + shadcn/ui.

    117 GitHub stars~5k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Design Extractor

    luongnv89/sleek-ui

    Extract a design system from a screenshot (PNG/JPG/WEBP) or a live URL and produce a schema-compliant design.v1.json file plus a ready-to-use agent prompt for applying the design to any website/app.

    133 GitHub stars~3.4k tokensUpdated 19 days ago
    Frontend & DesignAuto-check: warnings

More from borghei/Claude-Skills

All 364 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

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

    874 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.

    874 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.

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

    borghei/Claude-Skills

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

    874 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.

    874 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    874 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Questions about UI Design System

What does UI Design System do?

UI design system toolkit covering design tokens, component documentation, responsive calculations, and developer handoff. UI Design System is an agent skill from borghei/Claude-Skills. UI design system toolkit covering design tokens, component documentation, responsive calculations, and developer handoff.

When should I use UI Design System?

UI Design System fits situations like: creating design systems; maintaining visual consistency; facilitating design-dev handoff.

How do I install UI Design System in Claude Code?

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

How do I install UI Design System in Codex?

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

Can I use UI Design System 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 ui-design-system -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ui-design-system, .gemini/skills/ui-design-system, .github/skills/ui-design-system and .opencode/skills/ui-design-system in your project.

What does UI Design System need to run?

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

Does UI Design System 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 UI Design System 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 UI Design System use?

UI Design System 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 UI Design System use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.4k tokens, read only when the agent opens those files.

What are the alternatives to UI Design System?

Skills that share tags, products or a category with UI Design System: Design Dna (zanwei/design-dna, 1.9k stars), Website Design Taste Extractor (senlindesign/taste-skill, 381 stars), Material Design 3 UI/UX Guide (skydashnet/material-design-3-ui-skill, 130 stars) and UI Component Spec Designer (plugin87/ux-ui-agent-skills, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains UI Design System?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 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.