# I think AI coding assistants need an "npm" for reusable skills. I'm building one.

> Source: <https://dev.to/harsh_singh_2f42f847185ce/i-think-ai-coding-assistants-need-an-npm-for-reusable-skills-im-building-one-15gf>
> Published: 2026-07-11 06:02:28+00:00

I've been using multiple AI coding assistants (Claude Code, Cursor, Codex, Copilot, Gemini CLI, Windsurf, etc.) over the past few months, and I noticed the same problem everywhere.

Every assistant has its own way of defining skills, rules, or prompts.

If I build a useful skill for one assistant, I have to rewrite and maintain it separately for every other assistant.

That feels a lot like JavaScript before npm or containers before Docker.

So I started building **Kitbash**.

It's **not another AI coding assistant**.

The goal is to create an **open standard for portable AI skills**.

Some ideas I'm exploring:

It's still **pre-alpha**, so I'm mainly looking for feedback on the architecture and whether this is actually a problem worth solving.

🌐 Landing Page: [https://singhharsh1708.github.io/kitbash/](https://singhharsh1708.github.io/kitbash/)

💻 GitHub: [https://github.com/singhharsh1708/kitbash](https://github.com/singhharsh1708/kitbash)

I'd love to hear your thoughts.