cfsa-antigravity 3.0.2 → 3.1.0

package/template/.codex/skills/evolve-contract/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: evolve-contract
+description: Safely evolve shared contracts with consumer discovery, migration tests, versioning checks, and downstream spec cascade validation
+parameters:
+  - name: contract
+    type: string
+    required: false
+    description: Optional contract/schema identifier to evolve
+---
+
+## Overview
+
+
+## Step-by-Step
+
+1. Load migration/testing/error-handling skills.
+2. Identify contract and classify change risk (additive/narrowing/breaking).
+3. Discover all consumers.
+4. Run API versioning check when public API consumers are affected.
+5. Write migration tests (RED first).
+6. Update contract and consumers.
+7. Validate with project commands.
+8. Run spec cascade check for BE/FE/IA references.
+9. Record decision/update notes and propose validation rerun.

package/template/.codex/skills/evolve-feature/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: evolve-feature
+description: Introduce genuinely new scope into the pipeline by classifying change type and cascading updates through downstream layers
+parameters:
+  - name: input
+    type: string
+    required: false
+    description: Optional inline description or @file source for new scope
+---
+
+## Overview
+
+
+## Step-by-Step
+
+1. Run `evolve-feature-classify`.
+2. Run `evolve-feature-cascade`.
+3. Produce evolution record and require ambiguity audit on affected layers.

package/template/.codex/skills/evolve-feature-cascade/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: evolve-feature-cascade
+description: Cascade approved evolution changes through downstream layers, assess impact, run consistency checks, and write evolution audit record
+parameters:
+  - name: entry_point
+    type: string
+    required: false
+    description: Optional explicit entry-point document override
+---
+
+## Overview
+
+
+## Step-by-Step
+
+1. Run locked-decision conflict check.
+2. Cascade updates layer-by-layer with stop/approval at each layer.
+3. Append changelog entries to modified specs.
+4. Assess implementation/phase impact.
+5. Run consistency checks.
+6. Write evolution record.
+7. Run bootstrap check for newly introduced dependencies.
+8. Call `memory_compile` to refresh the graph after downstream spec updates.
+9. Propose mandatory ambiguity-audit rerun for affected layers.

package/template/.codex/skills/evolve-feature-classify/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: evolve-feature-classify
+description: Capture and classify new scope, write entry-point updates, and determine downstream cascade scope
+parameters:
+  - name: input
+    type: string
+    required: false
+    description: Optional inline description or @file source for change request
+---
+
+## Overview
+
+
+## Step-by-Step
+
+1. Capture change request details.
+2. Classify change type (new feature / new requirement / technical constraint / scope correction).
+3. Identify entry-point document by classification.
+4. Author entry-point additions with layer-appropriate depth.
+5. Require user approval before cascading.
+6. Determine cascade layer scope based on existing downstream content.

package/template/.codex/skills/find-skills/SKILL.md

@@ -0,0 +1,145 @@
+---
+name: find-skills
+description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
+---
+
+# Find Skills
+
+This skill helps you discover and install skills from the open agent skills ecosystem.
+
+## When to Use This Skill
+
+Use this skill when the user:
+
+- Asks "how do I do X" where X might be a common task with an existing skill
+- Says "find a skill for X" or "is there a skill for X"
+- Asks "can you do X" where X is a specialized capability
+- Expresses interest in extending agent capabilities
+- Wants to search for tools, templates, or workflows
+- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
+
+
+## When Called as a Workflow Fallback
+
+Workflows that load stack-specific skills may invoke this skill as a fallback when a required skill is not installed in `.codex/skills/` and has no matching entry in `.codex/skill-library/MANIFEST.md`. In this case:
+
+1. Use the `npx skills find [skill-name]` command to search the open agent skills ecosystem for a matching skill
+2. Present the top results to the user with install commands
+3. If the user installs a skill, the workflow that triggered this fallback should be re-run from its Step 0 placeholder guard
+4. If no matching skill is found, proceed with the workflow using general knowledge — note the gap explicitly in the output so the user can create or request the skill later
+
+**Reference implementation**: `write-architecture-spec-design.md` Step 4 is the canonical example of a workflow invoking this skill as a missing-skill fallback.
+
+## What is the Skills CLI?
+
+The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
+
+**Key commands:**
+
+- `npx skills find [query]` - Search for skills interactively or by keyword
+- `npx skills add <package>` - Install a skill from GitHub or other sources
+- `npx skills check` - Check for skill updates
+- `npx skills update` - Update all installed skills
+
+**Browse skills at:** https://skills.sh/
+
+## How to Help Users Find Skills
+
+### Step 1: Understand What They Need
+
+When a user asks for help with something, identify:
+
+1. The domain (e.g., React, testing, design, deployment)
+2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
+3. Whether this is a common enough task that a skill likely exists
+
+### Step 2: Search for Skills
+
+Run the find command with a relevant query:
+
+```bash
+npx skills find [query]
+```
+
+For example:
+
+- User asks "how do I make my React app faster?" → `npx skills find react performance`
+- User asks "can you help me with PR reviews?" → `npx skills find pr review`
+- User asks "I need to create a changelog" → `npx skills find changelog`
+
+The command will return results like:
+
+```
+Install with npx skills add <owner/repo@skill>
+
+vercel-labs/agent-skills@vercel-react-best-practices
+└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
+```
+
+### Step 3: Present Options to the User
+
+When you find relevant skills, present them to the user with:
+
+1. The skill name and what it does
+2. The install command they can run
+3. A link to learn more at skills.sh
+
+Example response:
+
+```
+I found a skill that might help! The "vercel-react-best-practices" skill provides
+React and Next.js performance optimization guidelines from Vercel Engineering.
+
+To install it:
+npx skills add vercel-labs/agent-skills@vercel-react-best-practices
+
+Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
+```
+
+### Step 4: Offer to Install
+
+If the user wants to proceed, you can install the skill for them:
+
+```bash
+npx skills add <owner/repo@skill> -g -y
+```
+
+The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
+
+## Common Skill Categories
+
+When searching, consider these common categories:
+
+| Category        | Example Queries                          |
+| --------------- | ---------------------------------------- |
+| Web Development | react, nextjs, typescript, css, tailwind |
+| Testing         | testing, jest, playwright, e2e           |
+| DevOps          | deploy, docker, kubernetes, ci-cd        |
+| Documentation   | docs, readme, changelog, api-docs        |
+| Code Quality    | review, lint, refactor, best-practices   |
+| Design          | ui, ux, design-system, accessibility     |
+| Productivity    | workflow, automation, git                |
+
+## Tips for Effective Searches
+
+1. **Use specific keywords**: "react testing" is better than just "testing"
+2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
+3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
+
+## When No Skills Are Found
+
+If no relevant skills exist:
+
+1. Acknowledge that no existing skill was found
+2. Offer to help with the task directly using your general capabilities
+3. Suggest the user could create their own skill with `npx skills init`
+
+Example:
+
+```
+I searched for skills related to "xyz" but didn't find any matches.
+I can still help you with this task directly! Would you like me to proceed?
+
+If this is something you do often, you could create your own skill:
+npx skills init my-xyz-skill
+```