antigravity-ai-kit 2.1.0 → 3.0.1

package/.agent/workflows/deploy.md

@@ -1,144 +1,195 @@
----
-description: Production deployment with pre-flight checks, execution, and verification.
----
-
-# /deploy - Production Deployment
-
-$ARGUMENTS
-
----
-
-## Sub-commands
-
-```
-/deploy            - Interactive deployment wizard
-/deploy check      - Run pre-deployment checks only
-/deploy preview    - Deploy to preview/staging
-/deploy production - Deploy to production
-/deploy rollback   - Rollback to previous version
-```
-
----
-
-## Pre-Deployment Checklist
-
-```markdown
-## 🚀 Pre-Deploy Checklist
-
-### Code Quality
-
-- [ ] No TypeScript errors (`npx tsc --noEmit`)
-- [ ] ESLint passing (`npx eslint .`)
-- [ ] All tests passing (`npm test`)
-
-### Security
-
-- [ ] No hardcoded secrets
-- [ ] Environment variables documented
-- [ ] Dependencies audited (`npm audit`)
-
-### Performance
-
-- [ ] Bundle size acceptable
-- [ ] No console.log statements
-- [ ] Images optimized
-
-### Ready to deploy? (y/n)
-```
-
----
-
-## Deployment Flow
-
-```
-/deploy
-    │
-    ▼
-Pre-flight checks
-    │
-    Pass? ──No──► Fix issues
-    │
-   Yes
-    │
-    ▼
-Build application
-    │
-    ▼
-Deploy to platform
-    │
-    ▼
-Health check & verify
-    │
-    ▼
-✅ Complete
-```
-
----
-
-## Output Format
-
-### Successful Deploy
-
-```markdown
-## 🚀 Deployment Complete
-
-### Summary
-
-- **Version:** v1.2.3
-- **Environment:** production
-- **Duration:** 47 seconds
-- **Platform:** Vercel
-
-### URLs
-
-- 🌐 Production: https://app.example.com
-- 📊 Dashboard: https://vercel.com/project
-
-### Health Check
-
-✅ API responding (200 OK)
-✅ Database connected
-✅ All services healthy
-```
-
-### Failed Deploy
-
-```markdown
-## ❌ Deployment Failed
-
-### Error
-
-[Error description]
-
-### Resolution
-
-1. [Fix steps]
-2. [Verification]
-3. Try `/deploy` again
-
-### Rollback Available
-
-Run `/deploy rollback` if needed.
-```
-
----
-
-## Platform Support
-
-| Platform | Command         | Auto-detect |
-| -------- | --------------- | ----------- |
-| Vercel   | `vercel --prod` | Next.js     |
-| Railway  | `railway up`    | NestJS      |
-| Expo EAS | `eas build`     | Mobile      |
-
----
-
-## Examples
-
-```
-/deploy
-/deploy check
-/deploy preview
-/deploy production
-/deploy rollback
-```
+---
+description: Production deployment with pre-flight checks, execution, and verification.
+version: 2.1.0
+sdlc-phase: ship
+skills: [deployment-procedures]
+commit-types: [chore, fix]
+---
+
+# /deploy — Production Deployment
+
+> **Trigger**: `/deploy [sub-command]`
+> **Lifecycle**: Ship — after `/review` gate passes
+
+> [!CAUTION]
+> Deployment impacts production users and consumes platform credits. Every push to `production` triggers builds on hosting platforms (Vercel, Railway, etc.). Never deploy untested code. Always have a rollback plan before deploying.
+
+> [!TIP]
+> This workflow leverages the **deployment-procedures** skill. Read `.agent/skills/deployment-procedures/SKILL.md` for extended guidance.
+
+---
+
+## Critical Rules
+
+1. **Rollback plan required** — never deploy without a documented rollback strategy
+2. **No test deploys to production** — use preview/staging environments for testing
+3. **Cost-awareness** — batch deployments; avoid unnecessary builds that waste credits
+4. **Pre-flight must pass** — all quality gates must pass before deployment
+5. **Health check mandatory** — verify the deployment is healthy before marking complete
+6. **No secrets in logs** — ensure deployment logs don't expose sensitive data
+
+---
+
+## Scope Filter
+
+Only deploy when changes affect **deployed artifacts**:
+
+| Change Type | Affects Production? | Deploy? |
+| :-------------------------- | :------------------ | :------ |
+| `apps/api/**`, `apps/web/**` | ✅ Yes | ✅ Yes |
+| `docker/**`, `railway.toml` | ✅ Yes (infra) | ✅ Yes |
+| `docs/**`, `*.md` | ❌ No | ❌ Never |
+| `.agent/**`, `.vscode/**` | ❌ No | ❌ Never |
+| `.github/**` | ⚠️ CI only | ⚠️ Case-by-case |
+| `packages/shared/**` | ⚠️ If consumed | ⚠️ Case-by-case |
+
+---
+
+## Argument Parsing
+
+| Command | Action |
+| :-------------------- | :----------------------------------------------- |
+| `/deploy` | Interactive deployment wizard |
+| `/deploy check` | Run pre-flight checks only |
+| `/deploy preview` | Deploy to preview/staging environment |
+| `/deploy production` | Deploy to production |
+| `/deploy rollback` | Rollback to previous version |
+
+---
+
+## Steps
+
+// turbo
+1. **Pre-Flight Checks**
+   - Code quality: `npx tsc --noEmit`, `npx eslint .` (or equivalent)
+   - Tests: `npm test` (or equivalent)
+   - Security: `npm audit`, no hardcoded secrets
+   - Build: `npm run build` succeeds
+   - Environment: all required variables documented and set
+
+// turbo
+2. **Scope Verification**
+   - Check which files changed (`git diff --stat`)
+   - Apply Scope Filter — abort if changes are docs/config-only
+   - Confirm deployment is production-impacting
+
+3. **Rollback Plan**
+   - Document current production version/commit
+   - Verify rollback command is available and tested
+   - Confirm database migration reversibility (if applicable)
+
+4. **Deploy**
+   - Build the application
+   - Deploy to target platform
+   - Monitor deployment progress
+
+// turbo
+5. **Health Check & Verify**
+   - API responding (HTTP 200)
+   - Database connected
+   - All critical services healthy
+   - No error spikes in monitoring
+
+6. **Post-Deploy**
+   - Document deployed version and commit SHA
+   - Update status tracking
+   - Notify stakeholders if applicable
+
+---
+
+## Output Template
+
+### Successful Deploy
+
+```markdown
+## 🚀 Deployment Complete
+
+### Summary
+
+- **Version**: [commit SHA or tag]
+- **Environment**: production | preview
+- **Duration**: [time]
+- **Platform**: [Vercel | Railway | EAS]
+
+### Health Check
+
+✅ API responding (200 OK)
+✅ Database connected
+✅ All services healthy
+
+### Rollback
+
+If issues arise: `/deploy rollback` to [previous version]
+
+After deploy: proceed to `/status` for monitoring.
+```
+
+### Failed Deploy
+
+```markdown
+## ❌ Deployment Failed
+
+### Error
+
+[Error description and logs]
+
+### Resolution
+
+1. [Fix steps]
+2. Run `/deploy check` to re-validate
+3. Retry `/deploy production`
+
+### Rollback Available
+
+Run `/deploy rollback` to restore [previous version].
+```
+
+---
+
+## Platform Support
+
+| Platform | Command | Auto-detect |
+| :------- | :-------------- | :---------- |
+| Vercel | `vercel --prod` | Next.js |
+| Railway | `railway up` | NestJS, API |
+| Expo EAS | `eas build` | React Native |
+
+---
+
+## Governance
+
+**PROHIBITED:**
+- Deploying code that hasn't passed `/review` quality gates
+- Using production for testing — use preview environments
+- Deploying docs-only or config-only changes to production
+- Skipping the rollback plan
+- Deploying without health check verification
+- Skipping failed steps · proceeding without resolution
+
+**REQUIRED:**
+- Pre-flight checks passing before any deployment
+- Scope verification using the Production-Impact Filter
+- Rollback plan documented before deploying
+- Health check after every deployment
+- Cost-conscious deployment batching
+
+---
+
+## Completion Criteria
+
+- [ ] Pre-flight checks pass (lint, type-check, tests, security, build)
+- [ ] Scope Filter confirms production-impacting changes
+- [ ] Rollback plan is documented
+- [ ] Deployment completes without errors
+- [ ] Health check passes (API, database, services)
+- [ ] Deployed version is documented
+- [ ] After deploy: proceed to `/status` for monitoring
+
+---
+
+## Related Resources
+
+- **Previous**: `/review` (quality gates must pass before deployment)
+- **Next**: `/status` (post-deploy monitoring)
+- **Skill**: `.agent/skills/deployment-procedures/SKILL.md`
+- **Global Rule**: Production Merge Discipline (see global rules)

package/.agent/workflows/enhance.md

@@ -1,65 +1,157 @@
----
-description: Add or update features in existing application. Iterative development.
----
-
-# /enhance - Update Application
-
-$ARGUMENTS
-
----
-
-## Task
-
-Add features or make updates to an existing application.
-
-### Steps
-
-1. **Understand Current State**
-   - Explore project structure
-   - Understand existing features, tech stack
-
-2. **Plan Changes**
-   - Determine what will be added/changed
-   - Detect affected files
-   - Check dependencies
-
-3. **Present Plan** (for major changes)
-
-   ```
-   "To add admin panel:
-   - I'll create 15 new files
-   - Update 8 files
-   - Takes ~10 minutes
-
-   Should I start?"
-   ```
-
-4. **Apply Changes**
-   - Call relevant agents
-   - Make changes
-   - Test
-
-5. **Verify**
-   - Run tests
-   - Check build
-
----
-
-## Examples
-
-```
-/enhance add dark mode
-/enhance build admin panel
-/enhance integrate payment system
-/enhance add search feature
-/enhance edit profile page
-/enhance make responsive
-```
-
----
-
-## Caution
-
-- **Get approval** for major changes
-- **Warn on conflicts** (e.g., "use Firebase" when project uses PostgreSQL)
-- **Preserve existing** functionality — don't break what works
+---
+description: Add or update features in existing application. Iterative development.
+version: 2.1.0
+sdlc-phase: build
+skills: [clean-code, testing-patterns]
+commit-types: [feat, refactor]
+---
+
+# /enhance — Iterative Feature Development
+
+> **Trigger**: `/enhance [description]`
+> **Lifecycle**: Build — after `/plan` or ad-hoc for minor updates
+
+> [!IMPORTANT]
+> This workflow modifies existing code. Always analyze the impact of changes before implementation. Preserve existing functionality — never break what works.
+
+> [!TIP]
+> This workflow leverages the **clean-code** skill. Read `.agent/skills/clean-code/SKILL.md` for extended guidance on code quality during iterative development.
+
+---
+
+## Critical Rules
+
+1. **Preserve existing functionality** — changes must not break what currently works
+2. **Regression check mandatory** — run the full test suite after every change
+3. **User approval for major changes** — present an impact analysis before modifying >5 files
+4. **Incremental approach** — make small, verifiable changes rather than large rewrites
+5. **Follow existing conventions** — match the patterns already established in the codebase
+6. **Document changes** — update documentation to reflect the modified behavior
+
+---
+
+## Argument Parsing
+
+| Command | Action |
+| :----------------------------- | :---------------------------------------------- |
+| `/enhance` | Prompt for feature description |
+| `/enhance [description]` | Begin enhancing the specified feature directly |
+
+---
+
+## Steps
+
+// turbo
+1. **Understand Current State**
+   - Explore the project structure and architecture
+   - Review existing features, tech stack, and conventions
+   - Identify the files and modules relevant to the enhancement
+
+// turbo
+2. **Impact Analysis**
+   - Identify all files that will be affected by the change
+   - Map dependencies and downstream consumers
+   - Assess risk of regressions in adjacent features
+   - Flag any breaking changes or architectural implications
+
+3. **Present Enhancement Plan** (for changes affecting >5 files)
+
+   ```
+   "To add [feature]:
+   - I'll create [N] new files
+   - Modify [N] existing files
+   - Affected areas: [list]
+   - Estimated risk: Low | Medium | High
+
+   Should I proceed?"
+   ```
+
+4. **Implement Changes**
+   - Follow existing code patterns and conventions
+   - Apply changes incrementally
+   - Keep each change small and verifiable
+
+// turbo
+5. **Regression Check**
+   - Run the full test suite
+   - Verify build succeeds
+   - Check that existing functionality is preserved
+   - Run lint and type-check
+
+6. **Document Changes**
+   - Update inline documentation
+   - Update README or docs if user-facing behavior changes
+   - Add changelog entry if applicable
+
+---
+
+## Output Template
+
+```markdown
+## 🔧 Enhancement: [Feature Name]
+
+### Changes Summary
+
+| Action | File | Description |
+| :----- | :--- | :---------- |
+| Modified | `path/to/file` | [what changed] |
+| Created | `path/to/file` | [purpose] |
+
+### Impact Analysis
+
+- **Files affected**: [count]
+- **Risk level**: Low | Medium | High
+- **Breaking changes**: None | [description]
+
+### Regression Check
+
+- ✅ Tests: [pass count] passing
+- ✅ Build: successful
+- ✅ Lint: clean
+- ✅ Type-check: clean
+
+### What Changed
+
+[Human-readable summary of the enhancement]
+
+After enhancement: proceed to `/test` for validation or `/preview` for visual check.
+```
+
+---
+
+## Governance
+
+**PROHIBITED:**
+- Breaking existing functionality to add new features
+- Making large changes without impact analysis
+- Skipping regression checks after modifications
+- Ignoring existing code conventions
+- Skipping failed steps · proceeding without resolution
+
+**REQUIRED:**
+- Impact analysis before implementation
+- User approval for changes affecting >5 files
+- Regression check (tests, build, lint) after every change
+- Documentation update for user-facing changes
+- Incremental, verifiable changes
+
+---
+
+## Completion Criteria
+
+- [ ] Current state is understood (architecture, patterns, conventions)
+- [ ] Impact analysis is complete (affected files, risk level)
+- [ ] User approved the plan (for major changes)
+- [ ] Changes are implemented following existing patterns
+- [ ] Regression check passes (tests, build, lint, type-check)
+- [ ] Documentation is updated
+- [ ] After enhancement: proceed to `/test` for validation or `/preview` for visual check
+
+---
+
+## Related Resources
+
+- **Previous**: `/plan` (implementation plan for major enhancements)
+- **Next**: `/test` (validate changes) · `/preview` (visual verification)
+- **Skill**: `.agent/skills/clean-code/SKILL.md`
+- **Related Skills**: `.agent/skills/architecture/SKILL.md` · `.agent/skills/testing-patterns/SKILL.md`