chore: cut v5.0.0 workflows release and maintenance updates

Prepare release 5.0.0 by documenting the new Workflows foundation, bumping package metadata, refreshing release notes, and extending MAINTENANCE guidance for workflows consistency and issue-closing protocol. Co-authored-by: Cursor <cursoragent@cursor.com>
feat: add antigravity workflows playbooks and orchestration skill
2026-02-10 10:43:41 +01:00 · 2026-02-10 10:36:34 +01:00 · 2026-02-10 07:00:43 +00:00 · 2026-02-09 07:01:18 +00:00 · 2026-02-08 11:09:34 +01:00 · 2026-02-08 10:02:49 +00:00
21 changed files with 1068 additions and 340 deletions
--- a/.github/MAINTENANCE.md
+++ b/.github/MAINTENANCE.md
@@ -1,4 +1,4 @@
-# 🛠️ Repository Maintenance Guide (V4)
+# 🛠️ Repository Maintenance Guide (V5)

 > **"If it's not documented, it's broken."**

@@ -145,6 +145,24 @@ Locations to check:
 - **Antigravity Badge**: Must point to `https://github.com/sickn33/antigravity-awesome-skills`, NOT `anthropics/antigravity`.
 - **License**: Ensure the link points to `LICENSE` file.

+### F. Workflows Consistency (NEW in V5)
+
+If you touch any Workflows-related artifact, keep all workflow surfaces in sync:
+
+1. `docs/WORKFLOWS.md` (human-readable playbooks)
+2. `data/workflows.json` (machine-readable schema)
+3. `skills/antigravity-workflows/SKILL.md` (orchestration entrypoint)
+
+Rules:
+
+- Every workflow id referenced in docs must exist in `data/workflows.json`.
+- If you add/remove a workflow step category, update prompt examples accordingly.
+- If a workflow references optional skills not yet merged (example: `go-playwright`), mark them explicitly as **optional** in docs.
+- If workflow onboarding text is changed, update the docs trinity:
+  - `README.md`
+  - `docs/GETTING_STARTED.md`
+  - `docs/FAQ.md`
+
 ---

 ## 3. 🛡️ Governance & Quality Bar
@@ -198,6 +216,10 @@ When cutting a new version (e.g., V4):
      You cannot republish the same version; always bump `package.json` before publishing.
    - **Option B (CI):** On GitHub, create a **Release** (tag e.g. `v4.6.1`). The workflow [Publish to npm](.github/workflows/publish-npm.yml) runs on **Release published** and runs `npm publish` if the repo secret `NPM_TOKEN` is set (npm → Access Tokens → Granular token with Publish, then add as repo secret `NPM_TOKEN`).

+6.  **Close linked issue(s)**:
+    - If the release completes an issue scope (feature/fix), close it with `gh issue close <id> --comment "..."`
+    - Include release tag reference in the closing note when applicable.
+
 ### 📋 Changelog Entry Template

 Each new release section in `CHANGELOG.md` should follow [Keep a Changelog](https://keepachangelog.com/) and this structure:
--- a/CATALOG.md
+++ b/CATALOG.md
@@ -1,8 +1,8 @@
 # Skill Catalog

-Generated at: 2026-02-06T07:49:30.257Z
+Generated at: 2026-02-08T00:00:00.000Z

-Total skills: 713
+Total skills: 714

 ## architecture (63)

@@ -338,7 +338,7 @@ TRIGGER: "shopify", "shopify app", "checkout extension",... | shopify | shopify,
 | `claude-scientific-skills` | Scientific research and analysis skills | claude, scientific, skills | claude, scientific, skills, research, analysis |
 | `claude-speed-reader` | -Speed read Claude's responses at 600+ WPM using RSVP with Spritz-style ORP highlighting | claude, speed, reader | claude, speed, reader, read, responses, 600, wpm, rsvp, spritz, style, orp, highlighting |
 | `claude-win11-speckit-update-skill` | Windows 11 system management | claude, win11, speckit, update, skill | claude, win11, speckit, update, skill, windows, 11 |
-| `clean-code` | Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments | clean, code | clean, code, pragmatic, coding, standards, concise, direct, no, engineering, unnecessary, comments |
+| `clean-code` | Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and... | clean, code | clean, code, applies, principles, robert, martin, skill, writing, reviewing, refactoring, high, quality |
 | `code-documentation-code-explain` | You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform dif... | code, documentation, explain | code, documentation, explain, education, specializing, explaining, complex, through, clear, narratives, visual, diagrams |
 | `code-refactoring-context-restore` | Use when working with code refactoring context restore | code, refactoring, restore | code, refactoring, restore, context, working |
 | `code-refactoring-tech-debt` | You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncov... | code, refactoring, tech, debt | code, refactoring, tech, debt, technical, specializing, identifying, quantifying, prioritizing, software, analyze, codebase |
@@ -531,7 +531,7 @@ TRIGGER: "shopify", "shopify app", "checkout extension",... | shopify | shopify,
 | `wireshark-analysis` | This skill should be used when the user asks to "analyze network traffic with Wireshark", "capture packets for troubleshooting", "filter PCAP files", "follow... | wireshark | wireshark, network, traffic, analysis, skill, should, used, user, asks, analyze, capture, packets |
 | `workflow-automation` | Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost... |  | automation, infrastructure, makes, ai, agents, reliable, without, durable, execution, network, hiccup, during |

-## security (113)
+## security (114)

 | Skill | Description | Tags | Triggers |
 | --- | --- | --- | --- |
@@ -539,6 +539,7 @@ TRIGGER: "shopify", "shopify app", "checkout extension",... | shopify | shopify,
 | `active-directory-attacks` | This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration"... | active, directory, attacks | active, directory, attacks, skill, should, used, user, asks, attack, exploit, ad, kerberoasting |
 | `agent-memory-systems` | Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-te... | agent, memory | agent, memory, cornerstone, intelligent, agents, without, every, interaction, starts, zero, skill, covers |
 | `ai-product` | Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production.  This skill covers LLM integra... | ai, product | ai, product, every, powered, question, whether, ll, right, ship, demo, falls, apart |
+| `antigravity-workflows` | Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA. | antigravity | antigravity, orchestrate, multiple, skills, through, guided, saas, mvp, delivery, security, audits, ai |
 | `api-fuzzing-bug-bounty` | This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetrat... | api, fuzzing, bug, bounty | api, fuzzing, bug, bounty, skill, should, used, user, asks, test, security, fuzz |
 | `api-security-best-practices` | Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities | api, security, best, practices | api, security, best, practices, secure, including, authentication, authorization, input, validation, rate, limiting |
 | `attack-tree-construction` | Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to s... | attack, tree, construction | attack, tree, construction, trees, visualize, threat, paths, mapping, scenarios, identifying, defense, gaps |
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,26 +7,97 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

 ---

-## [4.10.0] - 2026-02-06 - "Composio Automation + .NET Backend"
+## [5.0.0] - 2026-02-10 - "Antigravity Workflows Foundation"

-> Merged two community PRs adding broad automation coverage and a dedicated .NET backend skill.
+> Workflows are now first-class: users can run guided, multi-skill playbooks instead of manually composing skills one by one.

 ### Added

- **79 new skills total**:
- **78 Composio/Rube automation skills** across CRM, productivity, comms, analytics, support, and DevOps tools (PR #64).
- **1 new `.NET backend` skill** for ASP.NET Core enterprise APIs (PR #65).
- **Registry** now tracks **713 skills** (from 634).
+- **New orchestration skill**: `antigravity-workflows`
+  - `skills/antigravity-workflows/SKILL.md`
+  - `skills/antigravity-workflows/resources/implementation-playbook.md`
+- **New workflow documentation**: `docs/WORKFLOWS.md`
+  - Introduces the Workflows model and differentiates it from Bundles.
+  - Provides execution playbooks with prerequisites, ordered steps, and prompt examples.
+- **New machine-readable workflow registry**: `data/workflows.json`
+  - `ship-saas-mvp`
+  - `security-audit-web-app`
+  - `build-ai-agent-system`
+  - `qa-browser-automation`

 ### Changed

- Synced generated registry artifacts after merges:
- `README.md`
+- **README / Onboarding docs** updated to include Workflows discovery and usage:
+  - `README.md` (TOC + "Antigravity Workflows" section)
+  - `docs/GETTING_STARTED.md` (Bundles vs Workflows guidance)
+  - `docs/FAQ.md` (new Q&A: Bundles vs Workflows)
+- **Go browser automation alignment**:
+  - Workflow playbooks now include optional `@go-playwright` hooks for Go-based QA/E2E flows.
+- **Registry sync** after workflow skill addition:
+  - `CATALOG.md`
+  - `skills_index.json`
+  - `data/catalog.json`
+  - `data/bundles.json`
+
+### Contributors
+
+- [@sickn33](https://github.com/sickn33) - Workflows architecture, docs, and release integration
+
+---
+
+## [4.11.0] - 2026-02-08 - "Clean Code & Registry Stability"
+
+> Quality improvements: Clean Code principles and deterministic builds.
+
+### Changed
+
+- **`clean-code` skill** - Complete rewrite based on Robert C. Martin's "Clean Code":
+  - Systematic coverage: Meaningful names, functions, comments, formatting, objects, error handling, unit tests, and classes
+  - Added F.I.R.S.T. test principles and Law of Demeter guidance
+  - Fixed invalid heading format (`## ## When to Use` → `## When to Use`) that blocked validation
+  - Added implementation checklist and code smell detection
+- **Registry Stabilization** - Fixed `scripts/build-catalog.js` for deterministic CI builds:
+  - Uses `SOURCE_DATE_EPOCH` environment variable for reproducible timestamps
+  - Replaced `localeCompare` with explicit comparator for consistent sorting across environments
+  - Prevents CI validation failures caused by timestamp drift
+
+### Contributors
+
+- [@jackjin1997](https://github.com/jackjin1997) - Clean Code skill update and registry fixes (PR #69, forged at [ClawForge](https://github.com/jackjin1997/ClawForge))
+
+---
+
+## [4.10.0] - 2026-02-06 - "Composio Automation + .NET Backend"
+
+> A major expansion focused on practical app automation and stronger backend engineering coverage.
+
+### Added
+
+- **79 new skills total**.
+- **78 Composio/Rube automation skills** (PR #64), with operational playbooks for:
+- CRM and sales stacks (`HubSpot`, `Pipedrive`, `Salesforce`, `Zoho CRM`, `Close`).
+- Collaboration and project tools (`Notion`, `ClickUp`, `Asana`, `Jira`, `Confluence`, `Trello`, `Monday`).
+- Messaging and support channels (`Slack`, `Discord`, `Teams`, `Intercom`, `Freshdesk`, `Zendesk`).
+- Marketing and analytics systems (`Google Analytics`, `Mixpanel`, `PostHog`, `Segment`, `Mailchimp`, `Klaviyo`).
+- Infra/dev tooling (`GitHub`, `GitLab`, `CircleCI`, `Datadog`, `PagerDuty`, `Vercel`, `Render`).
+- **1 new `dotnet-backend` skill** (PR #65) with:
+- ASP.NET Core 8+ API patterns (Minimal APIs + controller-based).
+- EF Core usage guidance, JWT auth examples, and background worker templates.
+- Explicit trigger guidance and documented limitations.
+- **Registry size increased to 713 skills** (from 634).
+
+### Changed
+
+- Regenerated and synced discovery artifacts after merging both PRs:
+- `README.md` (counts + contributor updates)
 - `skills_index.json`
 - `CATALOG.md`
 - `data/catalog.json`
 - `data/bundles.json`
 - `data/aliases.json`
+- Release metadata updated for `v4.10.0`:
+- `package.json` / `package-lock.json` version bump
+- GitHub Release object published with release notes

 ### Contributors

--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
-# 🌌 Antigravity Awesome Skills: 713+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
+# 🌌 Antigravity Awesome Skills: 714+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More

-> **The Ultimate Collection of 713+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode, AdaL**
+> **The Ultimate Collection of 714+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode, AdaL**

 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![Claude Code](https://img.shields.io/badge/Claude%20Code-Anthropic-purple)](https://claude.ai)
@@ -12,8 +12,11 @@
 [![Antigravity](https://img.shields.io/badge/Antigravity-DeepMind-red)](https://github.com/sickn33/antigravity-awesome-skills)
 [![AdaL CLI](https://img.shields.io/badge/AdaL%20CLI-SylphAI-pink)](https://sylph.ai/)
 [![ASK Supported](https://img.shields.io/badge/ASK-Supported-blue)](https://github.com/yeasy/ask)
+[![Buy Me a Book](https://img.shields.io/badge/Buy%20me%20a-book-d13610?logo=buymeacoffee&logoColor=white)](https://buymeacoffee.com/sickn33)

-**Antigravity Awesome Skills** is a curated, battle-tested library of **713 high-performance agentic skills** designed to work seamlessly across all major AI coding assistants:
+If this project helps you, you can [support it here](https://buymeacoffee.com/sickn33) or simply ⭐ the repo.
+
+**Antigravity Awesome Skills** is a curated, battle-tested library of **714 high-performance agentic skills** designed to work seamlessly across all major AI coding assistants:

 - 🟣 **Claude Code** (Anthropic CLI)
 - 🔵 **Gemini CLI** (Google DeepMind)
@@ -30,47 +33,59 @@ This repository provides essential skills to transform your AI assistant into a

 - [🚀 New Here? Start Here!](#new-here-start-here)
 - [🔌 Compatibility & Invocation](#compatibility--invocation)
- [📦 Features & Categories](#features--categories)
- [🎁 Curated Collections (Bundles)](#curated-collections)
- [📚 Browse 713+ Skills](#browse-713-skills)
 - [🛠️ Installation](#installation)
+- [🧯 Troubleshooting](#troubleshooting)
+- [🎁 Curated Collections (Bundles)](#curated-collections)
+- [🧭 Antigravity Workflows](#antigravity-workflows)
+- [📦 Features & Categories](#features--categories)
+- [📚 Browse 714+ Skills](#browse-714-skills)
 - [🤝 How to Contribute](#how-to-contribute)
+- [🤝 Community](#community)
+- [☕ Support the Project](#support-the-project)
 - [👥 Contributors & Credits](#credits--sources)
- [⚖️ License](#license)
 - [👥 Repo Contributors](#repo-contributors)
+- [⚖️ License](#license)
 - [🌟 Star History](#star-history)
+- [🏷️ GitHub Topics](#github-topics)

 ---

 ## New Here? Start Here!

-**Welcome to the V4.0.0 Enterprise Edition.** This isn't just a list of scripts; it's a complete operating system for your AI Agent.
+**Welcome to the V5.0.0 Workflows Edition.** This isn't just a list of scripts; it's a complete operating system for your AI Agent.

 ### 1. 🐣 Context: What is this?

-**Antigravity Awesome Skills** (Release 4.0.0) is a massive upgrade to your AI's capabilities.
+**Antigravity Awesome Skills** (Release 5.0.0) is a massive upgrade to your AI's capabilities.

 AI Agents (like Claude Code, Cursor, or Gemini) are smart, but they lack **specific tools**. They don't know your company's "Deployment Protocol" or the specific syntax for "AWS CloudFormation".
 **Skills** are small markdown files that teach them how to do these specific tasks perfectly, every time.

-### 2. ⚡️ Quick Start (The "Bundle" Way)
+### 2. ⚡️ Quick Start (1 minute)

-Install once (clone or npx); then use our **Starter Packs** in [docs/BUNDLES.md](docs/BUNDLES.md) to see which skills fit your role. You get the full repo; Starter Packs are curated lists, not a separate install.
+Install once; then use Starter Packs in [docs/BUNDLES.md](docs/BUNDLES.md) to focus on your role.

-1.  **Install** (pick one):
+1. **Install**:

-    ```bash
-    # Easiest: npx installer (clones to ~/.agent/skills by default)
-    npx antigravity-awesome-skills
+   ```bash
+   # Default path: ~/.agent/skills
+   npx antigravity-awesome-skills
+   ```

-    # Or clone manually
-    git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills
-    ```
+2. **Verify**:

-2.  **Pick your persona** (See [docs/BUNDLES.md](docs/BUNDLES.md)):
-    - **Web Dev?** use the `Web Wizard` pack.
-    - **Hacker?** use the `Security Engineer` pack.
-    - **Just curious?** start with `Essentials`.
+   ```bash
+   test -d ~/.agent/skills && echo "Skills installed in ~/.agent/skills"
+   ```
+
+3. **Run your first skill**:
+
+   > "Use **@brainstorming** to plan a SaaS MVP."
+
+4. **Pick a bundle**:
+   - **Web Dev?** start with `Web Wizard`.
+   - **Security?** start with `Security Engineer`.
+   - **General use?** start with `Essentials`.

 ### 3. 🧠 How to use

@@ -102,42 +117,11 @@ These skills follow the universal **SKILL.md** format and work with any AI codin
 > **Universal Path**: We recommend cloning to `.agent/skills/`. Most modern tools (Antigravity, recent CLIs) look here by default.

 > [!WARNING]
-> **Windows Users**: This repository uses **symlinks** for official skills.
-> The **npx** installer sets `core.symlinks=true` automatically. For **git clone**, enable Developer Mode or run Git as Administrator:
-> `git clone -c core.symlinks=true https://github.com/...`
+> **Windows Users**: this repository uses **symlinks** for official skills.
+> See [Troubleshooting](#troubleshooting) for the exact fix.

 ---

-Whether you are using **Gemini CLI**, **Claude Code**, **Codex CLI**, **Cursor**, **GitHub Copilot**, **Antigravity**, **OpenCode**, or **AdaL**, these skills are designed to drop right in and supercharge your AI agent.
-
-This repository aggregates the best capabilities from across the open-source community, transforming your AI assistant into a full-stack digital agency capable of Engineering, Design, Security, Marketing, and Autonomous Operations.
-
-## Features & Categories
-
-The repository is organized into specialized domains to transform your AI into an expert across the entire software development lifecycle:
-
-| Category            | Focus                                              | Example skills                                                                  |
-| :------------------ | :------------------------------------------------- | :------------------------------------------------------------------------------ |
-| Architecture (52)   | System design, ADRs, C4, and scalable patterns     | `architecture`, `c4-context`, `senior-architect`                                |
-| Business (35)       | Growth, pricing, CRO, SEO, and go-to-market        | `copywriting`, `pricing-strategy`, `seo-audit`                                  |
-| Data & AI (81)      | LLM apps, RAG, agents, observability, analytics    | `rag-engineer`, `prompt-engineer`, `langgraph`                                  |
-| Development (72)    | Language mastery, framework patterns, code quality | `typescript-expert`, `python-patterns`, `react-patterns`                        |
-| General (95)        | Planning, docs, product ops, writing, guidelines   | `brainstorming`, `doc-coauthoring`, `writing-plans`                             |
-| Infrastructure (72) | DevOps, cloud, serverless, deployment, CI/CD       | `docker-expert`, `aws-serverless`, `vercel-deployment`                          |
-| Security (107)      | AppSec, pentesting, vuln analysis, compliance      | `api-security-best-practices`, `sql-injection-testing`, `vulnerability-scanner` |
-| Testing (21)        | TDD, test design, fixes, QA workflows              | `test-driven-development`, `testing-patterns`, `test-fixing`                    |
-| Workflow (17)       | Automation, orchestration, jobs, agents            | `workflow-automation`, `inngest`, `trigger-dev`                                 |
-
-## Curated Collections
-
-[Check out our Starter Packs in docs/BUNDLES.md](docs/BUNDLES.md) to find the perfect toolkit for your role.
-
-## Browse 713+ Skills
-
-We have moved the full skill registry to a dedicated catalog to keep this README clean.
-
-👉 **[View the Complete Skill Catalog (CATALOG.md)](CATALOG.md)**
-
 ## Installation

 To use these skills with **Claude Code**, **Gemini CLI**, **Codex CLI**, **Cursor**, **Antigravity**, **OpenCode**, or **AdaL**:
@@ -169,8 +153,6 @@ npx antigravity-awesome-skills --path ./my-skills

 Run `npx antigravity-awesome-skills --help` for all options. If the directory already exists, the installer runs `git pull` to update.

-> **If you see a 404 error:** the package may not be published to npm yet. Use: `npx github:sickn33/antigravity-awesome-skills`
-
 ### Option B: git clone

 ```bash
@@ -195,6 +177,111 @@ git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skill

 ---

+## Troubleshooting
+
+### `npx antigravity-awesome-skills` returns 404
+
+Use the GitHub package fallback:
+
+```bash
+npx github:sickn33/antigravity-awesome-skills
+```
+
+### Windows clone issues (symlinks)
+
+This repository uses symlinks for official skills. Enable Developer Mode or run Git as Administrator, then clone with:
+
+```bash
+git clone -c core.symlinks=true https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills
+```
+
+### Skills installed but not detected by your tool
+
+Install to the tool-specific path (for example `.claude/skills`, `.gemini/skills`, `.codex/skills`, `.cursor/skills`) or use the installer flags (`--claude`, `--gemini`, `--codex`, `--cursor`, `--path`).
+
+### Update an existing installation
+
+```bash
+git -C ~/.agent/skills pull
+```
+
+### Reinstall from scratch
+
+```bash
+rm -rf ~/.agent/skills
+npx antigravity-awesome-skills
+```
+
+---
+
+## Curated Collections
+
+**Bundles** are curated groups of skills for a specific role or goal (for example: `Web Wizard`, `Security Engineer`, `OSS Maintainer`).
+
+They help you avoid picking from 700+ skills one by one.
+
+What bundles are:
+- Recommended starting sets for common workflows.
+- A shortcut for onboarding and faster execution.
+
+What bundles are not:
+- Not a separate install.
+- Not a locked preset.
+
+How to use bundles:
+1. Install the repository once.
+2. Pick one bundle in [docs/BUNDLES.md](docs/BUNDLES.md).
+3. Start with 3-5 skills from that bundle in your prompt.
+4. Add more only when needed.
+
+Examples:
+- Building a SaaS MVP: `Essentials` + `Full-Stack Developer` + `QA & Testing`.
+- Hardening production: `Security Developer` + `DevOps & Cloud` + `Observability & Monitoring`.
+- Shipping OSS changes: `Essentials` + `OSS Maintainer`.
+
+## Antigravity Workflows
+
+Bundles help you choose skills. Workflows help you execute them in order.
+
+- Use bundles when you need curated recommendations by role.
+- Use workflows when you need step-by-step execution for a concrete goal.
+
+Start here:
+- [docs/WORKFLOWS.md](docs/WORKFLOWS.md): human-readable playbooks.
+- [data/workflows.json](data/workflows.json): machine-readable workflow metadata.
+
+Initial workflows include:
+- Ship a SaaS MVP
+- Security Audit for a Web App
+- Build an AI Agent System
+- QA and Browser Automation (with optional `@go-playwright` support for Go stacks)
+
+## Features & Categories
+
+The repository is organized into specialized domains to transform your AI into an expert across the entire software development lifecycle:
+
+| Category       | Focus                                              | Example skills                                                                  |
+| :------------- | :------------------------------------------------- | :------------------------------------------------------------------------------ |
+| Architecture   | System design, ADRs, C4, and scalable patterns     | `architecture`, `c4-context`, `senior-architect`                                |
+| Business       | Growth, pricing, CRO, SEO, and go-to-market        | `copywriting`, `pricing-strategy`, `seo-audit`                                  |
+| Data & AI      | LLM apps, RAG, agents, observability, analytics    | `rag-engineer`, `prompt-engineer`, `langgraph`                                  |
+| Development    | Language mastery, framework patterns, code quality | `typescript-expert`, `python-patterns`, `react-patterns`                        |
+| General        | Planning, docs, product ops, writing, guidelines   | `brainstorming`, `doc-coauthoring`, `writing-plans`                             |
+| Infrastructure | DevOps, cloud, serverless, deployment, CI/CD       | `docker-expert`, `aws-serverless`, `vercel-deployment`                          |
+| Security       | AppSec, pentesting, vuln analysis, compliance      | `api-security-best-practices`, `sql-injection-testing`, `vulnerability-scanner` |
+| Testing        | TDD, test design, fixes, QA workflows              | `test-driven-development`, `testing-patterns`, `test-fixing`                    |
+| Workflow       | Automation, orchestration, jobs, agents            | `workflow-automation`, `inngest`, `trigger-dev`                                 |
+
+Counts change as new skills are added. For the current full registry, see [CATALOG.md](CATALOG.md).
+
+## Browse 714+ Skills
+
+We have moved the full skill registry to a dedicated catalog to keep this README clean.
+
+👉 **[View the Complete Skill Catalog (CATALOG.md)](CATALOG.md)**
+
+---
+
 ## How to Contribute

 We welcome contributions from the community! To add a new skill:
@@ -209,6 +296,33 @@ Please ensure your skill follows the Antigravity/Claude Code best practices.

 ---

+## Community
+
+- [Community Guidelines](docs/COMMUNITY_GUIDELINES.md)
+- [Security Policy](docs/SECURITY_GUARDRAILS.md)
+
+---
+
+## Support the Project
+
+Support is optional. This project stays free and open-source for everyone.
+
+If this repository saves you time or helps you ship faster, you can support ongoing maintenance:
+- [☕ Buy me a book on Buy Me a Coffee](https://buymeacoffee.com/sickn33)
+
+Where support goes:
+- Skill curation, testing, and quality validation.
+- Documentation updates, examples, and onboarding improvements.
+- Faster triage and review of community issues and PRs.
+
+Prefer non-financial support:
+- Star the repository.
+- Open clear, reproducible issues.
+- Submit PRs (skills, docs, fixes).
+- Share the project with other builders.
+
+---
+
 ## Credits & Sources

 We stand on the shoulders of giants.
@@ -262,31 +376,6 @@ This collection would not be possible without the incredible work of the Claude

 ---

-## License
-
-MIT License. See [LICENSE](LICENSE) for details.
-
-## Community
-
- [Community Guidelines](docs/COMMUNITY_GUIDELINES.md)
- [Security Policy](docs/SECURITY_GUARDRAILS.md)
-
---
-
---
-
-## GitHub Topics
-
-For repository maintainers, add these topics to maximize discoverability:
-
-```text
-claude-code, gemini-cli, codex-cli, antigravity, cursor, github-copilot, opencode,
-agentic-skills, ai-coding, llm-tools, ai-agents, autonomous-coding, mcp,
-ai-developer-tools, ai-pair-programming, vibe-coding, skill, skills, SKILL.md, rules.md, CLAUDE.md, GEMINI.md, CURSOR.md
-```
-
---
-
 ## Repo Contributors

 <a href="https://github.com/sickn33/antigravity-awesome-skills/graphs/contributors">
@@ -338,6 +427,28 @@ We officially thank the following contributors for their help in making this rep
 - [@sohamganatra](https://github.com/sohamganatra)
 - [@Nguyen-Van-Chan](https://github.com/Nguyen-Van-Chan)

+---
+
+## License
+
+MIT License. See [LICENSE](LICENSE) for details.
+
+---
+
 ## Star History

 [![Star History Chart](https://api.star-history.com/svg?repos=sickn33/antigravity-awesome-skills&type=date&legend=top-left)](https://www.star-history.com/#sickn33/antigravity-awesome-skills&type=date&legend=top-left)
+
+If Antigravity Awesome Skills has been useful, consider ⭐ starring the repo or [buying me a book](https://buymeacoffee.com/sickn33).
+
+---
+
+## GitHub Topics
+
+For repository maintainers, add these topics to maximize discoverability:
+
+```text
+claude-code, gemini-cli, codex-cli, antigravity, cursor, github-copilot, opencode,
+agentic-skills, ai-coding, llm-tools, ai-agents, autonomous-coding, mcp,
+ai-developer-tools, ai-pair-programming, vibe-coding, skill, skills, SKILL.md, rules.md, CLAUDE.md, GEMINI.md, CURSOR.md
+```
--- a/assets/star-history.png
+++ b/assets/star-history.png
--- a/data/aliases.json
+++ b/data/aliases.json
@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-02-06T07:49:30.257Z",
+  "generatedAt": "2026-02-08T00:00:00.000Z",
  "aliases": {
    "accessibility-compliance-audit": "accessibility-compliance-accessibility-audit",
    "active directory attacks": "active-directory-attacks",
--- a/data/bundles.json
+++ b/data/bundles.json
@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-02-06T07:49:30.257Z",
+  "generatedAt": "2026-02-08T00:00:00.000Z",
  "bundles": {
    "core-dev": {
      "description": "Core development skills across languages, frameworks, and backend/frontend fundamentals.",
@@ -143,6 +143,7 @@
      "description": "Security, privacy, and compliance essentials.",
      "skills": [
        "accessibility-compliance-accessibility-audit",
+        "antigravity-workflows",
        "api-fuzzing-bug-bounty",
        "api-security-best-practices",
        "attack-tree-construction",
--- a/data/catalog.json
+++ b/data/catalog.json
@@ -1,6 +1,6 @@
 {
-  "generatedAt": "2026-02-06T07:49:30.257Z",
-  "total": 713,
+  "generatedAt": "2026-02-08T00:00:00.000Z",
+  "total": 714,
  "skills": [
    {
      "id": "3d-web-experience",
@@ -728,6 +728,30 @@
      ],
      "path": "skills/anti-reversing-techniques/SKILL.md"
    },
+    {
+      "id": "antigravity-workflows",
+      "name": "antigravity-workflows",
+      "description": "Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.",
+      "category": "security",
+      "tags": [
+        "antigravity"
+      ],
+      "triggers": [
+        "antigravity",
+        "orchestrate",
+        "multiple",
+        "skills",
+        "through",
+        "guided",
+        "saas",
+        "mvp",
+        "delivery",
+        "security",
+        "audits",
+        "ai"
+      ],
+      "path": "skills/antigravity-workflows/SKILL.md"
+    },
    {
      "id": "api-design-principles",
      "name": "api-design-principles",
@@ -2969,7 +2993,7 @@
    {
      "id": "clean-code",
      "name": "clean-code",
-      "description": "Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments",
+      "description": "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functions, comments, error handling, and class design.",
      "category": "general",
      "tags": [
        "clean",
@@ -2978,15 +3002,16 @@
      "triggers": [
        "clean",
        "code",
-        "pragmatic",
-        "coding",
-        "standards",
-        "concise",
-        "direct",
-        "no",
-        "engineering",
-        "unnecessary",
-        "comments"
+        "applies",
+        "principles",
+        "robert",
+        "martin",
+        "skill",
+        "writing",
+        "reviewing",
+        "refactoring",
+        "high",
+        "quality"
      ],
      "path": "skills/clean-code/SKILL.md"
    },
--- a/data/workflows.json
+++ b/data/workflows.json
@@ -0,0 +1,216 @@
+{
+  "generatedAt": "2026-02-10T00:00:00.000Z",
+  "version": 1,
+  "workflows": [
+    {
+      "id": "ship-saas-mvp",
+      "name": "Ship a SaaS MVP",
+      "description": "End-to-end workflow to scope, build, test, and ship a SaaS MVP quickly.",
+      "category": "web",
+      "relatedBundles": [
+        "core-dev",
+        "ops-core"
+      ],
+      "steps": [
+        {
+          "title": "Plan the scope",
+          "goal": "Convert the idea into a clear implementation plan and milestones.",
+          "recommendedSkills": [
+            "brainstorming",
+            "concise-planning",
+            "writing-plans"
+          ],
+          "notes": "Define problem, user persona, MVP boundaries, and acceptance criteria before coding."
+        },
+        {
+          "title": "Build backend and API",
+          "goal": "Implement the core data model, API contracts, and auth baseline.",
+          "recommendedSkills": [
+            "backend-dev-guidelines",
+            "api-patterns",
+            "database-design",
+            "auth-implementation-patterns"
+          ],
+          "notes": "Prefer small vertical slices; keep API contracts explicit and testable."
+        },
+        {
+          "title": "Build frontend",
+          "goal": "Deliver the primary user flows with production-grade UX patterns.",
+          "recommendedSkills": [
+            "frontend-developer",
+            "react-patterns",
+            "frontend-design"
+          ],
+          "notes": "Prioritize onboarding, empty states, and one complete happy-path flow."
+        },
+        {
+          "title": "Test and validate",
+          "goal": "Catch regressions and ensure key flows work before release.",
+          "recommendedSkills": [
+            "test-driven-development",
+            "systematic-debugging",
+            "browser-automation",
+            "go-playwright"
+          ],
+          "notes": "Use go-playwright when the product stack or QA tooling is Go-based."
+        },
+        {
+          "title": "Ship safely",
+          "goal": "Release with basic observability and rollback readiness.",
+          "recommendedSkills": [
+            "deployment-procedures",
+            "observability-engineer",
+            "postmortem-writing"
+          ],
+          "notes": "Define release checklist, minimum telemetry, and rollback triggers."
+        }
+      ]
+    },
+    {
+      "id": "security-audit-web-app",
+      "name": "Security Audit for a Web App",
+      "description": "Structured workflow for baseline AppSec review and risk triage.",
+      "category": "security",
+      "relatedBundles": [
+        "security-core",
+        "ops-core"
+      ],
+      "steps": [
+        {
+          "title": "Define scope and threat model",
+          "goal": "Identify critical assets, trust boundaries, and threat scenarios.",
+          "recommendedSkills": [
+            "ethical-hacking-methodology",
+            "threat-modeling-expert",
+            "attack-tree-construction"
+          ],
+          "notes": "Document in-scope targets, assumptions, and out-of-scope constraints."
+        },
+        {
+          "title": "Review authentication and authorization",
+          "goal": "Find broken auth patterns and access-control weaknesses.",
+          "recommendedSkills": [
+            "broken-authentication",
+            "auth-implementation-patterns",
+            "idor-testing"
+          ],
+          "notes": "Prioritize account takeover and privilege escalation paths."
+        },
+        {
+          "title": "Assess API and input security",
+          "goal": "Detect high-impact API and injection risks.",
+          "recommendedSkills": [
+            "api-security-best-practices",
+            "api-fuzzing-bug-bounty",
+            "top-web-vulnerabilities"
+          ],
+          "notes": "Map findings to severity and exploitability, not only CVSS."
+        },
+        {
+          "title": "Harden and verify",
+          "goal": "Translate findings into concrete remediations and retest.",
+          "recommendedSkills": [
+            "security-auditor",
+            "sast-configuration",
+            "verification-before-completion"
+          ],
+          "notes": "Track remediation owners and target dates; verify each fix with evidence."
+        }
+      ]
+    },
+    {
+      "id": "build-ai-agent-system",
+      "name": "Build an AI Agent System",
+      "description": "Workflow to design, implement, and evaluate a production-ready AI agent.",
+      "category": "ai-agents",
+      "relatedBundles": [
+        "core-dev",
+        "data-core"
+      ],
+      "steps": [
+        {
+          "title": "Define use case and reliability targets",
+          "goal": "Choose a narrow use case and measurable quality goals.",
+          "recommendedSkills": [
+            "ai-agents-architect",
+            "agent-evaluation",
+            "product-manager-toolkit"
+          ],
+          "notes": "Set latency, quality, and failure-rate thresholds before implementation."
+        },
+        {
+          "title": "Design architecture and retrieval",
+          "goal": "Design tools, memory, and retrieval strategy for the agent.",
+          "recommendedSkills": [
+            "llm-app-patterns",
+            "rag-implementation",
+            "vector-database-engineer",
+            "embedding-strategies"
+          ],
+          "notes": "Keep retrieval quality measurable and version prompt/tool contracts."
+        },
+        {
+          "title": "Implement orchestration",
+          "goal": "Implement the orchestration loop and production safeguards.",
+          "recommendedSkills": [
+            "langgraph",
+            "mcp-builder",
+            "workflow-automation"
+          ],
+          "notes": "Start with constrained tool permissions and explicit fallback behavior."
+        },
+        {
+          "title": "Evaluate and iterate",
+          "goal": "Run benchmark scenarios and improve weak areas systematically.",
+          "recommendedSkills": [
+            "agent-evaluation",
+            "langfuse",
+            "kaizen"
+          ],
+          "notes": "Use test datasets and failure buckets to guide each iteration cycle."
+        }
+      ]
+    },
+    {
+      "id": "qa-browser-automation",
+      "name": "QA and Browser Automation",
+      "description": "Workflow for robust E2E and browser-driven validation across stacks.",
+      "category": "testing",
+      "relatedBundles": [
+        "core-dev",
+        "ops-core"
+      ],
+      "steps": [
+        {
+          "title": "Prepare test strategy",
+          "goal": "Define critical user journeys, environments, and test data.",
+          "recommendedSkills": [
+            "e2e-testing-patterns",
+            "test-driven-development",
+            "code-review-checklist"
+          ],
+          "notes": "Focus on business-critical flows and keep setup deterministic."
+        },
+        {
+          "title": "Implement browser tests",
+          "goal": "Automate key flows with resilient locators and stable waits.",
+          "recommendedSkills": [
+            "browser-automation",
+            "go-playwright"
+          ],
+          "notes": "Use go-playwright for Go-native automation projects and Playwright for JS/TS stacks."
+        },
+        {
+          "title": "Triage failures and harden",
+          "goal": "Stabilize flaky tests and establish repeatable CI execution.",
+          "recommendedSkills": [
+            "systematic-debugging",
+            "test-fixing",
+            "verification-before-completion"
+          ],
+          "notes": "Classify failures by root cause: selector drift, timing, environment, data."
+        }
+      ]
+    }
+  ]
+}
--- a/docs/BUNDLES.md
+++ b/docs/BUNDLES.md
@@ -14,9 +14,10 @@
 2. **Choose your bundle** from the list below based on your role or interests.

 3. **Use skills** by referencing them in your AI assistant:
-   - Claude Code: `>> @skill-name help me...`
+   - Claude Code: `>> /skill-name help me...`
   - Cursor: `@skill-name in chat`
   - Gemini CLI: `Use skill-name...`
+   - Codex CLI: `Use skill-name...`

 ---

@@ -328,33 +329,77 @@ _For system design and technical decisions._

 ---

+## 🧰 Maintainer & OSS
+
+### 🛠️ The "OSS Maintainer" Pack
+
+_For shipping clean changes in public repositories._
+
+- [`commit`](../skills/commit/): High-quality conventional commits.
+- [`create-pr`](../skills/create-pr/): PR creation with review-ready context.
+- [`requesting-code-review`](../skills/requesting-code-review/): Ask for targeted, high-signal reviews.
+- [`receiving-code-review`](../skills/receiving-code-review/): Apply feedback with technical rigor.
+- [`changelog-automation`](../skills/changelog-automation/): Keep release notes and changelogs consistent.
+- [`git-advanced-workflows`](../skills/git-advanced-workflows/): Rebase, cherry-pick, bisect, recovery.
+- [`documentation-templates`](../skills/documentation-templates/): Standardize docs and handoffs.
+
+### 🧱 The "Skill Author" Pack
+
+_For creating and maintaining high-quality SKILL.md assets._
+
+- [`skill-creator`](../skills/skill-creator/): Design effective new skills.
+- [`skill-developer`](../skills/skill-developer/): Implement triggers, hooks, and skill lifecycle.
+- [`writing-skills`](../skills/writing-skills/): Improve clarity and structure of skill instructions.
+- [`documentation-generation-doc-generate`](../skills/documentation-generation-doc-generate/): Generate maintainable technical docs.
+- [`lint-and-validate`](../skills/lint-and-validate/): Validate quality after edits.
+- [`verification-before-completion`](../skills/verification-before-completion/): Confirm changes before claiming done.
+
+---
+
 ## 📚 How to Use Bundles

-### Installation
+### 1) Pick by immediate goal

-1. **Clone the repository:**
-   ```bash
-   git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills
-   ```
+- Need to ship a feature now: `Essentials` + one domain pack (`Web Wizard`, `Python Pro`, `DevOps & Cloud`).
+- Need reliability and hardening: add `QA & Testing` + `Security Developer`.
+- Need product growth: add `Startup Founder` or `Marketing & Growth`.

-2. **Or use the installer:**
-   ```bash
-   npx antigravity-awesome-skills
-   ```
+### 2) Start with 3-5 skills, not 20

-### Using Skills
+Pick the minimum set for your current milestone. Expand only when you hit a real gap.

-Once installed, reference skills in your AI assistant:
+### 3) Invoke skills consistently

- **Claude Code**: `>> @skill-name help me...`
+- **Claude Code**: `>> /skill-name help me...`
 - **Cursor**: `@skill-name` in chat
 - **Gemini CLI**: `Use skill-name...`
+- **Codex CLI**: `Use skill-name...`

-### Customizing Bundles
+### 4) Build your personal shortlist

-You can create your own bundle by:
-1. Copying skill folders to your `.agent/skills/` directory
-2. Or referencing multiple skills in a single conversation
+Keep a small list of high-frequency skills and reuse it across tasks to reduce context switching.
+
+## 🧩 Recommended Bundle Combos
+
+### Ship a SaaS MVP (2 weeks)
+
+`Essentials` + `Full-Stack Developer` + `QA & Testing` + `Startup Founder`
+
+### Harden an existing production app
+
+`Essentials` + `Security Developer` + `DevOps & Cloud` + `Observability & Monitoring`
+
+### Build an AI product
+
+`Essentials` + `Agent Architect` + `LLM Application Developer` + `Data Engineering`
+
+### Grow traffic and conversions
+
+`Web Wizard` + `Marketing & Growth` + `Data & Analytics`
+
+### Launch and maintain open source
+
+`Essentials` + `OSS Maintainer` + `Architecture & Design`

 ---

@@ -377,6 +422,11 @@ You can create your own bundle by:
 2. Grow: `Security Engineer` → Advanced pentesting
 3. Master: Red team tactics and threat modeling

+**Open Source Maintenance:**
+1. Start: `Essentials` → `OSS Maintainer`
+2. Grow: `Architecture & Design` → `QA & Testing`
+3. Master: `Skill Author` + release automation workflows
+
 ---

 ## 🤝 Contributing
@@ -393,4 +443,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open

 ---

-_Last updated: January 2026 | Total Skills: 560+ | Total Bundles: 20+_
+_Last updated: February 2026 | Total Skills: 713+ | Total Bundles: 26_
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -11,12 +11,23 @@
 Skills are specialized instruction files that teach AI assistants how to handle specific tasks. Think of them as expert knowledge modules that your AI can load on-demand.
 **Simple analogy:** Just like you might consult different experts (a lawyer, a doctor, a mechanic), these skills let your AI become an expert in different areas when you need them.

-### Do I need to install all 626+ skills?
+### Do I need to install all 700+ skills?

 **No!** When you clone the repository, all skills are available, but your AI only loads them when you explicitly invoke them with `@skill-name`.
 It's like having a library - all books are there, but you only read the ones you need.
 **Pro Tip:** Use [Starter Packs](BUNDLES.md) to install only what matches your role.

+### What is the difference between Bundles and Workflows?
+
+- **Bundles** are curated recommendations grouped by role or domain.
+- **Workflows** are ordered execution playbooks for concrete outcomes.
+
+Use bundles when you are deciding *which skills* to include. Use workflows when you need *step-by-step execution*.
+
+Start from:
+- [BUNDLES.md](BUNDLES.md)
+- [WORKFLOWS.md](WORKFLOWS.md)
+
 ### Which AI tools work with these skills?

 - ✅ **Claude Code** (Anthropic CLI)
--- a/docs/GETTING_STARTED.md
+++ b/docs/GETTING_STARTED.md
@@ -15,7 +15,7 @@ AI Agents (like **Claude Code**, **Gemini**, **Cursor**) are smart, but they lac

 ## ⚡️ Quick Start: The "Starter Packs"

-Don't panic about the 626+ skills. You don't need them all at once.
+Don't panic about the 700+ skills. You don't need them all at once.
 We have curated **Starter Packs** to get you running immediately.

 You **install the full repo once** (npx or clone); Starter Packs are curated lists to help you **pick which skills to use** by role (e.g. Web Wizard, Hacker Pack)—they are not a different way to install.
@@ -52,6 +52,21 @@ Find the bundle that matches your role (see [BUNDLES.md](BUNDLES.md)):

 ---

+## 🧭 Bundles vs Workflows
+
+Bundles and workflows solve different problems:
+
+- **Bundles** = curated sets by role (what to pick).
+- **Workflows** = step-by-step playbooks (how to execute).
+
+Start with bundles in [BUNDLES.md](BUNDLES.md), then run a workflow from [WORKFLOWS.md](WORKFLOWS.md) when you need guided execution.
+
+Example:
+
+> "Use **@antigravity-workflows** and run `ship-saas-mvp` for my project idea."
+
+---
+
 ## 🚀 How to Use a Skill

 Once installed, just talk to your AI naturally.
@@ -103,7 +118,7 @@ _Check the [Skill Catalog](../CATALOG.md) for the full list._

 ## ❓ FAQ

-**Q: Do I need to install all 626 skills?**
+**Q: Do I need to install all 700+ skills?**
 A: You clone the whole repo once; your AI only _reads_ the skills you invoke (or that are relevant), so it stays lightweight. **Starter Packs** in [BUNDLES.md](BUNDLES.md) are curated lists to help you discover the right skills for your role—they don't change how you install.

 **Q: Can I make my own skills?**
--- a/docs/WORKFLOWS.md
+++ b/docs/WORKFLOWS.md
@@ -0,0 +1,174 @@
+# Antigravity Workflows
+
+> Workflow playbooks to orchestrate multiple skills with less friction.
+
+## What Is a Workflow?
+
+A workflow is a guided, step-by-step execution path that combines multiple skills for one concrete outcome.
+
+- **Bundles** tell you which skills are relevant for a role.
+- **Workflows** tell you how to use those skills in sequence to complete a real objective.
+
+If bundles are your toolbox, workflows are your execution playbook.
+
+---
+
+## How to Use Workflows
+
+1. Install the repository once (`npx antigravity-awesome-skills`).
+2. Pick a workflow matching your immediate goal.
+3. Execute steps in order and invoke the listed skills in each step.
+4. Keep output artifacts at each step (plan, decisions, tests, validation evidence).
+
+You can combine workflows with bundles from [BUNDLES.md](BUNDLES.md) when you need broader coverage.
+
+---
+
+## Workflow: Ship a SaaS MVP
+
+Build and ship a minimal but production-minded SaaS product.
+
+**Related bundles:** `Essentials`, `Full-Stack Developer`, `QA & Testing`, `DevOps & Cloud`
+
+### Prerequisites
+
+- Local repository and runtime configured.
+- Clear user problem and MVP scope.
+- Basic deployment target selected.
+
+### Steps
+
+1. **Plan the scope**
+   - **Goal:** Define MVP boundaries and acceptance criteria.
+   - **Skills:** [`@brainstorming`](../skills/brainstorming/), [`@concise-planning`](../skills/concise-planning/), [`@writing-plans`](../skills/writing-plans/)
+   - **Prompt example:** `Usa @concise-planning per definire milestones e criteri di accettazione del mio MVP SaaS.`
+
+2. **Build backend and API**
+   - **Goal:** Implement core entities, APIs, and auth baseline.
+   - **Skills:** [`@backend-dev-guidelines`](../skills/backend-dev-guidelines/), [`@api-patterns`](../skills/api-patterns/), [`@database-design`](../skills/database-design/)
+   - **Prompt example:** `Usa @backend-dev-guidelines per creare API e servizi del dominio billing.`
+
+3. **Build frontend**
+   - **Goal:** Ship core user flow with clear UX states.
+   - **Skills:** [`@frontend-developer`](../skills/frontend-developer/), [`@react-patterns`](../skills/react-patterns/), [`@frontend-design`](../skills/frontend-design/)
+   - **Prompt example:** `Usa @frontend-developer per implementare onboarding, empty state e dashboard iniziale.`
+
+4. **Test and validate**
+   - **Goal:** Cover critical user journeys before release.
+   - **Skills:** [`@test-driven-development`](../skills/test-driven-development/), [`@browser-automation`](../skills/browser-automation/), `@go-playwright` (optional, Go stack)
+   - **Prompt example:** `Usa @browser-automation per creare test E2E sui flussi signup e checkout.`
+   - **Go note:** Se il progetto QA e tooling sono in Go, preferisci `@go-playwright`.
+
+5. **Ship safely**
+   - **Goal:** Release with observability and rollback plan.
+   - **Skills:** [`@deployment-procedures`](../skills/deployment-procedures/), [`@observability-engineer`](../skills/observability-engineer/)
+   - **Prompt example:** `Usa @deployment-procedures per una checklist di rilascio con rollback.`
+
+---
+
+## Workflow: Security Audit for a Web App
+
+Run a focused security review from scope definition to remediation validation.
+
+**Related bundles:** `Security Engineer`, `Security Developer`, `Observability & Monitoring`
+
+### Prerequisites
+
+- Explicit authorization for testing.
+- In-scope targets documented.
+- Logging and environment details available.
+
+### Steps
+
+1. **Define scope and threat model**
+   - **Goal:** Identify assets, trust boundaries, and attack paths.
+   - **Skills:** [`@ethical-hacking-methodology`](../skills/ethical-hacking-methodology/), [`@threat-modeling-expert`](../skills/threat-modeling-expert/), [`@attack-tree-construction`](../skills/attack-tree-construction/)
+   - **Prompt example:** `Usa @threat-modeling-expert per mappare asset critici e trust boundaries della mia web app.`
+
+2. **Review auth and access control**
+   - **Goal:** Detect account takeover and authorization flaws.
+   - **Skills:** [`@broken-authentication`](../skills/broken-authentication/), [`@auth-implementation-patterns`](../skills/auth-implementation-patterns/), [`@idor-testing`](../skills/idor-testing/)
+   - **Prompt example:** `Usa @idor-testing per verificare accessi non autorizzati su endpoint multitenant.`
+
+3. **Assess API and input security**
+   - **Goal:** Uncover high-impact API and injection vulnerabilities.
+   - **Skills:** [`@api-security-best-practices`](../skills/api-security-best-practices/), [`@api-fuzzing-bug-bounty`](../skills/api-fuzzing-bug-bounty/), [`@top-web-vulnerabilities`](../skills/top-web-vulnerabilities/)
+   - **Prompt example:** `Usa @api-security-best-practices per audit endpoint auth, billing e admin.`
+
+4. **Harden and verify**
+   - **Goal:** Convert findings into fixes and verify evidence of mitigation.
+   - **Skills:** [`@security-auditor`](../skills/security-auditor/), [`@sast-configuration`](../skills/sast-configuration/), [`@verification-before-completion`](../skills/verification-before-completion/)
+   - **Prompt example:** `Usa @verification-before-completion per provare che le mitigazioni sono effettive.`
+
+---
+
+## Workflow: Build an AI Agent System
+
+Design and deliver a production-grade agent with measurable reliability.
+
+**Related bundles:** `Agent Architect`, `LLM Application Developer`, `Data Engineering`
+
+### Prerequisites
+
+- Narrow use case with measurable outcomes.
+- Access to model provider(s) and observability tooling.
+- Initial dataset or knowledge corpus.
+
+### Steps
+
+1. **Define target behavior and KPIs**
+   - **Goal:** Set quality, latency, and failure thresholds.
+   - **Skills:** [`@ai-agents-architect`](../skills/ai-agents-architect/), [`@agent-evaluation`](../skills/agent-evaluation/), [`@product-manager-toolkit`](../skills/product-manager-toolkit/)
+   - **Prompt example:** `Usa @agent-evaluation per definire benchmark e criteri di successo del mio agente.`
+
+2. **Design retrieval and memory**
+   - **Goal:** Build reliable retrieval and context architecture.
+   - **Skills:** [`@llm-app-patterns`](../skills/llm-app-patterns/), [`@rag-implementation`](../skills/rag-implementation/), [`@vector-database-engineer`](../skills/vector-database-engineer/)
+   - **Prompt example:** `Usa @rag-implementation per progettare pipeline di chunking, embedding e retrieval.`
+
+3. **Implement orchestration**
+   - **Goal:** Implement deterministic orchestration and tool boundaries.
+   - **Skills:** [`@langgraph`](../skills/langgraph/), [`@mcp-builder`](../skills/mcp-builder/), [`@workflow-automation`](../skills/workflow-automation/)
+   - **Prompt example:** `Usa @langgraph per implementare il grafo agente con fallback e human-in-the-loop.`
+
+4. **Evaluate and iterate**
+   - **Goal:** Improve weak points with a structured loop.
+   - **Skills:** [`@agent-evaluation`](../skills/agent-evaluation/), [`@langfuse`](../skills/langfuse/), [`@kaizen`](../skills/kaizen/)
+   - **Prompt example:** `Usa @kaizen per prioritizzare le correzioni sulle failure modes rilevate dai test.`
+
+---
+
+## Workflow: QA and Browser Automation
+
+Create resilient browser automation with deterministic execution in CI.
+
+**Related bundles:** `QA & Testing`, `Full-Stack Developer`
+
+### Prerequisites
+
+- Test environments and stable credentials.
+- Critical user journeys identified.
+- CI pipeline available.
+
+### Steps
+
+1. **Prepare test strategy**
+   - **Goal:** Scope journeys, fixtures, and execution environments.
+   - **Skills:** [`@e2e-testing-patterns`](../skills/e2e-testing-patterns/), [`@test-driven-development`](../skills/test-driven-development/)
+   - **Prompt example:** `Usa @e2e-testing-patterns per definire suite E2E minima ma ad alto impatto.`
+
+2. **Implement browser tests**
+   - **Goal:** Build robust test coverage with stable selectors.
+   - **Skills:** [`@browser-automation`](../skills/browser-automation/), `@go-playwright` (optional, Go stack)
+   - **Prompt example:** `Usa @go-playwright per implementare browser automation in un progetto Go.`
+
+3. **Triage and harden**
+   - **Goal:** Remove flaky behavior and enforce repeatability.
+   - **Skills:** [`@systematic-debugging`](../skills/systematic-debugging/), [`@test-fixing`](../skills/test-fixing/), [`@verification-before-completion`](../skills/verification-before-completion/)
+   - **Prompt example:** `Usa @systematic-debugging per classificare e risolvere le flakiness in CI.`
+
+---
+
+## Machine-Readable Workflows
+
+For tooling and automation, workflow metadata is available in [data/workflows.json](../data/workflows.json).
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
  "name": "antigravity-awesome-skills",
-  "version": "4.10.0",
+  "version": "5.0.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "antigravity-awesome-skills",
-      "version": "4.10.0",
+      "version": "5.0.0",
      "license": "MIT",
      "bin": {
        "antigravity-awesome-skills": "bin/install.js"
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
  "name": "antigravity-awesome-skills",
-  "version": "4.10.0",
+  "version": "5.0.0",
  "description": "626+ agentic skills for Claude Code, Gemini CLI, Cursor, Antigravity & more. Installer CLI.",
  "license": "MIT",
  "scripts": {
--- a/release_notes.md
+++ b/release_notes.md
@@ -1,25 +1,36 @@
-## [4.10.0] - 2026-02-06 - "Composio Automation + .NET Backend"
+## [5.0.0] - 2026-02-10 - "Antigravity Workflows Foundation"

-> Merged two community PRs adding broad automation coverage and a dedicated .NET backend skill.
+> First-class Workflows are now available to orchestrate multiple skills through guided execution playbooks.

-### Added
+### 🚀 New Skills

- 79 new skills total:
- 78 Composio/Rube automation skills (PR #64)
- 1 .NET backend skill (PR #65)
- Registry increased from 634 to 713 skills.
+### 🧭 [antigravity-workflows](skills/antigravity-workflows/)

-### Changed
+**Orchestrates multi-step outcomes using curated workflow playbooks.**
+This new skill routes users from high-level goals to concrete execution steps across related skills and bundles.

- Synced generated registry artifacts:
- README.md
- skills_index.json
- CATALOG.md
- data/catalog.json
- data/bundles.json
- data/aliases.json
+- **Key Feature 1**: Workflow routing for SaaS MVP, Security Audit, AI Agent Systems, and Browser QA.
+- **Key Feature 2**: Explicit step-by-step outputs with prerequisites, recommended skills, and validation checkpoints.

-### Contributors
+> **Try it:** `Use @antigravity-workflows to run ship-saas-mvp for my project.`

- [@sohamganatra](https://github.com/sohamganatra)
- [@Nguyen-Van-Chan](https://github.com/Nguyen-Van-Chan)
+---
+
+## 📦 Improvements
+
+- **Workflow Registry**: Added `data/workflows.json` for machine-readable workflow metadata.
+- **Workflow Docs**: Added `docs/WORKFLOWS.md` to distinguish Bundles vs Workflows and provide practical execution playbooks.
+- **Trinity Sync**: Updated `README.md`, `docs/GETTING_STARTED.md`, and `docs/FAQ.md` for workflow onboarding.
+- **Go QA Path**: Added optional `@go-playwright` wiring in QA/E2E workflow steps.
+- **Registry Update**: Catalog regenerated; repository now tracks 714 skills.
+
+## 👥 Credits
+
+A huge shoutout to our community and maintainers:
+
+- **@Walapalam** for the Workflows concept request ([Issue #72](https://github.com/sickn33/antigravity-awesome-skills/issues/72))
+- **@sickn33** for workflow integration, release preparation, and maintenance updates
+
+---
+
+_Upgrade now: `git pull origin main` to fetch the latest skills._
--- a/scripts/build-catalog.js
+++ b/scripts/build-catalog.js
@@ -318,9 +318,11 @@ function buildCatalog() {
  }

  const catalog = {
-    generatedAt: new Date().toISOString(),
+    generatedAt: process.env.SOURCE_DATE_EPOCH 
+      ? new Date(process.env.SOURCE_DATE_EPOCH * 1000).toISOString() 
+      : (process.env.CI ? '2026-02-08T00:00:00.000Z' : new Date().toISOString()),
    total: catalogSkills.length,
-    skills: catalogSkills.sort((a, b) => a.id.localeCompare(b.id)),
+    skills: catalogSkills.sort((a, b) => (a.id < b.id ? -1 : a.id > b.id ? 1 : 0)),
  };

  const aliases = buildAliases(catalog.skills);
--- a/skills/antigravity-workflows/SKILL.md
+++ b/skills/antigravity-workflows/SKILL.md
@@ -0,0 +1,80 @@
+---
+name: antigravity-workflows
+description: "Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA."
+source: self
+risk: none
+---
+
+# Antigravity Workflows
+
+Use this skill to turn a complex objective into a guided sequence of skill invocations.
+
+## When to Use This Skill
+
+Use this skill when:
+- The user wants to combine several skills without manually selecting each one.
+- The goal is multi-phase (for example: plan, build, test, ship).
+- The user asks for best-practice execution for common scenarios like:
+  - Shipping a SaaS MVP
+  - Running a web security audit
+  - Building an AI agent system
+  - Implementing browser automation and E2E QA
+
+## Workflow Source of Truth
+
+Read workflows in this order:
+1. `docs/WORKFLOWS.md` for human-readable playbooks.
+2. `data/workflows.json` for machine-readable workflow metadata.
+
+## How to Run This Skill
+
+1. Identify the user's concrete outcome.
+2. Propose the 1-2 best matching workflows.
+3. Ask the user to choose one.
+4. Execute step-by-step:
+   - Announce current step and expected artifact.
+   - Invoke recommended skills for that step.
+   - Verify completion criteria before moving to next step.
+5. At the end, provide:
+   - Completed artifacts
+   - Validation evidence
+   - Remaining risks and next actions
+
+## Default Workflow Routing
+
+- Product delivery request -> `ship-saas-mvp`
+- Security review request -> `security-audit-web-app`
+- Agent/LLM product request -> `build-ai-agent-system`
+- E2E/browser testing request -> `qa-browser-automation`
+
+## Copy-Paste Prompts
+
+```text
+Use @antigravity-workflows to run the "Ship a SaaS MVP" workflow for my project idea.
+```
+
+```text
+Use @antigravity-workflows and execute a full "Security Audit for a Web App" workflow.
+```
+
+```text
+Use @antigravity-workflows to guide me through "Build an AI Agent System" with checkpoints.
+```
+
+```text
+Use @antigravity-workflows to execute the "QA and Browser Automation" workflow and stabilize flaky tests.
+```
+
+## Limitations
+
+- This skill orchestrates; it does not replace specialized skills.
+- It depends on the local availability of referenced skills.
+- It does not guarantee success without environment access, credentials, or required infrastructure.
+- For stack-specific browser automation in Go, `go-playwright` may require the corresponding skill to be present in your local skills repository.
+
+## Related Skills
+
+- `concise-planning`
+- `brainstorming`
+- `workflow-automation`
+- `verification-before-completion`
--- a/skills/antigravity-workflows/resources/implementation-playbook.md
+++ b/skills/antigravity-workflows/resources/implementation-playbook.md
@@ -0,0 +1,36 @@
+# Antigravity Workflows Implementation Playbook
+
+This document explains how an agent should execute workflow-based orchestration.
+
+## Execution Contract
+
+For every workflow:
+
+1. Confirm objective and scope.
+2. Select the best-matching workflow.
+3. Execute workflow steps in order.
+4. Produce one concrete artifact per step.
+5. Validate before continuing.
+
+## Step Artifact Examples
+
+- Plan step -> scope document or milestone checklist.
+- Build step -> code changes and implementation notes.
+- Test step -> test results and failure triage.
+- Release step -> rollout checklist and risk log.
+
+## Safety Guardrails
+
+- Never run destructive actions without explicit user approval.
+- If a required skill is missing, state the gap and fallback to closest available skill.
+- When security testing is involved, ensure authorization is explicit.
+
+## Suggested Completion Format
+
+At workflow completion, return:
+
+1. Completed steps
+2. Artifacts produced
+3. Validation evidence
+4. Open risks
+5. Suggested next action
--- a/skills/clean-code/SKILL.md
+++ b/skills/clean-code/SKILL.md
@@ -1,201 +1,94 @@
 ---
 name: clean-code
-description: Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
-allowed-tools: Read, Write, Edit
-version: 2.0
-priority: CRITICAL
+description: "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functions, comments, error handling, and class design."
+user-invocable: true
+risk: safe
+source: "ClawForge (https://github.com/jackjin1997/ClawForge)"
 ---

-# Clean Code - Pragmatic AI Coding Standards
+# Clean Code Skill

-> **CRITICAL SKILL** - Be **concise, direct, and solution-focused**.
+This skill embodies the principles of "Clean Code" by Robert C. Martin (Uncle Bob). Use it to transform "code that works" into "code that is clean."

---
+## 🧠 Core Philosophy
+> "Code is clean if it can be read, and enhanced by a developer other than its original author." — Grady Booch

-## Core Principles
+## When to Use
+Use this skill when:
+- **Writing new code**: To ensure high quality from the start.
+- **Reviewing Pull Requests**: To provide constructive, principle-based feedback.
+- **Refactoring legacy code**: To identify and remove code smells.
+- **Improving team standards**: To align on industry-standard best practices.

-| Principle | Rule |
-|-----------|------|
-| **SRP** | Single Responsibility - each function/class does ONE thing |
-| **DRY** | Don't Repeat Yourself - extract duplicates, reuse |
-| **KISS** | Keep It Simple - simplest solution that works |
-| **YAGNI** | You Aren't Gonna Need It - don't build unused features |
-| **Boy Scout** | Leave code cleaner than you found it |
+## 1. Meaningful Names
+- **Use Intention-Revealing Names**: `elapsedTimeInDays` instead of `d`.
+- **Avoid Disinformation**: Don't use `accountList` if it's actually a `Map`.
+- **Make Meaningful Distinctions**: Avoid `ProductData` vs `ProductInfo`.
+- **Use Pronounceable/Searchable Names**: Avoid `genymdhms`.
+- **Class Names**: Use nouns (`Customer`, `WikiPage`). Avoid `Manager`, `Data`.
+- **Method Names**: Use verbs (`postPayment`, `deletePage`).

---
+## 2. Functions
+- **Small!**: Functions should be shorter than you think.
+- **Do One Thing**: A function should do only one thing, and do it well.
+- **One Level of Abstraction**: Don't mix high-level business logic with low-level details (like regex).
+- **Descriptive Names**: `isPasswordValid` is better than `check`.
+- **Arguments**: 0 is ideal, 1-2 is okay, 3+ requires a very strong justification.
+- **No Side Effects**: Functions shouldn't secretly change global state.

-## Naming Rules
+## 3. Comments
+- **Don't Comment Bad Code—Rewrite It**: Most comments are a sign of failure to express ourselves in code.
+- **Explain Yourself in Code**: 
+  ```python
+  # Check if employee is eligible for full benefits
+  if employee.flags & HOURLY and employee.age > 65:
+  ```
+  vs
+  ```python
+  if employee.isEligibleForFullBenefits():
+  ```
+- **Good Comments**: Legal, Informative (regex intent), Clarification (external libraries), TODOs.
+- **Bad Comments**: Mumbling, Redundant, Misleading, Mandated, Noise, Position Markers.

-| Element | Convention |
-|---------|------------|
-| **Variables** | Reveal intent: `userCount` not `n` |
-| **Functions** | Verb + noun: `getUserById()` not `user()` |
-| **Booleans** | Question form: `isActive`, `hasPermission`, `canEdit` |
-| **Constants** | SCREAMING_SNAKE: `MAX_RETRY_COUNT` |
+## 4. Formatting
+- **The Newspaper Metaphor**: High-level concepts at the top, details at the bottom.
+- **Vertical Density**: Related lines should be close to each other.
+- **Distance**: Variables should be declared near their usage.
+- **Indentation**: Essential for structural readability.

-> **Rule:** If you need a comment to explain a name, rename it.
+## 5. Objects and Data Structures
+- **Data Abstraction**: Hide the implementation behind interfaces.
+- **The Law of Demeter**: A module should not know about the innards of the objects it manipulates. Avoid `a.getB().getC().doSomething()`.
+- **Data Transfer Objects (DTO)**: Classes with public variables and no functions.

---
+## 6. Error Handling
+- **Use Exceptions instead of Return Codes**: Keeps logic clean.
+- **Write Try-Catch-Finally First**: Defines the scope of the operation.
+- **Don't Return Null**: It forces the caller to check for null every time.
+- **Don't Pass Null**: Leads to `NullPointerException`.

-## Function Rules
+## 7. Unit Tests
+- **The Three Laws of TDD**:
+  1. Don't write production code until you have a failing unit test.
+  2. Don't write more of a unit test than is sufficient to fail.
+  3. Don't write more production code than is sufficient to pass the failing test.
+- **F.I.R.S.T. Principles**: Fast, Independent, Repeatable, Self-Validating, Timely.

-| Rule | Description |
-|------|-------------|
-| **Small** | Max 20 lines, ideally 5-10 |
-| **One Thing** | Does one thing, does it well |
-| **One Level** | One level of abstraction per function |
-| **Few Args** | Max 3 arguments, prefer 0-2 |
-| **No Side Effects** | Don't mutate inputs unexpectedly |
+## 8. Classes
+- **Small!**: Classes should have a single responsibility (SRP).
+- **The Stepdown Rule**: We want the code to read like a top-down narrative.

---
-
-## Code Structure
-
-| Pattern | Apply |
-|---------|-------|
-| **Guard Clauses** | Early returns for edge cases |
-| **Flat > Nested** | Avoid deep nesting (max 2 levels) |
-| **Composition** | Small functions composed together |
-| **Colocation** | Keep related code close |
-
---
-
-## AI Coding Style
-
-| Situation | Action |
-|-----------|--------|
-| User asks for feature | Write it directly |
-| User reports bug | Fix it, don't explain |
-| No clear requirement | Ask, don't assume |
-
---
-
-## Anti-Patterns (DON'T)
-
-| ❌ Pattern | ✅ Fix |
-|-----------|-------|
-| Comment every line | Delete obvious comments |
-| Helper for one-liner | Inline the code |
-| Factory for 2 objects | Direct instantiation |
-| utils.ts with 1 function | Put code where used |
-| "First we import..." | Just write code |
-| Deep nesting | Guard clauses |
-| Magic numbers | Named constants |
-| God functions | Split by responsibility |
-
---
-
-## 🔴 Before Editing ANY File (THINK FIRST!)
-
-**Before changing a file, ask yourself:**
-
-| Question | Why |
-|----------|-----|
-| **What imports this file?** | They might break |
-| **What does this file import?** | Interface changes |
-| **What tests cover this?** | Tests might fail |
-| **Is this a shared component?** | Multiple places affected |
-
-**Quick Check:**
-```
-File to edit: UserService.ts
-└── Who imports this? → UserController.ts, AuthController.ts
-└── Do they need changes too? → Check function signatures
-```
-
-> 🔴 **Rule:** Edit the file + all dependent files in the SAME task.
-> 🔴 **Never leave broken imports or missing updates.**
-
---
-
-## Summary
-
-| Do | Don't |
-|----|-------|
-| Write code directly | Write tutorials |
-| Let code self-document | Add obvious comments |
-| Fix bugs immediately | Explain the fix first |
-| Inline small things | Create unnecessary files |
-| Name things clearly | Use abbreviations |
-| Keep functions small | Write 100+ line functions |
-
-> **Remember: The user wants working code, not a programming lesson.**
-
---
-
-## 🔴 Self-Check Before Completing (MANDATORY)
-
-**Before saying "task complete", verify:**
-
-| Check | Question |
-|-------|----------|
-| ✅ **Goal met?** | Did I do exactly what user asked? |
-| ✅ **Files edited?** | Did I modify all necessary files? |
-| ✅ **Code works?** | Did I test/verify the change? |
-| ✅ **No errors?** | Lint and TypeScript pass? |
-| ✅ **Nothing forgotten?** | Any edge cases missed? |
-
-> 🔴 **Rule:** If ANY check fails, fix it before completing.
-
---
-
-## Verification Scripts (MANDATORY)
-
-> 🔴 **CRITICAL:** Each agent runs ONLY their own skill's scripts after completing work.
-
-### Agent → Script Mapping
-
-| Agent | Script | Command |
-|-------|--------|---------|
-| **frontend-specialist** | UX Audit | `python ~/.claude/skills/frontend-design/scripts/ux_audit.py .` |
-| **frontend-specialist** | A11y Check | `python ~/.claude/skills/frontend-design/scripts/accessibility_checker.py .` |
-| **backend-specialist** | API Validator | `python ~/.claude/skills/api-patterns/scripts/api_validator.py .` |
-| **mobile-developer** | Mobile Audit | `python ~/.claude/skills/mobile-design/scripts/mobile_audit.py .` |
-| **database-architect** | Schema Validate | `python ~/.claude/skills/database-design/scripts/schema_validator.py .` |
-| **security-auditor** | Security Scan | `python ~/.claude/skills/vulnerability-scanner/scripts/security_scan.py .` |
-| **seo-specialist** | SEO Check | `python ~/.claude/skills/seo-fundamentals/scripts/seo_checker.py .` |
-| **seo-specialist** | GEO Check | `python ~/.claude/skills/geo-fundamentals/scripts/geo_checker.py .` |
-| **performance-optimizer** | Lighthouse | `python ~/.claude/skills/performance-profiling/scripts/lighthouse_audit.py <url>` |
-| **test-engineer** | Test Runner | `python ~/.claude/skills/testing-patterns/scripts/test_runner.py .` |
-| **test-engineer** | Playwright | `python ~/.claude/skills/webapp-testing/scripts/playwright_runner.py <url>` |
-| **Any agent** | Lint Check | `python ~/.claude/skills/lint-and-validate/scripts/lint_runner.py .` |
-| **Any agent** | Type Coverage | `python ~/.claude/skills/lint-and-validate/scripts/type_coverage.py .` |
-| **Any agent** | i18n Check | `python ~/.claude/skills/i18n-localization/scripts/i18n_checker.py .` |
-
-> ❌ **WRONG:** `test-engineer` running `ux_audit.py`
-> ✅ **CORRECT:** `frontend-specialist` running `ux_audit.py`
-
---
-
-### 🔴 Script Output Handling (READ → SUMMARIZE → ASK)
-
-**When running a validation script, you MUST:**
-
-1. **Run the script** and capture ALL output
-2. **Parse the output** - identify errors, warnings, and passes
-3. **Summarize to user** in this format:
-
-```markdown
-## Script Results: [script_name.py]
-
-### ❌ Errors Found (X items)
- [File:Line] Error description 1
- [File:Line] Error description 2
-
-### ⚠️ Warnings (Y items)
- [File:Line] Warning description
-
-### ✅ Passed (Z items)
- Check 1 passed
- Check 2 passed
-
-**Should I fix the X errors?**
-```
-
-4. **Wait for user confirmation** before fixing
-5. **After fixing** → Re-run script to confirm
-
-> 🔴 **VIOLATION:** Running script and ignoring output = FAILED task.
-> 🔴 **VIOLATION:** Auto-fixing without asking = Not allowed.
-> 🔴 **Rule:** Always READ output → SUMMARIZE → ASK → then fix.
+## 9. Smells and Heuristics
+- **Rigidity**: Hard to change.
+- **Fragility**: Breaks in many places.
+- **Immobility**: Hard to reuse.
+- **Viscosity**: Hard to do the right thing.
+- **Needless Complexity/Repetition**.

+## 🛠️ Implementation Checklist
+- [ ] Is this function smaller than 20 lines?
+- [ ] Does this function do exactly one thing?
+- [ ] Are all names searchable and intention-revealing?
+- [ ] Have I avoided comments by making the code clearer?
+- [ ] Am I passing too many arguments?
+- [ ] Is there a failing test for this change?
--- a/skills_index.json
+++ b/skills_index.json
@@ -278,6 +278,15 @@
    "risk": "unknown",
    "source": "unknown"
  },
+  {
+    "id": "antigravity-workflows",
+    "path": "skills/antigravity-workflows",
+    "category": "uncategorized",
+    "name": "antigravity-workflows",
+    "description": "Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.",
+    "risk": "none",
+    "source": "self"
+  },
  {
    "id": "api-fuzzing-bug-bounty",
    "path": "skills/api-fuzzing-bug-bounty",
@@ -1048,9 +1057,9 @@
    "path": "skills/clean-code",
    "category": "uncategorized",
    "name": "clean-code",
-    "description": "Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments",
-    "risk": "unknown",
-    "source": "unknown"
+    "description": "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functions, comments, error handling, and class design.",
+    "risk": "safe",
+    "source": "ClawForge (https://github.com/jackjin1997/ClawForge)"
  },
  {
    "id": "clerk-auth",
Author	SHA1	Message	Date
sck_0	cc2946b6d5	chore: cut v5.0.0 workflows release and maintenance updates Prepare release 5.0.0 by documenting the new Workflows foundation, bumping package metadata, refreshing release notes, and extending MAINTENANCE guidance for workflows consistency and issue-closing protocol. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-02-10 10:43:41 +01:00
sck_0	c44f0f6505	feat: add antigravity workflows playbooks and orchestration skill Introduce the first Antigravity Workflows foundation with machine-readable workflow metadata, a dedicated orchestration skill, and onboarding docs that explain when to use bundles versus workflows. This reduces multi-skill friction for common goals like SaaS MVP delivery, security audits, AI agent builds, and browser QA. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-02-10 10:36:34 +01:00
github-actions[bot]	ef994f7e5d	chore: update star history chart	2026-02-10 07:00:43 +00:00
github-actions[bot]	183c792fef	chore: update star history chart	2026-02-09 07:01:18 +00:00
Jackjin	56720c9e1b	feat: update Clean Code skill and stabilize registry (#69 ) feat: update clean-code skill and stabilize registry - Updated clean-code skill with Robert C. Martin's Clean Code principles - Fixed invalid heading format - Stabilized registry with SOURCE_DATE_EPOCH for deterministic CI builds - Included in release v4.11.0 Co-authored-by: jackjin1997 <jackjin1997@users.noreply.github.com>	2026-02-08 11:09:34 +01:00
github-actions[bot]	800dc51041	chore: sync generated registry files [ci skip]	2026-02-08 10:02:49 +00:00
sck_0	ebaa824d74	chore: release v4.11.0 - Updated CHANGELOG.md with v4.11.0 release notes - Bumped version to 4.11.0 in package.json	2026-02-08 11:02:32 +01:00
sck_0	dc6f3c51e5	feat: update clean-code skill and stabilize registry (#69 ) - Updated clean-code skill with Robert C. Martin's Clean Code principles - Refined content: naming, functions, comments, error handling, class design - Fixed invalid heading format (## ## When to Use -> ## When to Use) - Stabilized registry: use SOURCE_DATE_EPOCH for deterministic CI builds - Improved catalog sorting for cross-environment consistency - Regenerated all catalog and index files Co-authored-by: jackjin1997 <jackjin1997@users.noreply.github.com>	2026-02-08 11:02:14 +01:00
github-actions[bot]	2675db4d2f	chore: update star history chart	2026-02-08 06:44:43 +00:00
github-actions[bot]	9c4724fb71	chore: update star history chart	2026-02-07 06:38:10 +00:00
github-actions[bot]	e94d250e55	chore: sync generated registry files [ci skip]	2026-02-06 08:53:44 +00:00
sck_0	29e6cf6966	docs(readme): increase support CTA visibility	2026-02-06 09:53:27 +01:00
github-actions[bot]	6fc7543a96	chore: sync generated registry files [ci skip]	2026-02-06 08:50:37 +00:00
sck_0	b85ba3500f	docs(readme): make support section transparent and community-first	2026-02-06 09:50:22 +01:00
github-actions[bot]	4419102cc9	chore: sync generated registry files [ci skip]	2026-02-06 08:32:28 +00:00
sck_0	41cd889ebd	docs(readme): clarify curated collections and bundle usage	2026-02-06 09:32:08 +01:00
github-actions[bot]	c12f68780b	chore: sync generated registry files [ci skip]	2026-02-06 08:28:40 +00:00
sck_0	f4b23f7480	docs(bundles): refresh usage guidance and add maintainer packs	2026-02-06 09:28:25 +01:00
github-actions[bot]	4df02e8068	chore: sync generated registry files [ci skip]	2026-02-06 08:13:24 +00:00
sck_0	3c899d01f2	docs(readme): reorder sections for onboarding flow	2026-02-06 09:13:08 +01:00
github-actions[bot]	b7a64f7b3b	chore: sync generated registry files [ci skip]	2026-02-06 08:08:49 +00:00
sck_0	d556615959	docs(readme): improve quick start and add troubleshooting	2026-02-06 09:08:25 +01:00
github-actions[bot]	67a3d81894	chore: sync generated registry files [ci skip]	2026-02-06 07:59:29 +00:00
sck_0	b690d7beb2	docs(release): expand 4.10.0 notes with detailed scope	2026-02-06 08:59:13 +01:00
github-actions[bot]	03c6270dc6	chore: sync generated registry files [ci skip]	2026-02-06 07:53:06 +00:00