Imported from harikrishna8121999/antigravity-workflows (
AGENTS.md). Install upstream withnpx skills add harikrishna8121999/antigravity-workflows. Copyright stays with the author.
Agent Instructions
These instructions are for AI agents working with the Antigravity Workflows repository.
šÆ Core Philosophy
All workflows in this repository follow five core principles:
| # | Principle | What It Means |
|---|---|---|
| 1 | Stack-Agnostic | Never assume React, Next.js, or any specific stack. Detect first. |
| 2 | Question-Driven | Ask clarifying questions before implementing. |
| 3 | Progressive Disclosure | Load minimal context first, expand on demand. |
| 4 | Single Responsibility | One workflow = one task. |
| 5 | Composable | Workflows can be combined for complex tasks. |
š Key Files
| File | Purpose |
|---|---|
workflows/registry.json |
Index of all available workflows with metadata |
workflows/<category>/<name>.md |
Individual workflow files |
CONTRIBUTING.md |
Guidelines for creating new workflows |
bin/cli.js |
CLI entry point |
src/commands/ |
CLI command implementations |
šļø Workflow Format
All workflows follow this structure:
---
description: [5-10 word description]
---
# Workflow Name
Brief intro explaining the purpose.
## Guardrails
- Boundaries and constraints
- What to avoid
## Steps
### 1. Understand Context
Ask clarifying questions first.
### 2. Analyze Project
Detect stack, framework, patterns.
### 3. [Implementation Steps]
Describe WHAT to do, not exact code.
### 4. Verify
Confirm success.
## Principles
- Universal best practices
## Reference
- Links to documentation
š When Executing a Workflow
-
Always detect project stack first
- Check
package.json, config files, file patterns - Look at existing code for conventions
- Check
-
Ask questions when unclear
- Don't assume the user wants React/Next.js
- Ask about scope, features, constraints
-
Follow existing patterns
- Match the project's coding style
- Use existing utilities and components
-
Use
// turboappropriately- Only for safe, non-destructive commands
- Never for delete operations or global changes
š Workflow Categories
| Category | Workflows |
|---|---|
development |
new-project, new-component, new-api, refactor, migrate |
git |
git-commit, git-pr, git-conflict |
testing |
unit-test, e2e-test, code-review |
debugging |
debug-error, debug-log, performance |
security |
security-audit, dependency-check |
documentation |
readme, api-docs, architecture |
deployment |
deploy, docker, ci-cd |
database |
db-schema, db-migrate, db-seed |
ai-tools |
prompt-engineering, rag-pipeline, workflow-creator |
creative |
landing-page, dashboard-ui, email-template |
ā Adding a New Workflow
- Create
workflows/<category>/<name>.mdfollowing the template - Ensure it follows the Stack-Agnostic principle
- Add entry to
workflows/registry.json - Test with
/<name>in Antigravity
See CONTRIBUTING.md for detailed guidelines.