AI skills are the new NPM packages

We used to share code. Now we share intent. For years, our industry has been built around one core idea: reuse. npm packages, shared libraries, frameworks — all ways to take someone else's solution and plug it into our own system. It worked. It scaled. It shaped how we build software. But there's always been a hidden cost. When you import a package, you're not just importing functionality — you're importing decisions. Architecture choices, naming conventions, constraints, trade-offs made by someone else, often in a different context. Sometimes that's exactly what you want. Other times, it's friction you carry for the lifetime of your product. From code to knowledge I've been thinking about this a lot lately, especially with the rise of AI in our workflows. And I keep coming back to the same idea: AI skills are becoming the new npm packages. But instead of distributing opinionated implementations, we're starting to distribute something more flexible — and arguably more valuable: experti