# Skills Index (antigravity-awesome-skills)

The reference for which skills to reach for on this project, and how.

## Setup / how skills work here
- **~1,588 skills installed** at `~/.claude/skills/` (from `sickn33/antigravity-awesome-skills`).
- **Update:** `npx -y antigravity-awesome-skills@latest --claude`.
- **Invoke:** the harness auto-surfaces a *subset* each session. To use any installed
  skill regardless, the user (or I, when surfaced) calls **`/<skill-name>`** → it becomes
  callable via the Skill tool. Always tell the user which skill was used.
- **Discover more:** `ls ~/.claude/skills | grep -i <topic>` (1,588 is too many to list here).
- **Vet before trusting an unknown one:** `/skill-audit` (a pre-install scanner — some skills
  in large catalogs are malicious). Prefer the curated list below.

## Project shortlist — reach for these (all confirmed installed)

| Skill | When to use |
|---|---|
| `tailwind-design-system` | design tokens / Tailwind build / theming / component variants (the aurora build) |
| `tailwind-patterns` | concrete Tailwind v4 component + layout patterns, container queries |
| `frontend-design` · `ckw-design` · `emil-design-eng` · `antigravity-design-expert` | UI/UX fidelity when matching a demo screen (look, spacing, interaction craft) |
| `deterministic-design` | prove a ported screen is balanced/usable (layout audit + screenshot) |
| `frontend-dev-guidelines` · `frontend-developer` · `cc-skill-frontend-patterns` | frontend structure / JS quality |
| `backend-dev-guidelines` · `php-pro` · `cc-skill-backend-patterns` | Yii2 / PHP controller + service work |
| `architect-review` · `code-reviewer` · `brooks-lint` · `logic-lens` · `bugs-are-annoying` | adversarial review — pair with verify-wave agents |
| `cc-skill-security-review` · `production-audit` | security / production-readiness pass |
| `accesslint-audit` · `accessibility-compliance-accessibility-audit` · `pagespeed-enhancer` | a11y + performance pass on ported screens |
| `webapp-testing` · `playwright-skill` · `tdd` | browser verification / test-first |
| `skill-creator` · `yao-meta-skill` | author a new project-specific skill when a recurring need emerges |

## Project-local skills (in `.claude/skills/` — gitignored, this machine)

Custom skills written for THIS project (2026-07-06). Invoke with `/<name>`; they encode the
playbook + memory gotchas as executable checklists:

| Skill | When to use |
|---|---|
| `aurora-port` | porting any demo screen/modal — enforces "see the rendered demo first", real-DB wiring, wave rules |
| `verify-portal` | after any portal change — lint, curl smoke, `render-smoke.sh`, authed login, **interaction test**, demo comparison |
| `i18n-guard` | adding/reconciling bilingual strings — categories/fileMap, Arabic-guard script (missing keys + non-Arabic ar values) |
| `yii-migrate` | schema changes — naming/docblock conventions, idempotent seeds, apply commands, API-impact gate |
| `api-impact` | before any data-model/API change — decides "portal-only, proceed" vs "shared mobile contract, flag first" |
| `aurora-scaffold` | new aurora page/modal/form — layout choice, ngIframeModal/postMessage wiring, JS boot pattern (anti-inert-form) |

## How this fits the porting flow ([[AURORA_DEMO_PORTING_PLAYBOOK]])
- Building/matching a demo screen → `tailwind-design-system` / `frontend-design` for the build,
  `deterministic-design` to prove the result.
- Wave **Verify** phase → run `code-reviewer` / `architect-review` / `cc-skill-security-review`
  on the diff; `accesslint-audit` on the rendered screen.
- Backend (controller/service/endpoint) → `backend-dev-guidelines` / `php-pro`.

Keep this list curated — add a skill here only after it proves useful on this project.