opencode-skills-collection 2.0.0-beta.1 → 2.0.0-beta.3

package/README.md

@@ -18,7 +18,7 @@
 > delivered instantly, with zero network latency at startup.
 
 > ⚠️ **Previously published
-as [`opencode-skills-antigravity`](https://www.npmjs.com/package/opencode-skills-antigravity)** — that package is now
+> as [`opencode-skills-antigravity`](https://www.npmjs.com/package/opencode-skills-antigravity)** — that package is now
 > deprecated and points to this one.
 
 ---
@@ -35,7 +35,7 @@ only loaded into context on demand.
 
 ## How It Works
 
-The plugin operates in three phases:
+The plugin operates in two phases:
 
 **1. Local deployment (startup)**
 
@@ -50,7 +50,7 @@ bundled-skills/ (npm package)
         │
         └── SkillPointer pipeline
               │
-              ├─ vault-manager     → moves 800+ raw skills to the vault
+              ├─ vault-manager     → moves raw skills to the vault
               └─ pointer-generator → writes ~35 lightweight pointer files
 ```
 
@@ -69,7 +69,7 @@ After the first startup, your `~/.config/opencode/` directory looks like this:
 ```
 ~/.config/opencode/
 ├── opencode.json
-├── skills/                          ← ~35 pointer folders (active, read by OpenCode)
+├── skills/                          ← pointer folders (active, read by OpenCode)
 │   ├── backend-dev-category-pointer/
 │   │   └── SKILL.md
 │   ├── devops-category-pointer/

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

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-04-08T09:03:21.581Z",
+  "updatedAt": "2026-04-09T09:09:48.777Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -1288,7 +1288,14 @@
     "typescript-advanced-types",
     "typescript-expert",
     "typescript-pro",
+    "ui-a11y",
+    "ui-component",
+    "ui-page",
+    "ui-pattern",
+    "ui-review",
+    "ui-setup",
     "ui-skills",
+    "ui-tokens",
     "ui-ux-designer",
     "ui-ux-pro-max",
     "ui-visual-validator",
@@ -1305,6 +1312,10 @@
     "using-neon",
     "using-superpowers",
     "uv-package-manager",
+    "ux-audit",
+    "ux-copy",
+    "ux-feedback",
+    "ux-flow",
     "ux-persuasion-engineer",
     "uxui-principles",
     "variant-analysis",

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.381+ skills."
+description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1.392+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,1.381+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,1.392+ 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 over 1,1.381 skills, this approach fills the context window before user messages are even added, causing truncation.
+With over 1,1.392 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

@@ -20,7 +20,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,381+ skills installed.
+This pattern avoids context overflow when you have 1,392+ skills installed.
 
 ---
 

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,381+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,392+ 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,381+ 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,392+ 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,381+ Agentic Skills`;
+- use a clean preview image that says `1,392+ 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

@@ -69,7 +69,7 @@ For manual updates, you need:
 The update process refreshes:
 - Skills index (`skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 1,381+ skills from the skills directory
+- All 1,392+ skills from the skills directory
 
 ## When to Update
 

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

@@ -673,4 +673,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,381+ | Total Bundles: 37_
+_Last updated: March 2026 | Total Skills: 1,392+ | Total Bundles: 37_

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,381+ skills instead of a narrow single-domain starter pack.
+- It includes 1,392+ 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,381+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,392+ 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 (V9.9.0)
+# Getting Started with Antigravity Awesome Skills (V9.10.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,381+ specialized areas
+- **Domain expertise** across 1,392+ 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

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

@@ -14,7 +14,7 @@ If you came in through a **Claude Code** or **Codex** plugin instead of a full l
 
 When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
 
-✅ **Downloaded 1,381+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)  
+✅ **Downloaded 1,392+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)  
 ✅ **Made them available** to your AI assistant  
 ❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
 
@@ -34,7 +34,7 @@ Bundles are **curated groups** of skills organized by role. They help you decide
 
 **Analogy:**
 
-- You installed a toolbox with 1,381+ tools (✅ done)
+- You installed a toolbox with 1,392+ tools (✅ done)
 - Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
 - You can either **pick skills from the tray** or install that tray as a focused marketplace bundle plugin
 
@@ -212,7 +212,7 @@ Let's actually use a skill right now. Follow these steps:
 
 ## Step 5: Picking Your First Skills (Practical Advice)
 
-Don't try to use all 1,381+ skills at once. Here's a sensible approach:
+Don't try to use all 1,392+ skills at once. Here's a sensible approach:
 
 If you want a tool-specific starting point before choosing skills, use:
 
@@ -343,7 +343,7 @@ Usually no, but if your AI doesn't recognize a skill:
 
 ### "Can I load all skills into the model at once?"
 
-No. Even though you have 1,381+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,392+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
 
 The intended pattern is:
 

package/bundled-skills/docs/users/visual-guide.md

@@ -34,7 +34,7 @@ antigravity-awesome-skills/
 ├── 📄 CONTRIBUTING.md                  ← Contributor workflow
 ├── 📄 CATALOG.md                       ← Full generated catalog
 │
-├── 📁 skills/                          ← 1,381+ skills live here
+├── 📁 skills/                          ← 1,392+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,381+ total)
+│   └── ... (1,392+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,381+ SKILLS          │
+                    │  1,392+ SKILLS          │
                     └────────────┬────────────┘
                                  │
         ┌────────────────────────┼────────────────────────┐
@@ -201,7 +201,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
 │   ├── 📁 brainstorming/                 │
 │   ├── 📁 stripe-integration/            │
 │   ├── 📁 react-best-practices/          │
-│   └── ... (1,381+ total)                │
+│   └── ... (1,392+ total)                │
 └─────────────────────────────────────────┘
 ```
 

package/bundled-skills/ui-a11y/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: ui-a11y
+description: "Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe."
+category: design
+risk: safe
+source: community
+source_repo: bitjaru/styleseed
+source_type: community
+date_added: "2026-04-08"
+author: bitjaru
+tags: [ui, accessibility, wcag, audit, styleseed]
+tools: [claude, cursor, codex, gemini]
+---
+
+# UI Accessibility Audit
+
+## Overview
+
+Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill audits components and pages for accessibility issues with an emphasis on the Toss seed's mobile UI patterns. It combines WCAG 2.2 AA checks with practical code fixes for touch targets, focus states, contrast, labels, and reduced motion.
+
+## When to Use
+
+- Use when reviewing a page or component for accessibility regressions
+- Use when a StyleSeed UI looks polished but has uncertain keyboard or contrast behavior
+- Use when adding new interactive controls to a mobile-first screen
+- Use when you want a prioritized list of issues and fixable items
+
+## Audit Areas
+
+### Perceivable
+
+- text contrast
+- non-text contrast for controls and graphics
+- alt text for images
+- labels for meaningful icons
+- no information conveyed by color alone
+
+### Operable
+
+- touch targets at least 44x44px
+- keyboard reachability for all interactive controls
+- logical tab order
+- visible focus indicators
+- reduced-motion support for nonessential animation
+
+### Understandable
+
+- visible labels or `aria-label` on inputs
+- error text associated with the correct field
+- clear wording for errors and validation
+- document language set appropriately
+
+### Robust
+
+- semantic HTML where possible
+- correct use of ARIA when semantics alone are insufficient
+- no faux buttons or links without the right roles and behavior
+
+## Output
+
+Return:
+1. Issues found, grouped by severity
+2. Safe autofixes that can be applied directly
+3. Items that need manual review or product judgment
+4. A short summary of the accessibility risk level
+
+## Best Practices
+
+- Fix semantics before layering on ARIA
+- Use the design system tokens only if they still meet contrast requirements
+- Treat touch target failures as real usability defects, not polish issues
+- Prefer partial, verified fixes over speculative accessibility changes
+
+## Additional Resources
+
+- [StyleSeed repository](https://github.com/bitjaru/styleseed)
+- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ui-a11y/SKILL.md)

package/bundled-skills/ui-component/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: ui-component
+description: "Generate a new UI component that follows StyleSeed Toss conventions for structure, tokens, accessibility, and component ergonomics."
+category: design
+risk: safe
+source: community
+source_repo: bitjaru/styleseed
+source_type: community
+date_added: "2026-04-08"
+author: bitjaru
+tags: [ui, components, design-system, frontend, styleseed]
+tools: [claude, cursor, codex, gemini]
+---
+
+# UI Component
+
+## Overview
+
+Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill generates components that respect the Toss seed's design language instead of improvising ad hoc markup and styling. It emphasizes semantic tokens, predictable typing, reusable variants, and mobile-friendly accessibility defaults.
+
+## When to Use
+
+- Use when you need a new UI primitive or composed component inside a StyleSeed-based project
+- Use when you want a component to match the existing Toss seed conventions
+- Use when a component should be reusable, typed, and design-token driven
+- Use when the AI might otherwise invent spacing, colors, or interaction patterns
+
+## How It Works
+
+### Step 1: Read the Local Design Context
+
+Before generating code, inspect the seed's source of truth:
+- `CLAUDE.md` for conventions
+- `css/theme.css` for semantic tokens
+- at least one representative component from `components/ui/`
+
+If the user already has a better local example, follow the local codebase over a generic template.
+
+### Step 2: Choose the Correct Home
+
+Place the output where it belongs:
+- `src/components/ui/` for primitives and low-level building blocks
+- `src/components/patterns/` for composed sections or multi-part patterns
+
+Do not create a new primitive if an existing one can be extended safely.
+
+### Step 3: Follow the Structural Rules
+
+Use these defaults unless the host project strongly disagrees:
+- function declaration instead of a `const` component
+- `React.ComponentProps<>` or equivalent native prop typing
+- `className` passthrough support
+- `cn()` or the project's standard class merger
+- `data-slot` for component identification
+- CVA or equivalent only when variants are genuinely needed
+
+### Step 4: Use Semantic Tokens Only
+
+Do not hardcode visual values if the design system has a token for them.
+
+Preferred examples:
+- `bg-card`
+- `text-foreground`
+- `text-muted-foreground`
+- `border-border`
+- `shadow-[var(--shadow-card)]`
+
+### Step 5: Preserve StyleSeed Typography and Spacing
+
+- Use the scale already defined by the seed
+- Prefer multiples of 6px
+- Use logical spacing utilities where supported
+- Keep display and heading text tight, body text readable, captions restrained
+
+### Step 6: Bake in Accessibility
+
+- Touch targets should be at least 44x44px for interactive elements
+- Keyboard focus must be visible
+- Pass through `aria-*` attributes where appropriate
+- Respect reduced-motion preferences for nonessential motion
+
+## Output
+
+Provide:
+1. The generated component
+2. The target path
+3. Any required imports or dependencies
+4. Notes on variants, tokens, or follow-up integration work
+
+## Best Practices
+
+- Compose from existing primitives before inventing new ones
+- Keep the component API small and predictable
+- Prefer semantic layout classes over arbitrary values
+- Export named components unless the host project uses another standard consistently
+
+## Additional Resources
+
+- [StyleSeed repository](https://github.com/bitjaru/styleseed)
+- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ui-component/SKILL.md)

package/bundled-skills/ui-page/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: ui-page
+description: "Scaffold a new mobile-first page using StyleSeed Toss layout patterns, section rhythm, and existing shell components."
+category: design
+risk: safe
+source: community
+source_repo: bitjaru/styleseed
+source_type: community
+date_added: "2026-04-08"
+author: bitjaru
+tags: [ui, page-design, mobile, layout, styleseed]
+tools: [claude, cursor, codex, gemini]
+---
+
+# UI Page
+
+## Overview
+
+Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill scaffolds a complete page or screen using the Toss seed's mobile-first composition rules. It keeps page structure consistent by building on the existing shell, top bar, bottom navigation, and card rhythm instead of producing disconnected sections.
+
+## When to Use
+
+- Use when you need a new page in a Toss-seed app
+- Use when you want a consistent page shell, spacing, and navigation structure
+- Use when you are adding a new product flow and need a solid starting layout
+- Use when you want to stay mobile-first even if the project later expands to larger breakpoints
+
+## How It Works
+
+### Step 1: Inspect the Existing Shell
+
+Read the current page scaffolding patterns first, especially:
+- page shell
+- top bar
+- bottom navigation
+- representative pages using the same route family
+
+### Step 2: Define the Page Purpose
+
+Clarify:
+- the page name
+- the primary user question the screen answers
+- the top one or two actions the user should take
+
+Every screen should have one dominant purpose.
+
+### Step 3: Use the Information Pyramid
+
+Lay out the page from highest importance to lowest:
+1. Hero or top summary
+2. KPI or key actions
+3. detail cards or supporting modules
+4. lists, history, or secondary content
+
+Avoid repeating the same section type mechanically from top to bottom.
+
+### Step 4: Apply the Toss Layout Rules
+
+Default layout choices:
+- mobile viewport width around `max-w-[430px]`
+- page background on `bg-background`
+- horizontal padding around `px-6`
+- section rhythm with `space-y-6`
+- generous bottom padding if a bottom nav is present
+- cards using semantic surface tokens, rounded corners, and light shadows
+
+### Step 5: Compose Instead of Rebuilding
+
+Use existing `ui/` and `patterns/` components wherever possible. New pages should primarily orchestrate existing building blocks, not recreate them.
+
+### Step 6: Account for Real Device Constraints
+
+- handle safe-area insets
+- avoid horizontal overflow
+- keep interactive clusters thumb-friendly
+- ensure long content scrolls cleanly without clipping the bottom navigation
+
+## Output
+
+Return:
+1. The page scaffold
+2. The chosen section structure
+3. Reused components and any newly required components
+4. Empty, loading, and error states that the page will need next
+
+## Best Practices
+
+- Keep the first version structurally correct before adding decoration
+- Use one strong hero instead of multiple competing highlights
+- Preserve navigation consistency across sibling screens
+- Prefer reusable section components when the page will likely repeat
+
+## Additional Resources
+
+- [StyleSeed repository](https://github.com/bitjaru/styleseed)
+- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ui-page/SKILL.md)

package/bundled-skills/ui-pattern/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: ui-pattern
+description: "Generate reusable UI patterns such as card sections, grids, lists, forms, and chart wrappers using StyleSeed Toss primitives."
+category: design
+risk: safe
+source: community
+source_repo: bitjaru/styleseed
+source_type: community
+date_added: "2026-04-08"
+author: bitjaru
+tags: [ui, patterns, design-system, reuse, styleseed]
+tools: [claude, cursor, codex, gemini]
+---
+
+# UI Pattern
+
+## Overview
+
+Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill builds reusable composed patterns from the seed's primitives. It is intended for sections like card lists, grids, form blocks, ranking lists, and chart wrappers that appear across multiple pages and need to look deliberate rather than ad hoc.
+
+## When to Use
+
+- Use when you need a reusable layout pattern rather than a one-off page section
+- Use when a page repeats the same arrangement of cards, rows, filters, or data blocks
+- Use when you want to build from existing StyleSeed primitives instead of copying markup
+- Use when you want a pattern component with props for dynamic content
+
+## How It Works
+
+### Step 1: Identify the Pattern Type
+
+Common pattern families include:
+- card section
+- two-column grid
+- horizontal scroller
+- list section
+- form section
+- stat grid
+- data table
+- detail card
+- chart card
+- filter bar
+- action sheet
+
+### Step 2: Read the Available Building Blocks
+
+Inspect both:
+- `components/ui/` for primitives
+- `components/patterns/` for neighboring patterns that can be extended
+
+The goal is composition, not duplication.
+
+### Step 3: Apply StyleSeed Layout Rules
+
+Keep the Toss seed defaults intact:
+- card surfaces on semantic tokens
+- rounded corners from the system scale
+- shadow tokens instead of improvised shadow values
+- consistent internal padding
+- section wrappers that align with the page margin system
+
+### Step 4: Make the Pattern Dynamic
+
+Expose data through props instead of hardcoding content. If a pattern has multiple variants, keep the API explicit and small.
+
+### Step 5: Keep the Pattern Reusable Across Pages
+
+Avoid page-specific assumptions unless the user explicitly wants a one-off section. If the markup only works on one route, it probably belongs in a page component, not a shared pattern.
+
+## Output
+
+Provide:
+1. The generated pattern component
+2. The target location
+3. Expected props and usage example
+4. Notes on which existing primitives were reused
+
+## Best Practices
+
+- Start from the smallest existing building block that solves the problem
+- Keep container, section, and item responsibilities separate
+- Use tokens and spacing rules consistently
+- Prefer extending a pattern over adding a near-duplicate sibling
+
+## Additional Resources
+
+- [StyleSeed repository](https://github.com/bitjaru/styleseed)
+- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ui-pattern/SKILL.md)