npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ykb-ui/figma-copilot

v0.1.0

Published

VS Code Copilot agents, prompts, and instructions for building with ykb-ui from Figma MCP and Code Connect.

Downloads

146

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

murathanakinmurathanakin

Keywords

Readme

@ykb-ui/figma-copilot

VS Code Copilot assets for implementing Figma designs with Figma MCP, Code Connect, and ykb-ui.

This package is the source for templates that consumer repositories can install into their own .github folders.

Target Workflow

  1. Figma MCP exposes the selected Figma frame or frame URL to VS Code Copilot.
  2. Code Connect resolves Figma components to real ykb-ui components, imports, props, and examples.
  3. The YKB UI Figma Builder custom agent applies repository conventions and generates local code.
  4. The developer reviews and tests changes locally before opening a pull request.

Install Command

Run this from the consumer repository root:

npx @ykb-ui/figma-copilot init

Useful options:

npx @ykb-ui/figma-copilot init --dry-run
npx @ykb-ui/figma-copilot init --check
npx @ykb-ui/figma-copilot init --force

Template Output

.github/
  agents/
    ykb-ui-figma-builder.agent.md
  prompts/
    figma-to-page.prompt.md
    figma-to-component.prompt.md
    review-ykb-ui-usage.prompt.md
  instructions/
    ykb-ui.instructions.md
  copilot-instructions.md

VS Code Usage

After the templates are installed into a consumer repository:

  • Select the YKB UI Figma Builder agent from Copilot Chat.
  • Run /figma-to-page <Figma frame URL> to generate a local page.
  • Run /figma-to-component <Figma frame or component URL> to generate a reusable component.
  • Run /review-ykb-ui-usage to review generated code for ykb-ui and Code Connect alignment.

The Figma MCP server is assumed to be named figma. If a consumer repository uses a different MCP server name, update the tools in .github/agents/ykb-ui-figma-builder.agent.md.

Existing .github Files

The init command preserves consumer-owned files.

  • If a target file does not exist, create it.
  • If .github/copilot-instructions.md exists, append or update only the managed ykb-ui section.
  • If a package-owned prompt or agent file exists with ykb-ui markers, update it.
  • If a conflicting file exists without ykb-ui markers, report the conflict instead of overwriting it.
  • Use --dry-run to preview changes without writing files.
  • Use --check to verify whether the repository is already up to date.
  • Use --force to overwrite conflicting package-owned files.

Managed sections use these markers:

<!-- ykb-ui-figma-copilot:start version="0.1.0" -->
<!-- ykb-ui-figma-copilot:end -->

Current Scope

V1 details the Button mapping only. Other common components have placeholder sections in ykb-ui.instructions.md so future mappings can be added without changing the file structure.