metacoding 1.5.1 → 2.0.1

package/README.md

@@ -1,552 +1,146 @@
-# `metacoding`: Guided Development Workflow for AI Assistants
+# `metacoding`: Workflow Skill for Coding Agents
 
 [![Version](https://img.shields.io/npm/v/metacoding.svg)](https://www.npmjs.com/package/metacoding)
 [![License](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
-[![GitHub Copilot](https://img.shields.io/badge/GitHub%20Copilot-Compatible-brightgreen.svg)](https://github.com/features/copilot)
-[![Claude Code](https://img.shields.io/badge/Claude%20Code-Compatible-brightgreen.svg)](https://claude.ai/)
-[![Cursor IDE](https://img.shields.io/badge/Cursor%20IDE-Compatible-brightgreen.svg)](https://www.cursor.com/)
-[![Gemini](https://img.shields.io/badge/Gemini%20Code%20Assist-Compatible-brightgreen.svg)](https://cloud.google.com/gemini)
 
-Transform your development experience with AI-guided coding standards, structured workflows, and quality practices that help you build better software from day one. Works with **GitHub Copilot**, **Claude Code**, **Codex/OpenAI**, **Gemini Code Assist**, and **Cursor IDE**.
+`metacoding` packages a cross-agent workflow skill that enforces disciplined delivery for modern coding agents. Instead of generating editor-specific instruction files, it installs vendor-specific skills for Codex, Claude Code, or Antigravity from one shared workflow bundle.
 
-## Table of Contents
+## What It Installs
 
-- [🎯 What is `metacoding`?](#-what-is-metacoding)
-- [💬 How to Use `metacoding` with AI Assistants](#-how-to-use-metacoding-with-ai-assistants)
-- [🛠 Installation Guide](#-installation-guide)
-- [📦 Using the `metacoding` CLI](#-using-the-metacoding-cli)
-- [🆘 Getting Help](#-getting-help)
-- [🤝 Contributing](#-contributing)
-- [📄 License](#-license)
+Running `metacoding init` now asks which coding agent you use:
 
-## 🎯 What is `metacoding`?
+- `Codex`
+- `Claude Code`
+- `Antigravity`
 
-`metacoding` is a **guided development methodology** that uses AI assistant custom instruction capabilities to help developers at any level follow established best practices. Works seamlessly with **GitHub Copilot** (VS Code), **Claude Code** (Terminal/IDE), **Codex/OpenAI** (Terminal), **Gemini Code Assist** (VS Code/IntelliJ), and **Cursor IDE**. Instead of just getting code suggestions, you get:
+You can also pass `--vendor codex`, `--vendor claude-code`, or `--vendor antigravity`.
+For mixed-agent teams, you can use `--vendor all` to install all workspace-scoped variants.
 
-- **Structured workflows** that guide you through proven development practices
-- **Quality standards** that help you avoid common mistakes
-- **Test-driven development** that's encouraged and guided step-by-step
-- **Documentation guidance** that keeps your projects maintainable
-- **Multi-assistant support** with a single canonical workflow adapted for each AI assistant
+The installed entrypoint depends on that choice:
 
-## 💬 How to Use `metacoding` with AI Assistants
-
-`metacoding` transforms AI assistants (GitHub Copilot, Claude Code, Codex/OpenAI, Gemini Code Assist, or Cursor IDE) into autonomous development partners that execute structured workflows. You specify what you want built, and your AI assistant independently follows a disciplined 7-step process that ensures quality, maintainability, and thorough testing. Your role is to provide clear requirements, validate results, and approve each stage before proceeding.
-
-### The `metacoding` 7-Step Development Workflow
-
-Every development task follows this mandatory workflow to ensure quality and consistency:
-
-#### Step 1: Describe Your Feature or Task
-
-Be specific about what you want to build. Copilot will automatically follow the workflow and create a comprehensive plan for your approval.
-
-- **Be specific about requirements**: Clearly describe the feature, functionality, or problem to solve
-- **Provide context**: Include relevant constraints, user needs, or business requirements
-- **Review Copilot's plan**: Copilot will automatically create an implementation outline following workflow standards
-- **Approve or refine**: Confirm the plan meets your needs or request adjustments
-- **Example prompt**: _"I want to add user authentication to my web app. Users should be able to register with email/password, login securely, logout, and have password reset functionality. The system should handle validation errors gracefully."_
-
-#### Step 2: Verify Task Documentation
-
-Copilot will automatically document tasks following the workflow. Your role is to review and approve the breakdown.
-
-- **Review task breakdown**: Copilot will add tasks to your project list and create subtasks
-- **Verify scope boundaries**: Ensure what's included and excluded is clear and appropriate
-- **Approve documentation**: Confirm the task structure before Copilot proceeds to testing
-- **Example verification**: _"Review the authentication tasks you've added. Does this scope make sense for our current iteration?"_
-
-#### Step 3: Validate Test Strategy
-
-Copilot will automatically document test cases before implementation. You verify the testing approach meets your quality standards.
-
-- **Review test documentation**: Copilot will document all test scenarios following TDD principles
-- **Verify coverage**: Ensure happy paths, error scenarios, and edge cases are included
-- **Approve test approach**: Confirm the testing strategy before Copilot implements failing tests
-- **Example verification**: _"Check the test cases you've documented for authentication. Are we covering all the important scenarios?"_
-
-#### Step 4: Monitor Implementation Progress
-
-Copilot will implement functionality to make tests pass. You track progress and validate the working solution.
-
-- **Track implementation**: Copilot will write minimal code following TDD red-green-refactor cycle
-- **Verify test results**: Copilot will run tests and report results - you confirm they're passing
-- **Test functionality yourself**: Validate that the implementation works as expected in practice
-- **Example check**: _"Show me the test results and let me verify the authentication is working correctly."_
-
-#### Step 5: Review Documentation Updates
-
-Copilot will automatically update all documentation. You verify completeness and accuracy of updates.
-
-- **Review documentation changes**: Copilot will update README, API docs, and code comments
-- **Verify task status updates**: Confirm completed work is properly marked in project management docs
-- **Approve changelog entries**: Review user-facing changes recorded in changelog
-- **Example review**: _"Show me what documentation you've updated for the authentication feature. Let me verify it's accurate and complete."_
-
-#### Step 6: Approve Version Control
-
-Copilot will create proper commits following conventional standards. You approve the commit structure and messages.
-
-- **Review commit structure**: Copilot will prepare atomic commits with conventional messages
-- **Verify file inclusion**: Ensure all related files (code, tests, docs) are included together
-- **Approve commits**: Confirm the commit represents complete, working functionality
-- **Example approval**: _"Show me the commit you've prepared for the authentication feature. Does it include everything we've built?"_
-
-#### Step 7: Confirm Workflow Completion
-
-Copilot will verify workflow completion automatically. You perform final validation before moving to new work.
-
-- **Review completion checklist**: Copilot will verify all tests pass, documentation is updated, and changes are committed
-- **Confirm clean repository state**: Verify temporary files are cleaned up and repository is organized
-- **Approve workflow completion**: Give explicit approval before starting any new tasks
-- **Example confirmation**: _"Confirm our authentication workflow is complete and we're ready for the next feature."_
-
-### Workflow Enforcement and Quality Assurance
-
-`metacoding` enforces strict quality practices:
-
-- **Documentation-First Principle**: No coding begins until documentation is complete
-- **Single-Task Focus**: One change at a time - never mix unrelated tasks
-- **Confirmation Gates**: User approval required before proceeding with implementation
-- **Test Coverage**: Comprehensive testing mandatory for all functionality
-- **Repository Hygiene**: Clean up temporary files and maintain organization
-
-### Effective Workflow Prompts
-
-**Starting a new feature:**
-_"Let's implement feature X following the 7-step workflow. First, help me understand requirements and create an implementation plan."_
-
-**During development:**
-_"We're on step 3 of our workflow. Document the test cases for this component before implementing tests."_
-
-**Scope management:**
-_"I want to add feature Y, but we're working on feature X. Add Y to the task list and let's complete X first."_
-
-**Quality check:**
-_"Review our current workflow step. Are we ready to proceed, or do we need to complete documentation first?"_
-
-### Automatic Context Application
-
-GitHub Copilot automatically applies relevant instruction files based on your work:
-
-- **Test files** → Applies test-driven development and quality standards
-- **Documentation** → Enforces documentation architecture and maintenance guidelines
-- **Code files** → Provides code review criteria and quality standards
-- **Release files** → Guides version management and release procedures
-
-### Manual Instruction Reference
-
-For specific guidance, explicitly reference instruction files:
-
-- _"Use the 7-step workflow to implement user registration"_
-- _"Apply code review guidelines to check this function"_
-- _"Follow test documentation standards to update our test cases"_
-- _"Use release instructions to prepare version 2.1.0"_
-
-### Workflow Violations and Corrections
-
-If you try to skip steps or mix tasks, Copilot will redirect you:
-
-- **Skipping documentation**: _"Let's document this task first before implementing"_
-- **Task switching**: _"I've added that to the task list. Let's complete our current workflow first"_
-- **Missing tests**: _"We need to document and implement tests before the production code"_
-
-### Best Practices for Workflow Success
-
-1. **Start small**: Begin with simple features to practice the workflow
-2. **Stay focused**: Complete one task fully before starting another
-3. **Trust the process**: The workflow prevents technical debt and quality issues
-4. **Attach context**: Include task lists, documentation, and related files in prompts
-5. **Confirm understanding**: Always confirm plans before implementation begins
-
-The `metacoding` workflow transforms chaotic development into a structured, quality-driven process that scales from personal projects to enterprise teams.
-
-## 🛠 Installation Guide
-
-### Prerequisites
-
-Before installing `metacoding`, choose your AI development setup:
-
-#### Supported AI Assistants
-
-- **GitHub Copilot** (VS Code) - Uses `.github/copilot-instructions.md`
-- **Claude Code** (Terminal or IDE) - Uses `CLAUDE.md`
-- **Codex/OpenAI** (Terminal) - Uses `AGENTS.md`
-- **Gemini Code Assist** (VS Code/IntelliJ) - Uses `GEMINI.md`
-- **Cursor IDE** - Uses `.cursor/rules/*.mdc` files
-
-#### General Requirements
-
-1. **Node.js** (version 16 or higher) for the CLI tool
-2. **Your chosen AI assistant** configured and ready to use
-3. **Git repository** (recommended but not required)
-
-### Quick Setup (Recommended)
-
-The easiest way to get started with `metacoding` is using our npm package:
-
-1. **Install globally:** `npm install -g metacoding`
-2. **Navigate to your project:** `cd your-project`
-3. **Initialize `metacoding`:** `metacoding init`
-4. **Follow the interactive prompts** to choose your AI setup and you're done!
-
-#### Init options
-
-**Basic usage:**
-
-- `metacoding init` - Interactive setup with environment, IDE, and assistant selection
-- `metacoding init --template react` - Use React template with interactive setup
-- `metacoding init --template node` - Use Node.js template with interactive setup
-- `metacoding init --template javascript` - Use JavaScript template with interactive setup
-- `metacoding init --template python` - Use Python template with interactive setup
-- `metacoding init --force` - Overwrite existing files
-
-**Multi-assistant setup (new in v1.5.0):**
-
-- `metacoding init --environment ide --ide vscode --assistants copilot` - VS Code with GitHub Copilot only
-- `metacoding init --environment ide --ide vscode --assistants all` - VS Code with all compatible assistants
-- `metacoding init --environment terminal --assistants claude` - Terminal setup for Claude Code
-- `metacoding init --environment terminal --assistants all` - Terminal with Claude, Codex, and Gemini
-- `metacoding init --environment ide --ide intellij --assistants gemini` - IntelliJ with Gemini Code Assist
-
-**Legacy direct setup (backward compatible):**
-
-- `metacoding init --vscode` - Set up for VS Code + GitHub Copilot (legacy flag)
-- `metacoding init --cursor` - Set up for Cursor IDE (legacy flag)
-- `metacoding init --cursor --template react` - Cursor setup with React template
-
-#### Post-Installation Configuration
-
-**For GitHub Copilot (VS Code):**
-The CLI automatically configures VS Code settings for custom instructions. If you need to configure manually, add these settings to your VS Code settings.json:
-
-```json
-{
-  "github.copilot.chat.codeGeneration.useInstructionFiles": true,
-  "chat.promptFiles": true
-}
+```text
+Codex:       .codex/skills/metacoding-workflow/SKILL.md
+Claude Code: .claude/agents/metacoding-workflow.md
+Antigravity: .agents/skills/metacoding-workflow/SKILL.md
 ```
 
-**For Claude Code:**
-Use the generated `CLAUDE.md` file as project instructions. In your terminal, run:
-
-```bash
-claude --project-instructions CLAUDE.md
+The support bundle is installed alongside the entrypoint. The shared content includes:
+
+```text
+references/
+  project-context.md
+  workflow-rules.md
+  platform-adaptation.md
+  typescript.md
+  javascript.md
+  node.md
+  react.md
+  python.md
+assets/templates/
+  task-entry.md
+  test-plan.md
+  repeated-task-checklist.md
+  changelog-entry.md
+  project-context.md
 ```
 
-**For Codex/OpenAI:**
-Configure your OpenAI client to use `AGENTS.md` as the system message:
-
-```bash
-# Example with OpenAI CLI
-openai api chat.completions.create --system-file AGENTS.md
+For Codex, the project install looks like:
+
+```text
+.codex/skills/metacoding-workflow/
+├── SKILL.md
+├── agents/openai.yaml
+├── references/
+│   ├── project-context.md
+│   ├── workflow-rules.md
+│   ├── platform-adaptation.md
+│   ├── typescript.md
+│   ├── javascript.md
+│   ├── node.md
+│   ├── react.md
+│   └── python.md
+└── assets/templates/
+    ├── task-entry.md
+    ├── test-plan.md
+    ├── repeated-task-checklist.md
+    ├── changelog-entry.md
+    └── project-context.md
 ```
 
-**For Gemini Code Assist:**
-Gemini Code Assist in VS Code/IntelliJ automatically discovers and uses `GEMINI.md` as a style guide. No additional configuration needed!
-
-**For Cursor IDE:**
-No additional configuration needed! Cursor automatically detects and uses `.cursor/rules/*.mdc` files.
-
-### File Structure by AI Setup
-
-**GitHub Copilot setup (VS Code):**
+The installed skill preserves the original `metacoding` workflow intent:
 
-```
-my-awesome-project/
-├── .github/
-│   ├── copilot-instructions.md
-│   └── instructions/
-│       ├── test-runner.instructions.md
-│       ├── release.instructions.md
-│       ├── docs-update.instructions.md
-│       └── code-review.instructions.md
-├── _meta/
-│   └── project-task-list.md
-└── test/
-    └── test-documentation.md
-```
-
-**Claude Code setup:**
+1. Ground in the repo before asking questions.
+2. Capture scope before changing code.
+3. Define test intent before implementation.
+4. Execute one bounded task at a time.
+5. Verify with tests and direct checks.
+6. Update docs or status artifacts that materially changed.
+7. Close with a VCS handoff or completion confirmation.
 
-```
-my-awesome-project/
-├── CLAUDE.md                    # Project instructions for Claude Code
-├── _meta/
-│   └── project-task-list.md
-└── test/
-    └── test-documentation.md
-```
+## CLI
 
-**Codex/OpenAI setup:**
+### Install
 
-```
-my-awesome-project/
-├── AGENTS.md                    # System message for Codex/OpenAI
-├── _meta/
-│   └── project-task-list.md
-└── test/
-    └── test-documentation.md
+```bash
+npm install -g metacoding
+cd your-project
+metacoding init
 ```
 
-**Gemini Code Assist setup:**
-
-```
-my-awesome-project/
-├── GEMINI.md                    # Style guide for Gemini Code Assist
-├── _meta/
-│   └── project-task-list.md
-└── test/
-    └── test-documentation.md
-```
+`init` remains interactive for project metadata such as project name, description, and tech stack. Use `--vendor` and `--template` to preselect those parts of the setup flow.
 
-**Cursor IDE setup:**
+Common options:
 
-```
-my-awesome-project/
-├── .cursor/
-│   └── rules/
-│       ├── workflow.mdc
-│       ├── test-runner.mdc
-│       ├── release.mdc
-│       ├── docs-update.mdc
-│       └── code-review.mdc
-├── _meta/
-│   └── project-task-list.md
-└── test/
-    └── test-documentation.md
-```
+- `metacoding init --vendor codex`
+- `metacoding init --vendor claude-code`
+- `metacoding init --vendor antigravity`
+- `metacoding init --vendor all`
+- `metacoding init --template react`
+- `metacoding init --template typescript`
+- `metacoding init --template node`
+- `metacoding init --template javascript`
+- `metacoding init --template python`
+- `metacoding init --force`
 
-**Multi-assistant setup (all assistants):**
+### Sync or Validate
 
+```bash
+metacoding update
+metacoding update --dry-run
+metacoding update --dry-run --strict
+metacoding update --force
 ```
-my-awesome-project/
-├── .github/
-│   ├── copilot-instructions.md
-│   └── instructions/
-│       └── [instruction files]
-├── CLAUDE.md
-├── AGENTS.md
-├── GEMINI.md
-├── _meta/
-│   └── project-task-list.md
-└── test/
-    └── test-documentation.md
-```
-
-│ └── code-review.mdc
-
-````
-
-### Test Your Setup
-
-#### For GitHub Copilot (VS Code):
-
-1. **Restart VS Code** to ensure all settings are applied
-2. **Create a new file** in your project (e.g., `test.js` or `main.py`)
-3. **Open GitHub Copilot Chat:**
-   - Press `Ctrl+Shift+P` (Windows/Linux) or `Cmd+Shift+P` (Mac)
-   - Type "GitHub Copilot: Open Chat"
-   - Press Enter
-4. **Test the setup:**
-   - Ask: "What is the development workflow for this project?"
-   - Copilot should reference your custom instructions and provide project-specific guidance!
-
-#### For Claude Code:
-
-1. **Run Claude with project instructions:**
-   ```bash
-   claude --project-instructions CLAUDE.md
-````
-
-2. **Test the setup:**
-   - Ask: "What is the development workflow for this project?"
-   - Claude should reference the canonical 7-step workflow from your CLAUDE.md file!
-
-#### For Codex/OpenAI:
-
-1. **Configure your OpenAI client** to use AGENTS.md as system message
-2. **Test the setup:**
-   - Ask: "What is the development workflow for this project?"
-   - The assistant should follow the structured workflow from your AGENTS.md file!
-
-#### For Gemini Code Assist:
-
-1. **Open your project** in VS Code or IntelliJ
-2. **Gemini automatically discovers** GEMINI.md as a style guide
-3. **Test the setup:**
-   - Ask: "What is the development workflow for this project?"
-   - Gemini should reference your configuration rules from GEMINI.md!
-
-#### For Cursor IDE:
-
-1. **Open your project** in Cursor IDE
-2. **Cursor automatically detects** .cursor/rules/\*.mdc files
-3. **Test the setup:**
-   - Open Cursor Chat (Cmd/Ctrl + L)
-   - Ask: "What is the development workflow for this project?"
-   - Cursor should reference your workflow rules!
-
-#### For Cursor IDE:
-
-1. **Open your project in Cursor IDE**
-2. **Verify rules are loaded:**
-   - Check that `workflow.cursorrules` appears in the Cursor IDE interface
-   - Look for rule indicators showing active patterns
-3. **Test the setup:**
-   - In Cursor chat, ask: "What is the development workflow for this project?"
-   - Cursor should reference your workflow rules and provide project-specific guidance!
-
-## ✅ You're Ready to Go!
-
-## 📦 Using the `metacoding` CLI
-
-Once installed, you can use these commands:
-
-### `metacoding init`
-
-Initialize metacoding in your current project:
-
-**Interactive setup:**
 
-- `metacoding init` - Interactive setup with environment, IDE, and assistant selection
-- `metacoding init --template react` - Initialize with React template (interactive setup)
-- `metacoding init --template node` - Initialize with Node.js template (interactive setup)
-- `metacoding init --template javascript` - Initialize with JavaScript template (interactive setup)
-- `metacoding init --template python` - Initialize with Python template (interactive setup)
-- `metacoding init --force` - Overwrite existing files without confirmation
+- `update` syncs the installed skill with the packaged version.
+- `update --vendor <vendor>` syncs or validates only one installed vendor variant.
+- `update --vendor all` syncs or validates all installed vendor variants explicitly.
+- `update --dry-run` validates the installed skill without changing files.
+- `update --force` overwrites local edits inside the installed skill directory.
 
-**Multi-assistant setup (v1.5.0+):**
+## Using the Skill
 
-- `metacoding init --environment ide --ide vscode --assistants all` - VS Code with all compatible assistants
-- `metacoding init --environment terminal --assistants claude` - Terminal setup for Claude Code
-- `metacoding init --environment ide --ide intellij --assistants gemini` - IntelliJ with Gemini Code Assist
+After installation, point your coding agent at the installed vendor entrypoint or ask it to use the `metacoding-workflow` skill/subagent for the next task.
 
-**Legacy direct setup (backward compatible):**
+The skill will:
 
-- `metacoding init --vscode` - Set up for VS Code + GitHub Copilot (legacy flag)
-- `metacoding init --cursor` - Set up for Cursor IDE (legacy flag)
-- `metacoding init --vscode --template react` - VS Code setup with React template (legacy)
-- `metacoding init --cursor --template javascript` - Cursor setup with JavaScript template (legacy)
+- inspect the repo before asking clarifying questions
+- keep work scoped to one bounded task
+- push test intent ahead of production edits
+- fall back to bundled templates when the repo lacks workflow artifacts
+- produce a commit-ready handoff when git actions are unavailable or out of scope
 
-### `metacoding update`
+## Migration Note
 
-Update your `metacoding` setup to the latest version:
+This package no longer treats GitHub Copilot or Cursor instruction files as the primary product. The canonical content lives under `skills/metacoding-workflow/`, and the CLI now renders vendor-specific installs for Codex, Claude Code, or Antigravity from that shared bundle.
 
-- `metacoding update` - Update to latest version
-- `metacoding update --dry-run` - Validate current setup without making changes
-- `metacoding update --dry-run --strict` - Strict validation rules
-- `metacoding update --backup` - Create backup before updating
+## Development
 
-### Help and Version
-
-- `metacoding --help` - Show all commands and examples
-- `metacoding --version` - Show version number
-
-## 🆘 Getting Help
-
-### Common Questions
-
-**Q: Do I need to be an experienced developer?**
-A: No! `metacoding` provides guidance and structure to help developers at any level adopt proven practices and improve their skills.
-
-**Q: Which AI assistant should I choose?**
-A: Choose based on your workflow and preferences:
-
-- **GitHub Copilot**: Best if you use VS Code and want deep IDE integration
-- **Claude Code**: Great for terminal-based workflows and complex reasoning
-- **Codex/OpenAI**: Flexible for custom integrations and API usage
-- **Gemini Code Assist**: Excellent for Google Cloud developers using VS Code/IntelliJ
-- **Cursor IDE**: Best for AI-first development with built-in AI features
-- **Multiple assistants**: You can configure multiple assistants in one project!
-
-**Q: What if I don't have an AI assistant subscription?**
-A: You'll need access to at least one of the supported AI assistants. Many offer free tiers or trials:
-
-- GitHub Copilot: Free for students through GitHub Education
-- Claude Code: Available with Claude Pro subscription
-- OpenAI Codex: Available through OpenAI API
-- Gemini Code Assist: Available for Google Cloud users
-- Cursor IDE: Free tier available, Pro subscription for advanced features
-
-**Q: Can I switch between VS Code and Cursor later?**
-A: Yes! Run `metacoding init --vscode` or `metacoding init --cursor` to switch your setup. The CLI will install the appropriate files for your chosen AI assistant.
-
-**Q: Can I use this without the CLI tool?**
-A: The CLI tool provides the easiest setup experience. For manual setup, you can download instruction files from our GitHub repository.
-
-**Q: Will this work with my preferred programming language?**
-A: Yes! The general `metacoding` template works with any language supported by your AI assistant.
-
-**Q: Can I customize the workflow for my team's needs?**
-A: Absolutely! All instruction files can be modified to match your specific requirements.
-
-**Q: Does this replace learning to code?**
-A: Nope. But it's totally up to you!.
-
-**Q: What VS Code settings are required?**
-A: For VS Code + GitHub Copilot, you need `github.copilot.chat.codeGeneration.useInstructionFiles: true` and `chat.promptFiles: true`. The CLI configures these automatically.
-
-**Q: Does Cursor IDE require special settings?**
-A: No additional settings needed! Cursor automatically detects `workflow.cursorrules` and `.cursor/rules/*.mdc` files.
-
-## Troubleshooting
-
-**Installation Issues:**
-
-- Make sure Node.js (version 16+) is installed: `node --version`
-- Verify npm is working: `npm --version`
-- Try clearing npm cache: `npm cache clean --force`
-
-**VS Code + GitHub Copilot Issues:**
-
-- Make sure you've restarted VS Code after installation
-- Verify your GitHub Copilot subscription is active
-- Check that the instruction files are in the correct `.github/` folder
-- Ensure VS Code settings include the required custom instruction settings
-- Try manually referencing instructions in GitHub Copilot
-
-**Cursor IDE Issues:**
-
-- Verify `workflow.cursorrules` file exists in your project root
-- Check that `.cursor/rules/*.mdc` files are present
-- Ensure Cursor IDE is updated to the latest version
-- Look for rule indicators in Cursor IDE interface showing active patterns
-- Try asking Cursor: "What rules are active for this project?"
-
-**Instructions not applying automatically:**
-
-- Ensure file names match exactly (including extensions)
-- Verify the folder structure is correct for your AI setup
-- Run `metacoding update --dry-run` to validate your setup
-- For VS Code: Check `.github/instructions/` folder structure
-- For Cursor: Check `workflow.cursorrules` and `.cursor/rules/` files
-
-**CLI Command Issues:**
-
-- Ensure `metacoding` is installed globally: `npm list -g metacoding`
-- Try reinstalling: `npm uninstall -g metacoding && npm install -g metacoding`
-- Check PATH configuration if command not found
-
-## Official Resources
-
-Learn more about GitHub Copilot custom instructions:
-
-- **[VS Code Custom Instructions Guide](https://code.visualstudio.com/blogs/2025/03/26/custom-instructions)** - **Official comprehensive guide** from the VS Code team on custom instructions
-- **[GitHub Copilot Documentation](https://docs.github.com/en/copilot/using-github-copilot/best-practices-for-using-github-copilot)** - Official GitHub Copilot best practices
-- **[VS Code Copilot Customization](https://code.visualstudio.com/docs/copilot/copilot-customization)** - Technical documentation for advanced customization
-
-## 🤝 Contributing
-
-We welcome contributions to make `metacoding` even better! Whether you have:
-
-- Improvements to existing workflows
-- New instruction patterns for specific technologies
-- Documentation enhancements
-- Bug fixes or clarifications
-
-Feel free to open an issue or submit a pull request.
+```bash
+npm test
+npm run build
+```
 
-## 📄 License
+## License
 
-This project is open source and available under the [MIT License](https://opensource.org/licenses/MIT). Use it freely in personal or commercial projects.
+MIT
+For Antigravity, the CLI currently installs the documented workspace-scoped variant under `.agents/skills/`. It does not yet install the global variant under `~/.gemini/antigravity/skills/`.

package/lib/cli.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":"AAUA,wBAAsB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC,CAsF1C"}
+{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":"AAUA,wBAAsB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC,CAwF1C"}