opencode-skills-antigravity 1.0.13 → 1.0.15

package/bundled-skills/app-store-changelog/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: app-store-changelog
+description: Generate user-facing App Store release notes from git history since the last tag.
+risk: safe
+source: "Dimillian/Skills (MIT)"
+date_added: "2026-03-25"
+---
+
+# App Store Changelog
+
+## Overview
+Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.
+
+## When to Use
+
+- When the user asks for App Store "What's New" text or release notes from git history.
+- When you need to turn raw commits into concise, user-facing release bullets.
+
+## Workflow
+
+### 1) Collect changes
+- Run `scripts/collect_release_changes.sh` from the repo root to gather commits and touched files.
+- If needed, pass a specific tag or ref: `scripts/collect_release_changes.sh v1.2.3 HEAD`.
+- If no tags exist, the script falls back to full history.
+
+### 2) Triage for user impact
+- Scan commits and files to identify user-visible changes.
+- Group changes by theme (New, Improved, Fixed) and deduplicate overlaps.
+- Drop internal-only work (build scripts, refactors, dependency bumps, CI).
+
+### 3) Draft App Store notes
+- Write short, benefit-focused bullets for each user-facing change.
+- Use clear verbs and plain language; avoid internal jargon.
+- Prefer 5 to 10 bullets unless the user requests a different length.
+
+### 4) Validate
+- Ensure every bullet maps back to a real change in the range.
+- Check for duplicates and overly technical wording.
+- Ask for clarification if any change is ambiguous or possibly internal-only.
+
+## Commit-to-Bullet Examples
+
+The following shows how raw commits are translated into App Store bullets:
+
+| Raw commit message | App Store bullet |
+|---|---|
+| `fix(auth): resolve token refresh race condition on iOS 17` | • Fixed a login issue that could leave some users unexpectedly signed out. |
+| `feat(search): add voice input to search bar` | • Search your library hands-free with the new voice input option. |
+| `perf(timeline): lazy-load images to reduce scroll jank` | • Scrolling through your timeline is now smoother and faster. |
+
+Internal-only commits that are **dropped** (no user impact):
+- `chore: upgrade fastlane to 2.219`
+- `refactor(network): extract URLSession wrapper into module`
+- `ci: add nightly build job`
+
+## Example Output
+
+```
+What's New in Version 3.4
+
+• Search your library hands-free with the new voice input option.
+• Scrolling through your timeline is now smoother and faster.
+• Fixed a login issue that could leave some users unexpectedly signed out.
+• Added dark-mode support to the settings screen.
+• Improved load times when opening large photo albums.
+```
+
+## Output Format
+- Title (optional): "What's New" or product name + version.
+- Bullet list only; one sentence per bullet.
+- Stick to storefront limits if the user provides one.
+
+## Resources
+- `scripts/collect_release_changes.sh`: Collect commits and touched files since last tag.
+- `references/release-notes-guidelines.md`: Language, filtering, and QA rules for App Store notes.

package/bundled-skills/app-store-changelog/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "App Store Changelog"
+  short_description: "Generate App Store release notes"
+  default_prompt: "Use $app-store-changelog to draft App Store release notes from the changes since the last tag."

package/bundled-skills/app-store-changelog/references/release-notes-guidelines.md

@@ -0,0 +1,34 @@
+# App Store Release Notes Guidelines
+
+## Goals
+- Produce user-facing release notes that describe visible changes since the last tag.
+- Include all user-impacting changes; omit purely internal or refactor-only work.
+- Keep language plain, short, and benefit-focused.
+
+## Output Shape
+- Prefer 5 to 10 bullets total for most releases.
+- Group by theme if needed: New, Improved, Fixed.
+- Each bullet should be one sentence and start with a verb.
+- Avoid internal codenames, ticket IDs, or file paths.
+
+## Filtering Rules
+- Include: new features, UI changes, behavior changes, bug fixes users would notice, performance improvements with visible impact.
+- Exclude: refactors, dependency bumps, CI changes, developer tooling, internal logging, analytics changes unless they affect user privacy or behavior.
+- If a change is ambiguous, ask for clarification or describe it as a small improvement only if it is user-visible.
+
+## Language Guidance
+- Translate technical terms into user-facing descriptions.
+- Avoid versions of "API", "refactor", "nil", "crash log", or "dependency".
+- Prefer "Improved", "Added", "Fixed", "Updated" or action verbs like "Search", "Upload", "Sync".
+- Keep tense present or past: "Added", "Improved", "Fixed".
+
+## Examples
+- "Added account switching from the profile menu."
+- "Improved timeline loading speed on slow connections."
+- "Fixed media attachments not opening in full screen."
+
+## QA Checklist
+- Every bullet ties to a real change in the range.
+- No duplicate bullets that describe the same change.
+- No internal jargon or file paths.
+- Final list fits App Store text limits for the target storefront if provided.

package/bundled-skills/app-store-changelog/scripts/collect_release_changes.sh

@@ -0,0 +1,33 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+since_ref="${1:-}"
+until_ref="${2:-HEAD}"
+
+if [[ -z "${since_ref}" ]]; then
+  if git describe --tags --abbrev=0 >/dev/null 2>&1; then
+    since_ref="$(git describe --tags --abbrev=0)"
+  fi
+fi
+
+range=""
+if [[ -n "${since_ref}" ]]; then
+  range="${since_ref}..${until_ref}"
+else
+  range="${until_ref}"
+fi
+
+repo_root="$(git rev-parse --show-toplevel)"
+
+printf "Repo: %s\n" "${repo_root}"
+if [[ -n "${since_ref}" ]]; then
+  printf "Range: %s..%s\n" "${since_ref}" "${until_ref}"
+else
+  printf "Range: start..%s (no tags found)\n" "${until_ref}"
+fi
+
+printf "\n== Commits ==\n"
+git log --reverse --date=short --pretty=format:'%h|%ad|%s' ${range}
+
+printf "\n\n== Files Touched ==\n"
+git log --reverse --name-only --pretty=format:'--- %h %s' ${range} | sed '/^$/d'

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

@@ -1,9 +1,9 @@
 ---
 title: Jetski/Cortex + Gemini Integration Guide
-description: "Come usare antigravity-awesome-skills con Jetski/Cortex evitando l’overflow di contesto con 1.311+ skill."
+description: "Come usare antigravity-awesome-skills con Jetski/Cortex evitando l’overflow di contesto con 1.326+ skill."
 ---
 
-# Jetski/Cortex + Gemini: integrazione sicura con 1.311+ skill
+# Jetski/Cortex + Gemini: integrazione sicura con 1.326+ skill
 
 Questa guida mostra come integrare il repository `antigravity-awesome-skills` con un agente basato su **Jetski/Cortex + Gemini** (o framework simili) **senza superare il context window** del modello.
 
@@ -23,7 +23,7 @@ Non bisogna mai:
 - concatenare il contenuto di tutte le `SKILL.md` in un singolo system prompt;
 - reiniettare l’intera libreria per **ogni** richiesta.
 
-Con oltre 1.311 skill, questo approccio riempie il context window prima ancora di aggiungere i messaggi dell’utente, causando l’errore di truncation.
+Con oltre 1.326 skill, questo approccio riempie il context window prima ancora di aggiungere i messaggi dell’utente, causando l’errore di 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,311+ skills installed.
+This pattern avoids context overflow when you have 1,326+ 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,311+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,326+ 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,311+ 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,326+ 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,32 +28,32 @@ Preferred homepage:
 
 Preferred social preview:
 
-- use a clean preview image that says `1,311+ Agentic Skills`;
+- use a clean preview image that says `1,326+ Agentic Skills`;
 - mention Claude Code, Cursor, Codex CLI, and Gemini CLI;
 - avoid dense text and tiny logos that disappear in social cards.
 
 Preferred topics:
 
-- `agentic-skills`
-- `agent-skills`
-- `ai-agents`
-- `ai-agent-skills`
-- `awesome-list`
-- `awesome-lists`
 - `antigravity`
 - `antigravity-skills`
-- `autonomous-coding`
 - `claude-code`
 - `claude-code-skills`
+- `cursor`
+- `cursor-skills`
 - `codex-cli`
 - `codex-skills`
-- `cursor-skills`
-- `developer-tools`
 - `gemini-cli`
 - `gemini-skills`
-- `mcp`
-- `ai-workflows`
+- `kiro`
+- `ai-agents`
+- `ai-agent-skills`
+- `agent-skills`
+- `agentic-skills`
+- `developer-tools`
 - `skill-library`
+- `ai-workflows`
+- `ai-coding`
+- `mcp`
 
 ## Release notes checklist
 

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,311+ skills from the skills directory
+- All 1,326+ skills from the skills directory
 
 ## When to Update
 

package/bundled-skills/docs/sources/sources.md

@@ -80,6 +80,16 @@ The following skills were added from the curated collection at [VoltAgent/awesom
 | `fp-ts-react`     | [whatiskadudoing/fp-ts-skills](https://github.com/whatiskadudoing/fp-ts-skills) | Compatible | fp-ts with React 18/19 and Next.js                       |
 | `fp-ts-errors`    | [whatiskadudoing/fp-ts-skills](https://github.com/whatiskadudoing/fp-ts-skills) | Compatible | Type-safe error handling with Either and TaskEither      |
 
+## Skills from Dimillian/Skills
+
+The following skills were added from [Dimillian/Skills](https://github.com/Dimillian/Skills), a curated Codex skills repository focused on Apple platforms, GitHub workflows, refactoring, and performance work.
+
+| Skill / Group | Original Source | License | Notes |
+| :------------ | :-------------- | :------ | :---- |
+| `app-store-changelog`, `github`, `orchestrate-batch-refactor`, `project-skill-audit`, `react-component-performance`, `simplify-code` | [Dimillian/Skills](https://github.com/Dimillian/Skills) | MIT | Workflow, GitHub, React performance, and code simplification skills. |
+| `ios-debugger-agent`, `macos-menubar-tuist-app`, `macos-spm-app-packaging`, `swift-concurrency-expert` | [Dimillian/Skills](https://github.com/Dimillian/Skills) | MIT | Apple-platform debugging, packaging, and Swift concurrency guidance. |
+| `swiftui-liquid-glass`, `swiftui-performance-audit`, `swiftui-ui-patterns`, `swiftui-view-refactor` | [Dimillian/Skills](https://github.com/Dimillian/Skills) | MIT | SwiftUI-specific implementation, performance, and refactoring patterns. |
+
 ---
 
 ## Recently Added Skills (March 2026)

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

@@ -4,6 +4,8 @@
 
 > These packs are curated starter recommendations for humans. Generated bundle ids in `data/bundles.json` are broader catalog/workflow groupings and do not need to map 1:1 to the editorial packs below.
 
+> **Important:** bundles are not invokable mega-skills such as `@web-wizard` or `/essentials-bundle`. Use the individual skills listed in the pack, or use the activation scripts if you want only that bundle's skills active in your live Antigravity directory.
+
 ## Quick Start
 
 1. **Install the repository:**
@@ -22,6 +24,12 @@
    - Gemini CLI: `Use skill-name...`
    - Codex CLI: `Use skill-name...`
 
+If you want a bundle to behave like a focused active subset instead of a reading list, use:
+
+- macOS/Linux: `./scripts/activate-skills.sh --clear Essentials`
+- macOS/Linux: `./scripts/activate-skills.sh --clear "Web Wizard"`
+- Windows: `.\scripts\activate-skills.bat --clear Essentials`
+
 ---
 
 ## Essentials & Core
@@ -579,4 +587,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,311+ | Total Bundles: 36_
+_Last updated: March 2026 | Total Skills: 1,326+ | Total Bundles: 36_

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

@@ -4,9 +4,13 @@ If you are looking for **Claude Code skills** you can install from GitHub, this
 
 Antigravity Awesome Skills gives Claude Code users an installable library of `SKILL.md` playbooks, role-based bundles, and execution workflows. The goal is not just to collect prompts, but to make repeatable engineering tasks easier to invoke, review, and reuse.
 
+## How to use Antigravity Awesome Skills with Claude Code
+
+Install the library into Claude Code, then invoke focused skills directly in the conversation or through the plugin marketplace path. Claude Code benefits most when you keep the prompt specific about the skill, the scope, and the intended output.
+
 ## Why use this repo for Claude Code
 
-- It includes 1,311+ skills instead of a narrow single-domain starter pack.
+- It includes 1,326+ skills instead of a narrow single-domain starter pack.
 - It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
 - It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.
 - It covers both everyday engineering tasks and specialized work like security reviews, infrastructure, product planning, and documentation.

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

@@ -4,6 +4,14 @@ If you want **Codex CLI skills** that are easy to install and practical in a loc
 
 Antigravity Awesome Skills supports Codex CLI through the `.codex/skills/` path and gives you a wide set of reusable task playbooks for planning, implementation, debugging, testing, security review, and delivery.
 
+## How to use Antigravity Awesome Skills with Codex CLI
+
+Install the library into your Codex path, then invoke focused skills directly in your prompt. The most common pattern is:
+
+1. install with `npx antigravity-awesome-skills --codex`
+2. choose one workflow-oriented skill such as `@brainstorming`, `@concise-planning`, or `@test-driven-development`
+3. ask Codex to apply that skill to a concrete file, feature, test, or bugfix
+
 ## Why use this repo for Codex CLI
 
 - It supports Codex CLI with a dedicated install flag and a standard skills layout.

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

@@ -4,6 +4,10 @@ If you searched for **Cursor skills** on GitHub, this repository is built to be
 
 Antigravity Awesome Skills supports Cursor through the `.cursor/skills/` path and keeps the entry point simple: install once, then invoke the skills you need in chat.
 
+## How to use Antigravity Awesome Skills with Cursor
+
+Install the library into Cursor's skills directory, then call skills directly in chat with `@skill-name`. Cursor works especially well when you combine planning, implementation, and validation skills inside one conversation.
+
 ## Why use this repo for Cursor
 
 - It supports Cursor directly with a dedicated install flag.

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

@@ -29,6 +29,15 @@ Start from:
 - [bundles.md](bundles.md)
 - [workflows.md](workflows.md)
 
+### What is the difference between skills and MCP tools?
+
+- **Skills** are reusable `SKILL.md` playbooks that guide an AI assistant through a workflow.
+- **MCP tools** are integrations or callable capabilities that let the assistant interact with external systems.
+
+Use skills when you want better process, structure, and execution quality. Use MCP tools when you need access to APIs, services, databases, or other systems. Use both when you want reliable workflows plus external capabilities.
+
+For the longer explanation, read [skills-vs-mcp-tools.md](skills-vs-mcp-tools.md).
+
 ### Which AI tools work with these skills?
 
 - ✅ **Claude Code** (Anthropic CLI)
@@ -162,6 +171,26 @@ If Antigravity becomes unstable only when the full skills library is active, swi
 
 That guide shows how to run `scripts/activate-skills.sh` from a cloned copy of this repository so only the bundles or skill ids you need stay active in `~/.gemini/antigravity/skills`.
 
+### Gemini CLI hangs after a few turns or says "This is taking a bit longer, we're still on it". What should I do?
+
+Start with a quick isolation check:
+
+1. Start a brand-new Gemini CLI conversation.
+2. Try one prompt with no skills at all.
+3. Try the same task again with only one small skill such as `brainstorming`.
+4. Temporarily reduce your active skill set to 2-5 skills and retry.
+
+How to interpret the result:
+
+- If plain Gemini CLI hangs even without skills, the problem is likely on the Gemini CLI/runtime side rather than this repository.
+- If plain Gemini works, but hangs only when skills are present or after several turns, the likely cause is conversation/context growth.
+
+In that case:
+
+- keep a much smaller active set
+- start fresh conversations more often
+- use the overload guide: [agent-overload-recovery.md](agent-overload-recovery.md)
+
 ### How do I update skills?
 
 Navigate to your skills directory and pull the latest changes:
@@ -185,6 +214,22 @@ Use the `@` symbol followed by the skill name:
 @brainstorming help me design a todo app
 ```
 
+### Can I invoke a whole bundle like `@Essentials` or `/web-wizard`?
+
+No. Bundles are curated lists of skills, not standalone invokable mega-skills.
+
+Use them in one of these two ways:
+
+- pick individual skills from the bundle and invoke those directly
+- use the activation scripts if you want only that bundle's skills active in Antigravity
+
+Examples:
+
+```bash
+./scripts/activate-skills.sh --clear Essentials
+./scripts/activate-skills.sh --clear "Web Wizard"
+```
+
 ### Can I use multiple skills at once?
 
 **Yes!** You can invoke multiple skills:

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

@@ -4,11 +4,15 @@ If you are evaluating **Gemini CLI skills** on GitHub, this repository is a stro
 
 Antigravity Awesome Skills supports Gemini CLI through the `.gemini/skills/` path and combines general engineering playbooks with specialized skills for AI systems, integrations, infrastructure, testing, product, and growth.
 
+## How to use Antigravity Awesome Skills with Gemini CLI
+
+Install into the Gemini skills path, then ask Gemini to apply one skill at a time to a specific task. This works best when you keep the active set small and choose a clear workflow-oriented skill for the job in front of you.
+
 ## Why use this repo for Gemini CLI
 
 - 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,311+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,326+ 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 (V8.8.0)
+# Getting Started with Antigravity Awesome Skills (V8.9.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,311+ specialized areas
+- **Domain expertise** across 1,326+ 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/skills-vs-mcp-tools.md

@@ -0,0 +1,89 @@
+# Skills vs MCP Tools
+
+If you are trying to understand the difference between **Antigravity skills** and **MCP tools**, the short version is:
+
+- **Skills** are reusable `SKILL.md` playbooks that tell an AI assistant how to execute a workflow.
+- **MCP tools** are integrations or callable capabilities that let the assistant interact with external systems.
+
+The two are complementary, not competing.
+
+## What a skill does
+
+A skill gives the model better instructions for a repeated task such as:
+
+- planning a feature
+- reviewing code
+- running a security audit
+- writing a README
+- debugging a failing test suite
+
+In practice, a skill improves the assistant's decision-making, structure, and process for a task.
+
+Example:
+
+- `@brainstorming` helps the model clarify requirements before implementation.
+- `@lint-and-validate` helps the model run the right quality checks before claiming success.
+
+## What an MCP tool does
+
+An MCP tool gives the model a capability it would not otherwise have, such as:
+
+- reading from a database
+- calling GitHub APIs
+- fetching docs from a service
+- creating calendar events
+- querying an external system
+
+In practice, an MCP tool expands what the assistant can do in the world.
+
+## The easiest mental model
+
+Use this rule:
+
+- **Skills tell the assistant how to work.**
+- **MCP tools tell the assistant what systems it can touch.**
+
+If you only install tools, the assistant may have access but still behave inconsistently.
+
+If you only install skills, the assistant may know the workflow but still lack the capability to reach the external system it needs.
+
+Together, they are much stronger.
+
+## Which one should you start with?
+
+Start with **skills** if:
+
+- you want better planning, coding, debugging, testing, or review behavior immediately
+- you are working mostly in local files and terminal flows
+- you want reusable playbooks before adding more integrations
+
+Start with **MCP tools** if:
+
+- your main blocker is access to external systems
+- you need the model to call APIs, query services, or interact with hosted platforms
+- you already like the model's workflow quality, but need more reach
+
+Use **both** when:
+
+- you want reliable workflows plus external capabilities
+- you are building agent systems, internal tooling, or multi-step operational flows
+
+## How this repo fits in
+
+Antigravity Awesome Skills is primarily a **skill library**:
+
+- installable `SKILL.md` playbooks
+- bundles for role-based starting points
+- workflows for ordered execution patterns
+- tool-specific guides for Claude Code, Cursor, Codex CLI, Gemini CLI, and others
+
+Many skills in this repo also explain how to work with MCP, APIs, and other integrations, but the repository itself is centered on reusable workflow guidance rather than acting as an MCP server.
+
+## Good next reads
+
+- [FAQ](faq.md)
+- [Bundles](bundles.md)
+- [Workflows](workflows.md)
+- [AI Agent Skills](ai-agent-skills.md)
+- [Codex CLI Skills](codex-cli-skills.md)
+- [Gemini CLI Skills](gemini-cli-skills.md)

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

@@ -12,7 +12,7 @@ Great question! Here's what just happened and what to do next:
 
 When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
 
-✅ **Downloaded 1,311+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)  
+✅ **Downloaded 1,326+ 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)
 
@@ -32,7 +32,7 @@ Bundles are **recommended lists** of skills grouped by role. They help you decid
 
 **Analogy:**
 
-- You installed a toolbox with 1,311+ tools (✅ done)
+- You installed a toolbox with 1,326+ tools (✅ done)
 - Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
 - You don't install bundles—you **pick skills from them**
 
@@ -41,6 +41,7 @@ Bundles are **recommended lists** of skills grouped by role. They help you decid
 ❌ Separate installations  
 ❌ Different download commands  
 ❌ Something most users need to activate during normal install
+❌ Invokable mega-skills like `@essentials` or `/web-wizard`
 
 ### Example: The "Web Wizard" Bundle
 
@@ -53,6 +54,13 @@ When you see the [Web Wizard bundle](bundles.md#-the-web-wizard-pack), it lists:
 
 These are **recommendations** for which skills a web developer should try first. They're already installed—you just need to **use them in your prompts**.
 
+If you want only one bundle active at a time in Antigravity, use the activation scripts instead of trying to invoke the bundle name directly:
+
+```bash
+./scripts/activate-skills.sh --clear Essentials
+./scripts/activate-skills.sh --clear "Web Wizard"
+```
+
 ---
 
 ## Step 2: How to Actually Execute/Use a Skill
@@ -88,6 +96,8 @@ The exact syntax varies by tool, but it's always simple:
 Use the brainstorming skill to help me plan my app
 ```
 
+If Gemini CLI starts hanging after a few turns, try a fresh conversation and temporarily reduce the active set to just 2-5 skills to rule out context growth.
+
 #### Codex CLI
 
 ```bash
@@ -192,7 +202,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,311+ skills at once. Here's a sensible approach:
+Don't try to use all 1,326+ skills at once. Here's a sensible approach:
 
 If you want a tool-specific starting point before choosing skills, use:
 
@@ -323,7 +333,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,311+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,326+ 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,311+ skills live here
+├── 📁 skills/                          ← 1,326+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,311+ total)
+│   └── ... (1,326+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,311+ SKILLS          │
+                    │  1,326+ 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,311+ total)                │
+│   └── ... (1,326+ total)                │
 └─────────────────────────────────────────┘
 ```