SKILLS

Claude Code skills built for real work, not demos.

Two kinds live here:

• Distilled — a public corpus turned into something an agent can actually use. Apple's Human Interface Guidelines is the first: 171 verbatim pages plus the hard specs Apple doesn't publish as text.
• Hand-crafted — workflow skills written out of months of daily agent use, encoding the rules that stopped repeat mistakes.

Every skill is plain Markdown. No install step, no runtime, no dependencies. All of them are written to be project-agnostic: no hardcoded personal paths, no assumed tooling beyond what the skill names.

Skills

Design

Skill	What it does
apple-hig	Apple HIG as a working design reference for iOS/iPadOS 26+ (Liquid Glass). Dynamic Type scale, SF Pro tracking, system color hex, device metrics, layout margins, plus the full component/foundation/pattern corpus. Build, audit, or retrofit UI that has to look Apple-native — on SwiftUI/UIKit or on the web.

Engineering discipline

Skill	What it does
gate-isolate	Debug-to-truth loop for non-trivial bugs. Gate the surface → instrument the boundary → isolate a faithful env → prove cause and fix with the same probe. Kills the plausible-but-wrong guess cycle, where each bad theory costs a full fix round.
ship	Git and deploy ritual behind an explicit green-light gate. One approval covers exactly one action — "fix it" is not "commit it", "commit" is not "push". Conventional commits, committer-identity check, repo-level bans read first.
rls-audit	Authorized self-audit of your own Supabase projects: what the anon key actually reaches, RLS gaps, service-role exposure. Enumerate the public surface, test as anon, report findings by severity.
rls-enforce	The other half of the pair — consumes rls-audit's findings and closes each one. A pattern library per table class (owner-scoped CRUD, open-read/closed-write, PII lockdown, definer-function gateway), applied as idempotent migrations with paired reverts, then re-verified.

Repo knowledge

Skill	What it does
digest	Cold-open an unfamiliar repo, read-only. Docs → identity → shape → data → runtime, cheap to deep, stopping when the picture is clear. Changes nothing.
document	Capture one session's work into the repo's docs. Captures the why — intention vs implementation, decisions and rejected alternatives — because git already records the what.
full-document	Whole-repo documentation pass. Gap-audits documented vs undocumented subsystems, presents the work plan first, then writes until a cold maintainer can understand the system without reading the code.
runbook	Mines the repo, local agent rules, and past sessions into one operational card: IDs, tenants, health checks, deploy and git rules. The card other skills read instead of re-asking.
initiate	Project cold start — PRD → scaffold → docs → task seeding. Setup and alignment only; no feature code during initiation.

SEO

Skill	What it does
seo-health	Technical and on-page sanity pass. Crawlability, indexation, meta, schema, per-page checks — Pass/Warn/Fail. The floor that gates every other SEO effort. Not keyword work.
seo-campaign	Engineers a full 6-month campaign from zero: research bank, strategy, locked KPI plan, task queue. Builds the campaign; other loops run it.
technical-seo-audit	Reads a crawl export (Screaming Frog, Sitebulb, Ahrefs) and returns a prioritised, plain-English issue list — redirect chains and loops, duplicate titles, non-indexable pages, broken internal links, orphans. Ships with sample input and output. Third-party: built by StudioHawk for Hawk Academy, included as-is.

More are being moved in.

Conventions

Two things the workflow skills assume, both swappable:

• Docs folder. They read and write repo documentation under .docs/. If your project keeps docs elsewhere (docs/, .github/, a wiki), change the path — nothing else depends on the name.
• The runbook. Several skills expect a per-repo operational card (IDs, test tenants, health checks, deploy and git rules) so they don't have to re-ask for project facts every session. runbook generates it; the others read it if it exists and degrade gracefully if it doesn't.

Skills that touch git, deploys, paid API credits, or production data are approval-gated by design. They state the plan and stop. That is deliberate — leave it in.

Install

Drop a skill folder into your skills directory:

git clone https://github.com/danielimad/SKILLS.git
cp -R SKILLS/apple-hig ~/.claude/skills/     # one skill
cp -R SKILLS/*/ ~/.claude/skills/            # all of them

Per-project instead of global: copy into .claude/skills/ inside the repo.

Claude picks it up from the description in SKILL.md — no registration needed. Invoke explicitly with /apple-hig, or just describe the task ("make this screen look native iOS", "why is this screen blank") and the right skill loads on its own.

Structure

Most skills are a single file:

ship/
  SKILL.md              the whole skill

Reference-heavy ones split:

apple-hig/
  SKILL.md              entry point — always loaded
  references/
    _index.json         machine-readable map of all pages
    _specs-*.md         digests: typography, color, layout, geometry
    <topic>.md          171 verbatim HIG pages, slug = filename

SKILL.md stays small and stays loaded. references/ is read on demand — the skill tells the agent which file answers which question instead of dumping 1.8 MB into context.

That split is the whole design. A skill that loads everything is a skill that runs out of room.

Provenance

apple-hig is crawled from developer.apple.com/tutorials/data/design/human-interface-guidelines/*.json — Apple's own backing API for the HIG site, so the prose is verbatim rather than paraphrased. Each page carries its source URL and update date. Color hex values aren't published as text; they were recovered by sampling Apple's swatch images at 2x and validated against known constants.

Corpus stamped 2025-12-16 or later. Refresh after a WWDC by re-running the crawl and diffing updated in _index.json.

Contributing

Issues and PRs welcome, with one bar: a skill has to earn its context. Additions should be things you've actually run against real work, with numbers verified against a primary source. Keep skills project-agnostic — no personal paths, no private references a reader can't follow.

License

MIT for the skill authoring, with two exceptions:

• apple-hig reproduces content from Apple's public developer documentation for reference use. Apple trademarks and copyrights belong to Apple Inc. This project is not affiliated with or endorsed by Apple.
• technical-seo-audit was authored by StudioHawk and is included with its attribution intact. It ships without its own license file; check with the original authors before redistributing it separately.