I think I have over 250+ skills installed.
Here’s the one that ties them together.

Building a toolkit is easy. The hard part is knowing which piece of it to reach for, right now, in this project. This is how I solved that.

I’ve been building out my agent skills toolkit for a while. Things like /polish, /animate, /delight, /critique, /typeset. All useful. All slowly fading from my memory.

You open a project and your head is already in the code. You’re not stopping to think “which skill applies here?” You’re thinking about the feature. The deadline. The thing that feels slightly off but you can’t name it yet.

So I built a skill for that.

npx skills add iamichieuche/theres-a-skill-for-that -y -g

The idea

Kaizen (改善) is Japanese for continuous improvement. Small changes that add up over time. That felt like the right name for a skills pack.

The first skill in the pack is /theres-a-skill-for-that. It’s a skill advisor for designers, builders, design engineers, and developers who care about craft and want their products to look, move, and feel better. Not test coverage, not bundle size. The stuff you can actually see.

It just makes a call.

Drop it into any project (a Next.js app, a SwiftUI prototype, some half-finished landing page) and it reads the room. Your stack, recent git changes, what files you’ve been touching. Then it checks your installed skills and the skills.sh catalog and tells you what to actually run.

It knows the difference between a project that needs motion work and one that needs its design system sorting out. Between a UI that’s almost there and one that needs a rethink. It figures out what phase you’re in and gives you a specific answer for right now.

How it works

It runs in three stages before it ever responds to you.

01
Reads the project
Scans package.json, git log, recent diffs, what libraries you’re using, what you’ve been working on.
02
Checks your installed skills
Looks through everything in ~/.claude/skills/ and ~/.agents/skills/. Matches what it found to what you have.
03
Checks skills.sh for gaps
Scans the full public catalog. If there’s something worth adding, not just nice-to-have but something that fills a real gap, it gives you the install command.

Then it gives you one to three skills. Never more. If one clearly fits, it says one. If two work well together (say, /animate and /delight before a launch) it’ll say both, tell you why, and which one to run first.

The recommendations are specific to what it actually found in your project. Not generic. Not “you could run /polish at any time.” It tells you why this skill, right now.

Usage

Run it with no arguments for a full project read;

/theres-a-skill-for-that

Or give it context about what you’re trying to do;

/theres-a-skill-for-that before we launch
/theres-a-skill-for-that the animations feel wrong
/theres-a-skill-for-that push the UI further

Works in

and any other agent that supports the skills format.

Install

The whole pack installs in one command. Right now it’s just /theres-a-skill-for-that, with more coming.

# Install globally
npx skills add iamichieuche/theres-a-skill-for-that -y -g

# Then use it anywhere
/theres-a-skill-for-that

The more skills you have installed, the better it gets. The “run now” picks only from what’s installed, so a bigger toolkit means sharper calls. It always checks skills.sh too, and if you’re missing something that would actually help, it tells you what to add.

Built with Claude Code and /theres-a-skill-for-that.
Source on GitHub.