Agent skill

Figma Connect Component

by bitovi in bitovi/ai-enablement-prompts

Generate Figma Code Connect mappings that link React components to their Figma counterparts.

MITAuto-check passedFrontend & Design

Install Figma Connect Component

skills CLI
$ npx skills add bitovi/ai-enablement-prompts --skill figma-connect-component -a claude-code

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

GitHub CLI
$ gh skill install bitovi/ai-enablement-prompts figma-connect-component --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/bitovi/ai-enablement-prompts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/figma/figma-connect-component .claude/skills/figma-connect-component && 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
figma-connect-component
GitHub stars
121
Token cost
~3.3k tokens
SKILL.md length
859 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

Generate Figma Code Connect mappings that link React components to their Figma counterparts.

  • Works in 6 steps: Gather Figma Component Data → Discover Figma URL (if needed) → Read Code Component and Inline the… → …
  • A component exists in code and needs a Code Connect file so Figma shows real code snippets in Dev Mode
  • SKILL.md covers When to Use This Skill, Required Inputs, Execution Steps and Rules, plus 5 more sections
  • Calls tsc and npx; reaches figma.com

What it does

Figma Connect Component is an agent skill from bitovi/ai-enablement-prompts. Generate Figma Code Connect mappings that link React components to their Figma counterparts. Use when a component exists in code and needs a Code Connect file so Figma shows real code snippets in Dev Mode. Also triggers on phrases like "connect this component to Figma", "generate Code Connect", "publish to Figma", "add figma.connect for this component", "link this to Figma Dev Mode".

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering React components. It works with Figma and Model Context Protocol. The repository describes itself as: Prompts Bitovi uses for software development. The licence is MIT.

When your agent uses it

  • A component exists in code and needs a Code Connect file so Figma shows real code snippets in Dev Mode
  • Phrases like connect this component to Figma
  • Generate Code Connect
  • Publish to Figma

Example prompts

  • “connect this component to Figma”
  • “generate Code Connect”
  • “publish to Figma”
  • “/figma-connect-component”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Gather Figma Component Data
  2. Discover Figma URL (if needed)
  3. Read Code Component and Inline the Mapping Contract
  4. Generate Mapping
  5. Write Code Connect File
  6. Update README with Mapping Diagram

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • tsc
    • npx

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • figma.com

    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

Figma Connect Component loads about 3.3k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 859 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from bitovi/ai-enablement-prompts at commit df229b1, republished under its MIT licence (© bitovi). 859 words, ~3,285 tokens.

Download SKILL.mdSave it as .claude/skills/figma-connect-component/SKILL.md (or your agent's skills folder).
name
figma-connect-component
description
Generate Figma Code Connect mappings that link React components to their Figma counterparts. Use when a component exists in code and needs a Code Connect file so Figma shows real code snippets in Dev Mode. Also triggers on phrases like "connect this component to Figma", "generate Code Connect", "publish to Figma", "add figma.connect for this component", "link this to Figma Dev Mode".
argument-hint
<figma-url> [<component-file-path>]
user-invocable
true

Generate Figma Code Connect for React Components

When to Use This Skill

User provides a Figma component URL (or component name) and wants to generate the Code Connect mapping for it.

Required Inputs

  1. Figma component identifier (one of):
    • Full URL: https://figma.com/design/{fileKey}/{fileName}?node-id={nodeId}
    • File key + node ID: fileKey: abc123, nodeId: 45:67
    • Evidence file path: .temp/figma-explore/{component}.json
    • Component name (will search for URL in project files)
  2. Code component folder path (e.g., src/components/Button/Button.tsx)

Execution Steps

1. Gather Figma Component Data

Option A: Evidence File Provided (Preferred)

If an evidence file from figma-explore is provided (e.g., .temp/figma-explore/{component}.json):

  • Read the JSON file directly
  • Extract: id (node ID), name, variants, variantProperties, componentPropertyDefinitions
  • The file contains all the variant names and values needed for Code Connect

Example evidence file structure:

json
{
  "id": "16:1234",
  "name": "Button",
  "type": "COMPONENT_SET",
  "variants": [
    { "name": "Type=Primary, Size=Small", "id": "16:1235" },
    { "name": "Type=Primary, Size=Large", "id": "16:1236" }
  ],
  "variantProperties": {
    "Type": ["Primary", "Secondary", "Ghost"],
    "Size": ["Small", "Medium", "Large"]
  },
  "componentPropertyDefinitions": {
    "Label": { "type": "TEXT", "defaultValue": "Button" },
    "Show Icon": { "type": "BOOLEAN", "defaultValue": false }
  }
}

Option B: URL/Node ID Provided (MCP Fallback)

If only a Figma URL or node ID is provided:

  1. Search for existing evidence files in .temp/figma-explore/ that match the component name
  2. If not found, use MCP tools:
    • Call mcp_figma_get_metadata with nodeId and fileKey
    • Call mcp_figma_get_design_context with nodeId and fileKey
2. Discover Figma URL (if needed)

If no URL or evidence file provided, search for it:

  1. Check {ComponentFolder}/README.md for "Figma Source" section
  2. Check specs/**/tasks.md for component-to-Figma mapping tables
  3. Check .temp/figma-explore/figma-components-index.json for matching component names
  4. Check prior conversation context for file key
3. Read Code Component and Inline the Mapping Contract
  1. Read the specified component file — identify exports, props interface, component name
  2. If .temp/design-components/{component-name}/proposed-api.md exists, read it and inline the prop-to-Figma mapping table into your working context. Do not reference this file by path during generation — the full mapping must be in active context so no property is guessed or missed.
  3. Cross-check: every prop in the React interface should have a corresponding Figma source in the table. Props with no Figma source (e.g., className, id) are omitted from Code Connect.
4. Generate Mapping
  • Map Figma properties to code props using figma.* helpers
  • Build example JSX template
  • Add appropriate imports
5. Write Code Connect File
  • Output to: {ComponentFolder}/{ComponentName}.figma.tsx
  • Raw file content only—no markdown fences
6. Update README with Mapping Diagram

If {ComponentFolder}/README.md exists, ensure it has a Design-to-Code Mapping section with a mermaid flowchart at the top showing the Figma-to-React property relationships.

Diagram format:

mermaid
flowchart LR
    subgraph Figma["Figma Variants"]
        FProp1["PropertyName1"]
        FProp2["PropertyName2"]
    end

    subgraph React["React Props"]
        RProp1["propName1"]
        RProp2["propName2"]
    end

    FProp1 -->|"Value1 → 'code1'<br>Value2 → 'code2'"| RProp1
    FProp2 -->|"mapping description"| RProp2

    style Figma fill:#f3e8ff,stroke:#9333ea
    style React fill:#dbeafe,stroke:#3b82f6

Placement: The mermaid diagram should be placed immediately after the ## Design-to-Code Mapping heading, before any tables.

Example README structure:

markdown
## Design-to-Code Mapping

```mermaid
flowchart LR
    subgraph Figma["Figma Variants"]
        FSize["Size"]
        FType["Type"]
    end

    subgraph React["React Props"]
        RSize["size"]
        RVariant["variant"]
    end

    FSize -->|"Small → 'sm'<br>Medium → 'md'<br>Large → 'lg'"| RSize
    FType -->|"Primary → 'primary'<br>Secondary → 'secondary'"| RVariant

    style Figma fill:#f3e8ff,stroke:#9333ea
    style React fill:#dbeafe,stroke:#3b82f6
` ` `

### Variant Mappings
| Figma Variant | Figma Value | React Prop | React Value |
...

Rules for the diagram:

  • Include all mapped variant properties (from figma.enum() calls)
  • Include boolean properties that map to React props
  • Show value transformations on the arrows (e.g., "Small → 'sm'")
  • Use <br> for multiple value mappings on one arrow
  • Exclude pseudo-states (hover, focus, pressed) from the diagram
  • Use purple styling for Figma subgraph, blue for React subgraph

Rules

Use Exact Figma Property Names

Critical: Code Connect requires the EXACT property names as they appear in Figma.

  • Get exact names from evidence files (.figma-components/*.json) or get_metadata output
  • Property names like ButtonType, Type, Size must match EXACTLY (case-sensitive)
  • The get_design_context MCP tool normalizes to camelCase - do NOT use those names
  • Property names are case-sensitive: Size ≠ size

Example from metadata:

name="ButtonType=Responsive, Type=Primary, Size=Small"

Use in Code Connect:

tsx
variant: { ButtonType: 'Responsive' },  // ✅ Exact match
props: {
  size: figma.enum('Size', { ... }),    // ✅ Exact match
  variant: figma.enum('Type', { ... }), // ✅ Exact match
}
Show full SKILL.md (349 more words)Show less
Only Use Real Figma Properties

Map based on what exists in Figma:

  • Component properties → figma.boolean(), figma.string(), figma.instance()
  • Variant properties → figma.enum()
  • Text layers → figma.textContent('LayerName')
  • Nested instances → figma.children('LayerName') or figma.children('*')
  • Child component props → figma.nestedProps('LayerName', { ... })

Never invent properties that don't exist in Figma.

Value Conventions
  • Drop pseudo-state variants: hover, pressed, focused, state, interaction
  • Map Figma Title Case to code: Primary → 'primary', Small → 'sm'
  • Normalize boolean variants: "Yes"/"No", "True"/"False", "On"/"Off" → true/false
Critical Constraint: No JavaScript Expressions

Code Connect snippets are strings, NOT executed code.

NEVER use:

tsx
{hasIcon && <Icon />}
{disabled ? 'disabled' : ''}
{icon || <Fallback />}

Instead, use mapping objects:

tsx
figma.boolean('Has Icon', {
  true: <Icon />,
  false: undefined
})

API Reference

Basic Helpers
tsx
// String property
figma.string('Label')

// Boolean property (simple)
figma.boolean('Disabled')

// Boolean with mapping
figma.boolean('Has Icon', {
  true: <Icon />,
  false: undefined
})

// Conditional string based on boolean
figma.boolean('Has label', {
  true: figma.string('Label'),
  false: undefined
})

// Enum/Variant property
figma.enum('Size', {
  'Small': 'sm',
  'Medium': 'md',
  'Large': 'lg'
})

// Text content from a layer
figma.textContent('Button Label')

// Instance swap property (nested component)
figma.instance('Icon')

// Child instances by layer name
figma.children('Tab')
figma.children(['Tab 1', 'Tab 2'])
figma.children('Icon*')  // wildcard
figma.children('*')      // all children
Advanced Helpers
tsx
// Nested props - access child component's properties on parent
figma.nestedProps('Button Shape', {
  size: figma.enum('Size', { ... })
})

// className builder
figma.className([
  'btn-base',
  figma.enum('Size', { 'Large': 'btn-large' }),
  figma.boolean('Disabled', { true: 'btn-disabled', false: '' })
])

// Instance with type inference
figma.instance<React.FunctionComponent>('Icon')  // Returns component type
figma.instance<string>('Icon')                    // Returns string ID

// Access nested instance props in parent
figma.instance('Icon').getProps<{ iconId: string, size: 'sm' | 'lg' }>()

// Custom render for nested instance
figma.instance('Icon').render<{ id: string }>(props => <CustomIcon id={props.id} />)
Variant Restrictions

Only use this pattern when different Figma variants map to entirely different React components. If all variants map to the same React component with different props, use a single figma.connect():

tsx
figma.connect(PrimaryButton, 'https://...', {
  variant: { Type: 'Primary' },
  example: () => <PrimaryButton />
})

figma.connect(SecondaryButton, 'https://...', {
  variant: { Type: 'Secondary' },
  example: () => <SecondaryButton />
})

// Boolean variant restriction
figma.connect(IconButton, 'https://...', {
  variant: { 'Has Icon': true },
  example: () => <IconButton />
})

// Multiple variant combination
figma.connect(DangerButton, 'https://...', {
  variant: { Type: 'Danger', Disabled: true },
  example: () => <DangerButton />
})

Complete Example

tsx
import figma from '@figma/code-connect'
import { Button } from './Button'

figma.connect(Button, 'https://figma.com/design/abc123/File?node-id=1:2', {
  props: {
    variant: figma.enum('Variant', {
      Primary: 'primary',
      Secondary: 'secondary'
    }),
    size: figma.enum('Size', {
      Small: 'sm',
      Medium: 'md',
      Large: 'lg'
    }),
    disabled: figma.boolean('Disabled'),
    label: figma.textContent('Label'),
    icon: figma.boolean('Has Icon', {
      true: figma.instance('Icon'),
      false: undefined
    })
  },
  example: ({ variant, size, disabled, label, icon }) => (
    <Button variant={variant} size={size} disabled={disabled} icon={icon}>
      {label}
    </Button>
  )
})

Icon Connection Patterns

Icons as JSX Elements
tsx
// Icon component
figma.connect('https://...icon-url...', {
  example: () => <IconHeart />
})

// Parent using the icon
figma.connect(Button, 'https://...button-url...', {
  props: {
    icon: figma.instance('Icon')
  },
  example: ({ icon }) => <Button>{icon}</Button>
})
// Renders: <Button><IconHeart/></Button>
Icons as React Components
tsx
// Icon returns component reference (not JSX)
figma.connect('https://...icon-url...', {
  example: () => IconHeart  // No angle brackets
})

// Parent receives component type
figma.connect(Button, 'https://...', {
  props: {
    Icon: figma.instance<React.FunctionComponent>('Icon')
  },
  example: ({ Icon }) => <Button Icon={Icon} />
})
// Renders: <Button Icon={IconHeart} />
Icons as String IDs
tsx
// Icon returns string ID
figma.connect('https://...icon-url...', {
  example: () => 'icon-heart'
})

// Parent uses string
figma.connect(Button, 'https://...', {
  props: {
    iconId: figma.instance<string>('Icon')
  },
  example: ({ iconId }) => <Button iconId={iconId} />
})
// Renders: <Button iconId="icon-heart" />

What NOT to Do

These mistakes produce Code Connect files that fail silently or publish incorrect mappings:

  • Don't use get_design_context property names. MCP normalizes them to camelCase. The actual Figma property names are Title Case with spaces (e.g., Has Icon, ButtonType, Size). Use get_metadata output or the raw variant names from evidence files.
  • Don't invent properties that don't exist in Figma. If proposed-api.md lists a prop like className that has no Figma source, omit it from Code Connect entirely.
  • Don't use JavaScript expressions in example templates. {hasIcon && <Icon />} is invalid — Code Connect snippets are static strings. Use figma.boolean('Has Icon', { true: <Icon />, false: undefined }) instead.
  • Don't skip the tsc --noEmit check. Run it after writing the .figma.tsx file. A type error in the Code Connect file will break the publish step.
  • Don't map pseudo-states. hover, focus, pressed, active Figma variants have no corresponding props — exclude them from all figma.enum() and figma.boolean() calls.
  • Don't reference proposed-api.md by path during generation. The mapping contract must be inlined into your working context in Step 3. Reaching back to re-read it mid-generation means the context wasn't loaded correctly.

Output

Write raw file content only—no markdown fences, no explanations.

File location: {ComponentFolder}/{ComponentName}.figma.tsx

Example: src/components/inline-edit/EditableText/EditableText.figma.tsx

File must be immediately usable with npx @figma/code-connect connect publish.

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

Files

Just SKILL.md in figma/figma-connect-component of bitovi/ai-enablement-prompts.

Open the folder on GitHubat commit df229b1

Compare with similar skills

Figma Connect Component 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.

Figma Connect Component compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Figma Connect Component this skillbitovi/ai-enablement-prompts121—~3.3kAutomated safety check: PassMIT
Wonder BlocksKhan/wonder-blocks163—~3.2kAutomated safety check: PassMIT
Loora Design Guidelassejlv/loora140—~2.4kAutomated safety check: PassAGPL-3.0
Figma Useshepherdjerred/monorepo112—~946Automated safety check: PassGPL-3.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Integrating shadcn/ui Componentsgoogle-labs-code/stitch-skills8.4k4 repos~2.3kAutomated safety check: NotesApache-2.0

Similar skills

  • Wonder Blocks

    Khan/wonder-blocks

    Implements user interfaces using the Wonder Blocks (WB) design system — Khan Academy's React component library.

    163 GitHub stars~3.2k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Loora Design Guide

    lassejlv/loora

    Build, edit, refine, troubleshoot, and review polished responsive product interfaces through the Loora MCP server and its structured Canvas schemas.

    140 GitHub stars~2.4k tokensUpdated 12 days ago
    Frontend & DesignAuto-check passed
  • Figma Use

    shepherdjerred/monorepo

    This skill should be used when the user asks to "create a Figma design", "design in Figma", "make a Figma mockup", "create an app icon", "design UI", "render JSX to Figma", "export from Figma"…

    112 GitHub stars~946 tokensUpdated today
    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
  • Integrating shadcn/ui Components

    google-labs-code/stitch-skills

    Official

    Guides finding, installing, customizing and wiring up shadcn/ui components in a project, with MCP tools for the component catalog and registries.

    8.4k GitHub starsUsed in 4 repos~2.3k tokens
    Frontend & DesignAuto-check: notes
  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Frontend & DesignAuto-check passed

More from bitovi/ai-enablement-prompts

All 40 skills in this repo
  • Component Registry

    bitovi/ai-enablement-prompts

    Track reusable UI components and unextracted patterns. An agent skill from bitovi/ai-enablement-prompts.

    121 GitHub stars~597 tokensUpdated 28 days ago
    Auto-check passed
  • Computed Styles

    bitovi/ai-enablement-prompts

    Extract and compare computed CSS styles between a baseline URL and a dev/Storybook URL using Playwright MCP evaluate calls.

    121 GitHub stars~2.4k tokensUpdated 28 days ago
    Auto-check passed
  • Create Plugin

    bitovi/ai-enablement-prompts

    A skill your agent uses when the user asks to "create a plugin", "add a plugin", "make a new plugin", "build a plugin", or wants to package skills into an installable plugin for this marketplace.

    121 GitHub stars~2k tokensUpdated 28 days ago
    Auto-check passed
  • Create React Modlet

    bitovi/ai-enablement-prompts

    Create React components, hooks, or utilities following the modlet pattern.

    121 GitHub stars~2.1k tokensUpdated 28 days ago
    Auto-check passed
  • Create Skill

    bitovi/ai-enablement-prompts

    A skill your agent uses when the user asks to "create a skill", "add a skill", "make a new skill", "build a skill", or wants to automate a repeated workflow into a reusable prompt.

    121 GitHub stars~1.6k tokensUpdated 28 days ago
    Auto-check passed
  • Create Skill

    bitovi/ai-enablement-prompts

    Create new Agent Skills for this project. An agent skill from bitovi/ai-enablement-prompts.

    121 GitHub stars~1.7k tokensUpdated 28 days ago
    Auto-check passed

Questions about Figma Connect Component

What does Figma Connect Component do?

Generate Figma Code Connect mappings that link React components to their Figma counterparts. Figma Connect Component is an agent skill from bitovi/ai-enablement-prompts. Generate Figma Code Connect mappings that link React components to their Figma counterparts.

When should I use Figma Connect Component?

Figma Connect Component fits situations like: A component exists in code and needs a Code Connect file so Figma shows real code snippets in Dev Mode; phrases like connect this component to Figma; generate Code Connect; publish to Figma.

How do I install Figma Connect Component in Claude Code?

Run `npx skills add bitovi/ai-enablement-prompts --skill figma-connect-component -a claude-code`. Or copy the skill folder (figma/figma-connect-component in bitovi/ai-enablement-prompts) into .claude/skills/figma-connect-component in your project. Claude Code loads it when a task matches its description.

How do I install Figma Connect Component in Codex?

Run `npx skills add bitovi/ai-enablement-prompts --skill figma-connect-component -a codex`. Or copy the skill folder (figma/figma-connect-component in bitovi/ai-enablement-prompts) into .agents/skills/figma-connect-component in your project. Codex loads it when a task matches its description.

Can I use Figma Connect Component 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 bitovi/ai-enablement-prompts --skill figma-connect-component -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/figma-connect-component, .gemini/skills/figma-connect-component, .github/skills/figma-connect-component and .opencode/skills/figma-connect-component in your project.

What does Figma Connect Component need to run?

Going by SKILL.md and its folder, Figma Connect Component needs the command-line tools its instructions call (tsc and npx).

Does Figma Connect Component access the network?

SKILL.md names 1 domain. In commands or code: figma.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Figma Connect Component 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. Review the folder before installing.

What licence does Figma Connect Component use?

Figma Connect Component is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Figma Connect Component use?

About 3.3k tokens (SKILL.md is roughly 13k 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 Figma Connect Component?

Skills that share tags, products or a category with Figma Connect Component: Wonder Blocks (Khan/wonder-blocks, 163 stars), Loora Design Guide (lassejlv/loora, 140 stars), Figma Use (shepherdjerred/monorepo, 112 stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Figma Connect Component?

bitovi (a GitHub organization) maintains it in bitovi/ai-enablement-prompts, which has 121 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on September 11, 2026.

Source: bitovi/ai-enablement-prompts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.