Bunch of cool and useful AI skills

Some of the best people in software are writing down how they work, as skills your coding agent can load. Install one and your agent picks up their habits: how they plan, how they test, which easing curve they'd choose.

What a skill is

A skill is a folder with one Markdown file in it, SKILL.md. The top lines say what the skill is and when to use it. Your agent reads only those until the work matches, then loads the rest and follows it.

There's nothing to run and no server to host. The same folder works in Claude Code, Codex, Cursor, GitHub Copilot and Gemini CLI, so a skill you like keeps working when you switch tools.

---
name: tdd
description: Test-driven development. Use when the user
  wants to build features or fix bugs test-first, mentions
  "red-green-refactor", or wants integration tests.
---

# Test-Driven Development

TDD is the red → green loop. This skill is the reference
that makes that loop produce tests worth keeping...

See [tests.md](tests.md) for examples and
[mocking.md](mocking.md) for mocking guidelines.

Four that change how you build

Agents are quick to write code and slow to ask whether it's the right code. These four put the questions, the tests and the review back in.

Superpowers, by Jesse Vincent

A whole way of working, as skills that switch on by themselves. Before it writes any code, the agent asks what you're really trying to do and shows you the spec in chunks short enough to read. Then it writes a plan, hands each task to a subagent, tests red then green, and reviews the work before moving on. Its README says a couple of hours of work without drifting off the plan is common.

Install in Claude Code: /plugin install superpowers@claude-plugins-official

Skills for Real Engineers, by Matt Pocock

Small skills that each do one job, straight from the TypeScript teacher's own setup. Start with /grill-me: the agent interviews you about a plan in rounds, gives its recommended answer to every question, and keeps going until nothing is left to guess. /tdd, /diagnosing-bugs and /improve-codebase-architecture are the next ones to try.

Install in Claude Code: claude plugin install mattpocock-skills@claude-plugins-official

gstack, by Garry Tan

The Y Combinator CEO's own setup turns your agent into a small team. /office-hours pushes back on how you've framed the idea and writes a design doc. /review hunts for bugs that pass CI and still break in production. /qa opens a real browser and reproduces them. /ship runs the tests, the review and the pull request. His own advice: start with the first three and stop there, and you'll know if it's for you.

Install: it needs Bun. Paste the install line from the gstack README into Claude Code, and it clones and sets itself up.

ub-mode, by Robert C. Martin

Uncle Bob, who wrote Clean Code, put his rules into one skill. First make it work: write the test first, question the premise, take something away before you add. Then make it right, checked by tools instead of the model's opinion: every function stays under a complexity and coverage score of 10, duplicated code gets caught, and mutation testing finds what your tests miss.

Install: copy its SKILL.md to ~/.claude/skills/ub-mode/ and run /ub-mode. The checks use his crapper, dryer and mutator tools.

"Agents don't have great taste." Emil Kowalski

Four that raise the design bar

Ask an agent for a page with no other guidance and you get the same one every time: Inter for everything, a purple gradient, cards inside cards. These four write a designer's judgement down so the agent can use it.

Skills for Designers and Engineers, by Emil Kowalski

Emil made the Sonner toast library and worked at Vercel and Linear, and his README opens with that line. His 16 skills list the small mistakes agents make, mostly in motion, and how to fix them. /review-animations checks your motion against his rules, /animation-performance fixes the animations that drop frames, and /break-ui throws worst-case data at your interface: long names, empty lists, huge counts.

Install: npx skills@latest add emilkowalski/skills

Impeccable, by Paul Bakaus

From the creator of jQuery UI, a design vocabulary you point at one thing at a time: /impeccable bolder the pricing cards, quieter the landing page, polish settings. critique gives a scored UX review, and audit checks accessibility, performance and layouts on every screen size, ranking what it finds from P0 to P3. Its 62 fixed rules catch the usual AI tells without calling a model.

Install: npx impeccable install, then /impeccable init in your project.

Stageshow, by Benji Taylor

Fake product UI that looks like the real product: stills, feature cards, cursor demos and bento grids, built in React. It films what it made, so the agent can check its own work for jumps and text that spills out of its box. We added it to our own repo this week for our marketing pictures.

Install: npx skills add benjitaylor/skills --skill stageshow

Agent Skills, by Meng To

The Design+Code founder's library is the biggest here, with 176 skills. Start with Video to Super Prompt, which turns a screen recording of a site into a prompt detailed enough to build it from, then look through the GSAP scroll motion, the Three.js scenes and 14 illustration styles.

Install: copy the skill folders you want from the repo into ~/.claude/skills/.

Read a skill before you install it

A skill is instructions your agent follows with your permissions. That's what makes it useful, and it's why you should read it first. It's a short Markdown file, so this takes minutes. Look for four things:

• What it runs. Some skills come with scripts and command-line tools.
• What it changes outside itself. gstack's install line also adds rules to your CLAUDE.md.
• What it tells the agent to add. A skill can ask your agent to put links or promotions into your work.
• What it sends home. Superpowers says in its README that an optional feature loads a logo from its site with the version number, and how to turn that off. That's the kind of note to look for.

Give the skills to your whole team

Installed this way, a skill lives on one laptop. Your teammates don't get it, and neither do the machines doing work in your workspace.

In WeMachines, put the SKILL.md under .claude/skills or .wemachines/skills in your repo and press Sync from repo on the Skills page. Switch each skill on for the team, then choose which machine uses which in its settings. Anyone on the team can write a skill there too, without touching the repo.

Every install line in one place

Start with one. Pick the step where your agent lets you down most, install the skill for it, and read it before you run it.