opencode-skills-collection 3.0.49 → 3.0.51

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-06-17T02:33:08.008Z",
+  "updatedAt": "2026-06-19T02:46:58.138Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -119,6 +119,7 @@
     "app-store-changelog",
     "app-store-optimization",
     "appdeploy",
+    "apple-notes-search",
     "application-performance-performance-optimization",
     "architect-review",
     "architecture",
@@ -352,6 +353,7 @@
     "circleci-automation",
     "cirq",
     "citation-management",
+    "ckw-design",
     "claimable-postgres",
     "clarity-gate",
     "clarvia-aeo-check",
@@ -512,6 +514,7 @@
     "design-orchestration",
     "design-spells",
     "design-taste-frontend",
+    "deterministic-design",
     "devcontainer-setup",
     "development",
     "devops-deploy",
@@ -882,6 +885,8 @@
     "logistics-exception-management",
     "loki-mode",
     "longbridge",
+    "lookdev",
+    "lookdev-auto",
     "loss-aversion-designer",
     "lovable-cleanup",
     "m365-agents-dotnet",
@@ -889,6 +894,7 @@
     "m365-agents-ts",
     "machine-learning-ops-ml-pipeline",
     "macos-menubar-tuist-app",
+    "macos-screen-recorder",
     "macos-spm-app-packaging",
     "magic-animator",
     "magic-ui-generator",
@@ -1100,6 +1106,7 @@
     "postmortem-writing",
     "powershell-windows",
     "pptx-official",
+    "pr-merge-champion",
     "pr-writer",
     "price-psychology-strategist",
     "pricing-strategy",
@@ -1215,6 +1222,7 @@
     "scikit-learn",
     "screen-reader-testing",
     "screenshots",
+    "screenstudio-alt",
     "scroll-experience",
     "seaborn",
     "search-specialist",
@@ -1365,6 +1373,23 @@
     "subagent-orchestrator",
     "subject-line-psychologist",
     "supabase-automation",
+    "super-code",
+    "super-code/bash",
+    "super-code/c",
+    "super-code/cpp",
+    "super-code/csharp",
+    "super-code/dart",
+    "super-code/elixir",
+    "super-code/go",
+    "super-code/java",
+    "super-code/kotlin",
+    "super-code/php",
+    "super-code/python",
+    "super-code/ruby",
+    "super-code/rust",
+    "super-code/scala",
+    "super-code/swift",
+    "super-code/typescript",
     "superpowers-lab",
     "supply-chain-risk-auditor",
     "sveltekit",
@@ -1514,6 +1539,7 @@
     "wcag-audit-patterns",
     "web-artifacts-builder",
     "web-design-guidelines",
+    "web-media-getter",
     "web-performance-optimization",
     "web-scraper",
     "web-security-testing",

package/bundled-skills/ab-test-setup/SKILL.md

@@ -127,6 +127,20 @@ Estimate:
 
 ---
 
+### Tracking Verification (Required before Gate 8)
+
+Before entering the Execution Readiness Gate below, run through this checklist to make "Tracking is verified" mean something concrete:
+
+1. **Event firing:** Trigger each event the primary and secondary metrics depend on (sign-up, add-to-cart, custom event) on staging or a debug page, and confirm it lands in your analytics destination within 30 seconds.
+2. **Variant attribution:** Verify that the variant assignment ID is attached to every fired event — not just the entry event. Use your analytics' raw event view to compare a sample of 5+ events per variant.
+3. **De-duplication:** Confirm that a user reloading the page does not cause double-counted events. If your stack uses client-side de-duping, the variant ID must be part of the dedup key.
+4. **Sample randomization:** Pull the first 100 assignment records from your assignment table; the variant split should be within ±5% of the configured allocation.
+5. **Guardrail metric pipeline:** Each guardrail metric defined in §6️⃣ must have a working dashboard or alert by the time the test launches.
+
+If any of the above fails, stop and resolve it before Gate 8.
+
+---
+
 ## 8️⃣ Execution Readiness Gate (Hard Stop)
 
 You may proceed to implementation **only if all are true**:

package/bundled-skills/apple-notes-search/SKILL.md

@@ -0,0 +1,122 @@
+---
+name: apple-notes-search
+description: "Semantic + keyword search and connection-discovery across the user's own Apple Notes via the apple-notes MCP server. Use when the user wants to find, recall, or synthesize something from their notes, or surface non-obvious bridges/related notes. macOS, on-device."
+risk: safe
+source: community
+source_repo: connerkward/mcp-apple-notes
+source_type: community
+date_added: "2026-06-16"
+author: connerkward
+tags: [apple-notes, search, mcp, macos, semantic-search, knowledge]
+tools: [claude-code]
+license: "MIT"
+license_source: "https://github.com/connerkward/mcp-apple-notes/blob/main/LICENSE"
+---
+
+# Apple Notes search & connection-discovery
+
+`apple-notes` is an MCP server for semantic search and connection-discovery across the
+user's own Apple Notes — hybrid search, Swanson-ABC bridges, entity threads, and cited
+synthesis over everything they've written. Embeddings, search, BM25, clustering, and
+bridges run **on-device**; only **synthesis generation** calls an LLM (local OR cloud,
+the user's choice).
+
+This skill covers (1) the one-time setup you must walk the user through, and (2) which
+tool to reach for, since the server exposes many.
+
+## When to Use This Skill
+
+- Use when the user wants to **find, recall, or look up** something from their own Apple
+  Notes ("search my notes for X", "what did I write about X", "did I ever note Y").
+- Use when the user wants to surface **non-obvious connections** across their notes
+  ("find bridges/connections across my notes", "what links X and Y", "show related notes").
+- Use when the user wants to **synthesize a position** from their notes ("summarize what I
+  think about X from my notes", "pull together everything I've written on X").
+- Also use for "index my Apple Notes", tag/folder queries, and "what's connected to X".
+- Do **not** use for creating reminders, or for non-Apple-Notes note systems.
+
+## First: is the MCP connected?
+
+If `apple-notes` tools are not available, the server isn't registered yet — do the
+**Setup** below before anything else. If tools exist but a search returns "not indexed"
+or empty, run `index-notes` first (see Ranking caveats).
+
+## Setup (walk the user through this — it's the skill's real value)
+
+The server reads Apple Notes' SQLite store directly, so the **bun** binary needs Full
+Disk Access. Steps, in order:
+
+1. **Install bun** (if absent): `brew install oven-sh/bun/bun`
+2. **Clone + install deps:**
+   ```bash
+   git clone https://github.com/connerkward/mcp-apple-notes
+   cd mcp-apple-notes && bun install
+   ```
+3. **Grant Full Disk Access to bun.** Run `which bun`, then open System Settings →
+   Privacy & Security → Full Disk Access, click `+`, and add that exact `bun` binary
+   path (commonly `/opt/homebrew/bin/bun` or `/usr/local/bin/bun`). Without this the
+   server cannot read NoteStore.sqlite and every call fails with a permissions error.
+   (`bun install`'s postinstall tries to open this pane automatically.)
+4. **Register the MCP server** (pick the user's client):
+   - Claude Code: `claude mcp add apple-notes -- bun /absolute/path/to/mcp-apple-notes/index.ts --stdio`
+   - Claude Desktop: add to `claude_desktop_config.json`:
+     ```json
+     { "mcpServers": { "apple-notes": {
+         "command": "/Users/<you>/.bun/bin/bun",
+         "args": ["/Users/<you>/mcp-apple-notes/index.ts", "--stdio"] } } }
+     ```
+   - As a Claude Code plugin (bundles this skill too): `/plugin marketplace add connerkward/ckw-skills` then `/plugin install apple-notes@connerkward`.
+5. **Restart the client**, then tell the user to ask **"Index my Apple Notes"** (or call
+   `index-notes`). First index of ~1,800 notes takes a few seconds.
+
+## Tool map — which tool for which job
+
+| Tool | Use when |
+|------|----------|
+| `index-notes` | First run, or to force a rebuild. Background job with live progress. |
+| `search-notes` | **Default search.** Hybrid semantic + BM25, re-ranked. Optional `folder`, `modifiedAfter`, `modifiedBefore`. "What did I write about X." |
+| `find-notes` | Exact substring match (like the Apple Notes search box). Use when the user wants a literal string, not meaning. Optional `folder`, date range. |
+| `get-note` | Fetch one full note by title (fuzzy fallback). |
+| `list-notes` | Notes by recency. Optional `folder`, date range, `limit`. |
+| `list-folders` | All folders + note counts. |
+| `list-tags` / `search-by-tag` | `#hashtag` inventory / notes carrying a given tag. |
+| `related-notes` | Notes related to a given one via shared tags, `[[wikilinks]]`, and vector similarity. "Show me related notes." |
+| `bridge-notes` | **Swanson-ABC bridges** — non-obvious connections: pairs (A, C) not directly similar but both strongly tied to a shared intermediary B. "Find non-obvious connections across my notes." Optional `folder`, `limit`. No LLM. |
+| `feed` | Ranked evidence-first connection stream (bridges + abstraction pairs + entity threads) as JSON. Optional `limit`. |
+| `entity-notes` / `list-entities` | "Where else do I talk about Mercedes?" Entity chips → notes by mention weight. **Needs the optional entity graph db** (`~/.mcp-apple-notes/layered_graph.db`); if absent these report how to generate it. |
+| `get-tables` | Pull pipe/tab tables out of a note. |
+| `create-note` / `update-note` | Create or edit a note. |
+| `check-changes` | Did notes change since last index? (does not trigger re-index) |
+| `index-health` | Sync status, last-indexed time, note count. Run this if results seem stale. |
+
+For "synthesize what I think about X" the synthesis lives in the **web app** endpoint
+(`GET /api/synthesize?q=` at `http://localhost:3741/` when run with `bun index.ts`),
+which writes a grounded answer with inline `[n]` citations back to source notes.
+
+## Ranking caveats (state these when results look off)
+
+- **Index before the first search.** No index → empty/garbage results; run `index-notes`.
+- **Auto re-index:** each search does ~1ms change detection and kicks ONE background
+  incremental index if notes changed — search returns immediately from the current index
+  and catches up when the job lands. If a just-edited note is missing, it's the catch-up
+  lag; re-run the search.
+- **Score:** `score = RRF(vector, BM25) × title_boost × recency_factor`.
+- **Temporal queries** (`recent`, `latest`, `today`) auto-shift to a 1-day recency
+  half-life at 70% weight; normal queries keep relevance primary (90-day half-life, 10%).
+- **Synthesis is the only cloud-capable part.** It needs an LLM: local via LM Studio /
+  Ollama (`SYNTH_BASE_URL=http://localhost:1234/v1 SYNTH_MODEL=<model> OPENAI_API_KEY=local`,
+  notes stay on-device) or real OpenAI (funded `OPENAI_API_KEY`, defaults to `gpt-4o-mini`).
+  Everything else — embeddings, search, BM25, clustering, bridges, entities — is on-device.
+
+## Limitations
+
+- macOS and Apple Notes only; it does not search Obsidian, Notion, Google Docs, or other note stores.
+- The MCP server needs local filesystem permissions to read Apple Notes data, so setup cannot be completed purely inside a remote shell.
+- Search quality depends on a fresh local index. Recently edited notes may require `check-changes`, `index-health`, or a rerun after background indexing catches up.
+- Entity tools require the optional layered graph database; without it, use hybrid search, exact search, related notes, or bridges instead.
+
+## Credits
+
+Fork of [RafalWilinski/mcp-apple-notes](https://github.com/RafalWilinski/mcp-apple-notes);
+this fork reads SQLite + protobuf directly and adds bridges, entities, feed, and synthesis.
+Authored by [Conner K Ward](https://github.com/connerkward). License MIT.

package/bundled-skills/astropy/references/coordinates.md

@@ -0,0 +1,9 @@
+# astropy.coordinates — Reference
+
+This file is a placeholder for the extended `astropy.coordinates` reference promised in the skill workflow.
+
+For detailed coordinate frame descriptions, transformations, observer-dependent frames (AltAz), catalog matching, and performance tips, see the upstream astropy docs:
+
+- https://docs.astropy.org/en/stable/coordinates/
+- https://docs.astropy.org/en/stable/coordinates/frames.html
+- https://docs.astropy.org/en/stable/coordinates/matchsep.html

package/bundled-skills/astropy/references/cosmology.md

@@ -0,0 +1,8 @@
+# astropy.cosmology — Reference
+
+This file is a placeholder for the extended `astropy.cosmology` reference promised in the skill workflow.
+
+For available models, distance calculations, time calculations, density parameters, and neutrino effects, see the upstream astropy docs:
+
+- https://docs.astropy.org/en/stable/cosmology/
+- https://docs.astropy.org/en/stable/cosmology/realizations.html

package/bundled-skills/astropy/references/fits.md

@@ -0,0 +1,8 @@
+# astropy.io.fits — Reference
+
+This file is a placeholder for the extended `astropy.io.fits` reference promised in the skill workflow.
+
+For file operations, header manipulation, image and table handling, multi-extension files, and performance considerations, see the upstream astropy docs:
+
+- https://docs.astropy.org/en/stable/io/fits/
+- https://docs.astropy.org/en/stable/io/fits/usage/headers.html

package/bundled-skills/astropy/references/tables.md

@@ -0,0 +1,8 @@
+# astropy.table — Reference
+
+This file is a placeholder for the extended `astropy.table` reference promised in the skill workflow.
+
+For table creation, I/O operations, data manipulation, sorting, filtering, joins, grouping, and performance tips, see the upstream astropy docs:
+
+- https://docs.astropy.org/en/stable/table/
+- https://docs.astropy.org/en/stable/table/operations.html

package/bundled-skills/astropy/references/time.md

@@ -0,0 +1,7 @@
+# astropy.time — Reference
+
+This file is a placeholder for the extended `astropy.time` reference promised in the skill workflow.
+
+For time formats, time scales, conversions, arithmetic, observing features, and precision handling, see the upstream astropy docs:
+
+- https://docs.astropy.org/en/stable/time/

package/bundled-skills/astropy/references/units.md

@@ -0,0 +1,9 @@
+# astropy.units — Reference
+
+This file is a placeholder for the extended `astropy.units` reference promised in the skill workflow.
+
+For comprehensive documentation, unit systems, equivalencies, performance optimization, and unit arithmetic, see the upstream astropy docs:
+
+- https://docs.astropy.org/en/stable/units/
+- https://docs.astropy.org/en/stable/units/equivalencies.html
+- https://docs.astropy.org/en/stable/units/standards.html

package/bundled-skills/astropy/references/wcs_and_other_modules.md

@@ -0,0 +1,9 @@
+# astropy.wcs and other modules — Reference
+
+This file is a placeholder for the extended `astropy.wcs` (and related modules) reference promised in the skill workflow.
+
+For WCS operations and transformations, plus related modules (`astropy.modeling`, `astropy.constants`, `astropy.convolution`, etc.), see the upstream astropy docs:
+
+- https://docs.astropy.org/en/stable/wcs/
+- https://docs.astropy.org/en/stable/modeling/
+- https://docs.astropy.org/en/stable/constants/

package/bundled-skills/browser-extension-builder/SKILL.md

@@ -44,7 +44,7 @@ use daily. You know the difference between a toy and a tool.
 
 ## Patterns
 
-### Extension Architecture
+### Architecture Patterns
 
 Structure for modern browser extensions
 

package/bundled-skills/ckw-design/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: ckw-design
+description: "Frontend design entry point: direction, design system, visual philosophy. Use whenever building or touching the look of any web UI (components, pages, dashboards, React/Vue/HTML-CSS) or when the user says \"make this look better\", \"fix the spacing/layout\", or mentions styling, color, type, or polish."
+risk: safe
+source: community
+source_type: community
+source_repo: connerkward/ckw-design-skill
+date_added: "2026-06-16"
+author: Conner K Ward
+license: MIT
+tags:
+  - design
+  - frontend
+  - ui
+  - css
+  - typography
+  - responsive
+tools:
+  - claude-code
+  - antigravity
+  - cursor
+  - gemini-cli
+  - codex-cli
+---
+## When to Use
+
+Use whenever building or styling web UIs — components, pages, dashboards, landing pages, React/Vue/HTML-CSS layouts — or whenever the user asks to make something "look better/nicer", fix spacing/layout, or mentions styling, color, typography, fonts, responsive design, polish, or aesthetics, even without the word "design".
+
+_Source: [connerkward/ckw-design-skill](https://github.com/connerkward/ckw-design-skill) (MIT)._
+
+# Design (entry)
+
+Use this skill when the user asks to build or style web UIs: components, pages, dashboards, landing pages, React/Vue/HTML-CSS layouts, or any frontend interface. Goal: distinctive, production-grade output that avoids generic AI aesthetics.
+
+**Before reporting any design "done": render it and have a *separate* judge critique the image** (not the code, not self-grading) — see design-spatial §1. Blind generation can't see its own collisions; this applies to all design output, not just spatial work.
+
+> **MANDATORY HORIZONTAL-OVERFLOW GATE — runs before ANY web UI is "done".**
+> Measure `document.documentElement.scrollWidth - document.documentElement.clientWidth`
+> at a **narrow width (~390px and ~1024px), this turn**, and confirm it's `0`. This
+> bug is invisible at desktop width and re-appears every time a row (header, nav,
+> toolbar) gains an item, so it ships repeatedly. Default to `flex-wrap:wrap` on
+> header/toolbar rows + `body{overflow-x:clip}`, and **re-measure after adding any
+> element to a horizontal row.** Full procedure + recurrence cases: design-spatial §4.
+> If you haven't measured narrow, you are not done — don't claim it.
+
+## Sub-skills (load when relevant)
+
+- **design-thinking** — Load for every design task. Defines purpose, tone, domain, color world, review bar, and cross-domain lens (cinema, architecture, marketing, UX, automotive, industrial design). See [design-thinking/SKILL.md](https://github.com/connerkward/ckw-design-skill/blob/main/design-thinking/SKILL.md).
+- **design-system** — Load when implementing: tokens, typography, motion, color semantics, backgrounds. Use when building components, pages, or design systems. See [design-system/SKILL.md](https://github.com/connerkward/ckw-design-skill/blob/main/design-system/SKILL.md).
+- **design-spatial** — Load when composing layout: explicit grid + 8-point spacing constraints, visual-weight/balance/alignment, and a render-then-critique vision loop. The fix for "spatial understanding is off" — generated layout that's centered mush, misaligned, or breaks at some widths. See [design-spatial/SKILL.md](https://github.com/connerkward/ckw-design-skill/blob/main/deterministic-design/design-spatial/SKILL.md).
+- **design-ux** — Load when auditing USABILITY (not just looks): a UI that "feels off"/"sucks to use", is hard to learn, needs an instruction wall, or any interactive tool/editor/app before shipping. Scores the rendered UI against Nielsen's 10 + interaction heuristics via a SEPARATE fresh-eyes judge → prioritized fix list. Usability ≠ aesthetics. See [design-ux/SKILL.md](https://github.com/connerkward/ckw-design-skill/blob/main/deterministic-design/design-ux/SKILL.md).
+- **design-philosophy** — Load for high-concept work, campaigns, or when the user asks for a visual philosophy, manifesto, or unmistakable art-like aesthetic. See [design-philosophy/SKILL.md](https://github.com/connerkward/ckw-design-skill/blob/main/design-philosophy/SKILL.md).
+
+## Visual assets — generate or source
+
+When design-thinking identifies a need for visual assets (logos, icons, hero images, textures, backgrounds):
+
+1. **Generate** → use an image-generation model or API for synthetic/branded assets.
+2. **Source a real/archival one** → free stock or archival image search, often cheaper and more authentic than generating.
+3. Use design-thinking output (tone, domain, color world) to craft prompts / queries.
+4. Evaluate against the design philosophy, refine, integrate into the build.
+
+## LLM-assisted work — always annotate model + cost
+
+When design work involves running an LLM (generative assets, VLM analysis, layout critique, prompt generation, etc.):
+
+- **Before running:** state which model will be used and the estimated cost (e.g., "gpt-4o-mini · ~$0.005/image" or "FLUX v1 · ~$0.006 per gen").
+- **After results:** annotate the output with the model used, actual cost if different from estimate, and any key params (seed, prompt, settings). Cost goes *visible to the user* (in the message, contact sheet header, or asset caption), not buried in logs.
+- **Why:** the user is deciding whether the cost-to-quality trade-off is worth it. Unlabeled or hidden costs hide the most important lever. This rule mirrors `media-attribution-rule` for generative assets and extends it to any LLM operation in the design workflow.
+
+**Examples:**
+- "Running gpt-4o-mini layout critique on 8 designs · est. ~$0.04 total" (before).
+- Contact sheet header: "FLUX v1 · $0.48 total (6 gen × $0.08)" (after).
+- Asset caption: "hero_banner_flux-dev_seed3891.jpg" (seeds enable reproducibility).
+- Uncertainty slider result: "VLM triage on 46,978 images · gpt-4o-mini · ~$9.40" (before); "✓ Completed: 12,447 images classified · gpt-4o-mini · $7.62" (after).
+
+## Algorithm / model explainers — show the equation, annotate the terms
+
+Whenever a UI surfaces an algorithm or model to the user (an "ⓘ how this works"
+panel, a model breakdown, a methods note), **include the actual equation, typeset,
+with its key terms annotated** — don't settle for prose. A scorer described only in
+words ("ranks by how much of the picked color is present") is unfalsifiable hand-
+waving; the formula `score = Σ fracᵢ · max(0, 1 − ΔEᵢ/τ)` with each term labelled
+tells the user *exactly* what the knob does and builds trust that there's real math
+under the hood.
+
+**How to apply:**
+- Render one clean, central equation per algorithm — the "sexy" core, not every
+  detail. Use proper notation: σ for sigmoid, Σ for sums, ‖·‖ for norms,
+  superscripts, ΔE, ∇²; a monospace/serif-math block set off from the prose.
+- **Annotate every symbol** immediately below: what `e_x`, `w`, `τ`, `Q` each are,
+  in one line each. An unlabelled equation is decoration; a labelled one is a spec.
+- Keep it dependency-light — styled HTML/Unicode math is fine and works offline; only
+  reach for KaTeX/MathJax if the expressions genuinely need it.
+- State the **decision rule** alongside the score (e.g. "personal if P ≥ 0.55").
+- This composes with the model+cost annotation above: the equation says *what* it
+  computes, the model/cost line says *what ran it and for how much*.
+
+**Example (a logistic head):**
+> P(personal │ x) = σ(**w**·**e**ₓ + b),  σ(z) = 1 / (1 + e⁻ᶻ)
+> • **e**ₓ — the image's 768-d embedding · **w**, b — weights learned from your labels
+> · decision: personal if P ≥ 0.55, reference if P ≤ 0.40.
+
+## Select-all always has a deselect — no dead-end selections
+
+Any **"Select all"** affordance MUST be paired with a way to **clear the selection** —
+preferably the *same button*, label-flipped when everything is already selected
+("Select all" ⇄ "Deselect all"). A select-all with no inverse is a trap: the user
+over-selects (or hits it by reflex), then has to un-click items one by one, or reload
+the page, to get back. The cost is silent — it only bites *after* they've committed to
+the wrong set.
+
+**How to apply:**
+- **Toggle the same button** (simplest, fewest controls): when all visible items are
+  selected, the button reads "Deselect all" and clears; otherwise "Select all". One
+  control, no dead end.
+- Or a **separate Clear/Deselect** shown whenever the selection is non-empty.
+- The deselect must reach the **same scope** the select-all did (all *shown*, all
+  *filtered*, all *on this page*) — don't let "Select all" grab 500 but "Clear" only
+  drop the 50 on screen.
+- This generalizes: any reversible bulk toggle (select, expand-all, mute-all,
+  check-all) needs its inverse one tap away. Symmetry of action — see
+  restraint-rule (don't strand the user mid-task).
+
+## Limitations
+
+- This skill improves visual direction and review discipline, but it does not replace rendering the actual UI and checking it in target browsers or devices.
+- Some recommendations assume access to screenshots, browser automation, or vision review; when those are unavailable, treat the guidance as a design checklist rather than proof.
+- Brand, legal, accessibility, and localization constraints from the product owner override the taste rules here.

package/bundled-skills/deterministic-design/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: deterministic-design
+description: "Render the UI and prove it's balanced + usable: a deterministic layout audit (centroid / optical-center / pixel-oracle balance via explicit math + annotated screenshot) plus a vision-judged Nielsen usability audit by a separate fresh-eyes judge. The measurement layer taste-only design skills lack."
+risk: safe
+source: community
+source_type: community
+source_repo: connerkward/deterministic-design-skill
+date_added: "2026-06-16"
+author: Conner K Ward
+license: MIT
+tags:
+  - design
+  - layout
+  - usability
+  - audit
+  - verification
+  - vision
+tools:
+  - claude-code
+  - antigravity
+  - cursor
+  - gemini-cli
+  - codex-cli
+---
+## When to Use
+
+Use to catch AI-generated UI that "looks off", is misaligned or centered-mush, or fails usability — when you need to PROVE a layout is balanced and usable instead of trusting the model's eye. Compose it with any taste/token design skill before reporting design "done".
+
+_Source: [connerkward/deterministic-design-skill](https://github.com/connerkward/deterministic-design-skill) (MIT)._
+
+# deterministic-design
+
+Thesis: **determinism beats AI randomness.** A model can't trust its own eye on layout — so
+don't. Render the UI and *measure* it.
+
+Two sub-skills (load as needed):
+- **[design-spatial](https://github.com/connerkward/deterministic-design-skill/blob/main/design-spatial/SKILL.md)** — deterministic layout audit: explicit grid
+  + 8-pt spacing, and `layout-audit.js` computes centroid / optical-center / pixel-oracle
+  balance and draws an annotated screenshot. **Numbers, not vibes.** Plus a render-then-
+  critique vision loop.
+- **[design-ux](https://github.com/connerkward/deterministic-design-skill/blob/main/design-ux/SKILL.md)** — usability audit: scores the rendered UI against
+  Nielsen's 10 + interaction heuristics via a SEPARATE fresh-eyes judge → prioritized fix list.
+
+This **improves** existing design skills (including the default Anthropic one) by adding the
+layer they lack — it doesn't just advise on taste, it renders, measures, and judges the
+output. Composable with any design skill.
+
+In central this lives as a subdir of ckw-design; it **publishes separately** as
+`deterministic-design-skill` (its own distribution) via publish-skill. One of the two
+flagship narratives — the *determinism* one; its sibling is human-in-the-loop (lookdev).
+
+## Limitations
+
+- Layout metrics and vision-judged audits catch many spatial and usability failures, but they are not a substitute for product judgment or user testing.
+- The workflow requires a rendered UI or screenshot; it cannot validate components that have not been built or captured.
+- Automated scoring can miss brand nuance, copy tone, accessibility needs, and domain-specific user expectations.

package/bundled-skills/docs/integrations/jetski-cortex.md

@@ -1,9 +1,9 @@
 ---
 title: Jetski/Cortex + Gemini Integration Guide
-description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,569+ skills."
+description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,595+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,569+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,595+ skills
 
 This guide shows how to integrate the `antigravity-awesome-skills` repository with an agent based on **Jetski/Cortex + Gemini** (or similar frameworks) **without exceeding the model context window**.
 
@@ -23,7 +23,7 @@ Never do:
 - concatenate all `SKILL.md` content into a single system prompt;
 - re-inject the entire library for **every** request.
 
-With 1,569+ skills, this approach fills the context window before user messages are even added, causing truncation.
+With 1,595+ skills, this approach fills the context window before user messages are even added, causing truncation.
 
 ---
 

package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md

@@ -21,7 +21,7 @@ This example shows one way to integrate **antigravity-awesome-skills** with a Je
 - How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
 - How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
 
-This pattern avoids context overflow when you have 1,569+ skills installed.
+This pattern avoids context overflow when you have 1,595+ skills installed.
 
 Manifest contract references:
 

package/bundled-skills/docs/maintainers/repo-growth-seo.md

@@ -6,7 +6,7 @@ This document keeps the repository's GitHub-facing discovery copy aligned with t
 
 Preferred positioning:
 
-> Installable GitHub library of 1,569+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,595+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
 
 Key framing:
 
@@ -20,7 +20,7 @@ Key framing:
 
 Preferred description:
 
-> Installable GitHub library of 1,569+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
+> Installable GitHub library of 1,595+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
 
 Preferred homepage:
 
@@ -28,7 +28,7 @@ Preferred homepage:
 
 Preferred social preview:
 
-- use a clean preview image that says `1,569+ Agentic Skills`;
+- use a clean preview image that says `1,595+ Agentic Skills`;
 - mention Claude Code, Cursor, Codex CLI, and Gemini CLI;
 - avoid dense text and tiny logos that disappear in social cards.
 

package/bundled-skills/docs/maintainers/skills-update-guide.md

@@ -72,7 +72,7 @@ The update process refreshes:
 - Canonical skills index (`skills_index.json`)
 - Compatibility mirror (`data/skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 1,569+ skills from the skills directory
+- All 1,595+ skills from the skills directory
 
 ## When to Update
 

package/bundled-skills/docs/users/bundles.md

@@ -917,4 +917,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: March 2026 | Total Skills: 1,569+ | Total Bundles: 52_
+_Last updated: March 2026 | Total Skills: 1,595+ | Total Bundles: 52_

package/bundled-skills/docs/users/claude-code-skills.md

@@ -12,7 +12,7 @@ Install the library into Claude Code, then invoke focused skills directly in the
 
 ## Why use this repo for Claude Code
 
-- It includes 1,569+ skills instead of a narrow single-domain starter pack.
+- It includes 1,595+ skills instead of a narrow single-domain starter pack.
 - It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
 - It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
 - It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.

package/bundled-skills/docs/users/gemini-cli-skills.md

@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
 
 - It installs directly into the expected Gemini skills path.
 - It includes both core software engineering skills and deeper agent/LLM-oriented skills.
-- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,569+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,595+ files.
 - It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
 
 ## Install Gemini CLI Skills

package/bundled-skills/docs/users/getting-started.md

@@ -1,4 +1,4 @@
-# Getting Started with Antigravity Awesome Skills (V12.7.0)
+# Getting Started with Antigravity Awesome Skills (V12.8.0)
 
 **New here? This guide will help you supercharge your AI Agent in 5 minutes.**
 

package/bundled-skills/docs/users/kiro-integration.md

@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
 
 Kiro's agentic capabilities are enhanced by skills that provide:
 
-- **Domain expertise** across 1,569+ specialized areas
+- **Domain expertise** across 1,595+ specialized areas
 - **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
 - **Workflow automation** for common development tasks
 - **AWS-specific patterns** for serverless, infrastructure, and cloud architecture