akakika-skills

I had a folder with hundreds of agent skills — some I wrote, a lot I collected, plenty half-finished. The good ones were buried under auto-generated stubs and notes-to-self. If someone asked "which of these are actually good," I couldn't have answered without digging for an hour. And none of it was anywhere anyone else could use.

The idea was simple: pick only the ones I would actually hand to another builder, clean each one to the same bar, and put them somewhere public. Not everything — the best two dozen. Quality over a big pile.

THE FRICTION

A skills folder is easy to grow and hard to maintain. Mine had sprawled past the point where I could tell what was worth keeping. The friction was not that the skills were bad — it was that the good ones had no way to stand out. Every time I reached for a skill I trusted, I had to wade past a dozen I didn't. The cleanup was overdue.

• Hundreds of skills, most half-finished or auto-generated — the signal-to-noise ratio was terrible.
• No way to answer "which ones are actually good" without an hour of digging through folders.
• Nothing public — all of it sat on my disk, invisible to anyone else who might find it useful.

WHAT IT DOES

akakika-skills collects 28 agent skills, organized into eight plain categories. It covers what I actually build with: Apple HIG and SwiftUI, macOS app details, AI-agent workflows, reading an unfamiliar codebase, project upkeep, and launch polish. Each skill is one self-contained folder with a SKILL.md — no build step, no dependencies. You read it, copy it, or drop it into your agent. It stays tool-agnostic: works with Claude Code, Codex, Cursor, or anything that reads the format.

It is nicer to keep one small thing polished than to maintain a folder of "someday."

HOW IT WORKS

Every skill is a folder: a short SKILL.md with a name, a "use when..." line so the agent knows when to reach for it, and then the actual guidance — rules, code, checklists. No build step, no dependencies. You read it, copy it, or drop it into your agent.

1. Find the skill you need. The README is a plain index so you can see all 28 at a glance — each with a one-line description of what it teaches the agent to do.
2. Drop it into your agent. Copy the folder into ~/.claude/skills, or your project's skills folder, or just open the SKILL.md and paste the part you need.
3. The agent reads it and knows when to use it. Each SKILL.md has a trigger line — "use when the user mentions X" — so the agent reaches for the right skill at the right time.

WHO IT IS FOR

Builders who use Claude Code, Codex, or Cursor and want skills that are specific and complete, not generic prompt filler. Especially anyone making native Apple apps — the collection leans hard into Apple HIG, SwiftUI, and macOS because that is what I build. But the agent-workflow and project-upkeep skills are useful no matter what stack you are on. The whole thing is MIT licensed and small on purpose — I would rather it stay tight and good than grow for the sake of it.