antigravity-devkit 1.0.3 → 1.0.4

package/template/workflows/debug.md

@@ -1,83 +0,0 @@
----
-description: Debug issues and fix bugs
----
-
-# /debug - Bug Fixing
-
-$ARGUMENTS
-
----
-
-## Purpose
-
-Systematically find and fix the root cause of issues.
-
----
-
-## Protocol
-
-### 1. Gather Information
-- What is the error message?
-- What are the reproduction steps?
-- What's expected vs actual?
-
-### 2. Apply Debugger Agent
-Route to `@debugger` with systematic-debugging skill.
-
-### 3. Investigation Flow
-
-```
-REPRODUCE → ISOLATE → IDENTIFY → FIX → VERIFY
-```
-
-### 4. Root Cause Analysis
-
-| Step | Question |
-|------|----------|
-| Reproduce | Can we trigger it? |
-| Isolate | Where does it fail? |
-| Identify | What's the root cause? |
-| Fix | Minimal change |
-| Verify | Does it work? |
-
----
-
-## Fix Approach
-
-- ✅ Minimal change
-- ✅ Add regression test
-- ✅ No side effects
-- ❌ Guess and patch
-- ❌ Multiple unrelated changes
-
----
-
-## Human Checkpoint
-
-```markdown
-🔍 **Root cause identified:**
-
-Issue: [description]
-Cause: [root cause]
-Fix: [proposed solution]
-
-**Approve fix?**
-```
-
----
-
-## Output
-
-```markdown
-✅ **Bug fixed**
-
-Root cause: [description]
-Fix: [what was changed]
-
-Files modified:
-- `path/to/file`
-
-Tests:
-- [x] Regression test added
-- [x] All tests pass
-```

package/template/workflows/deploy.md

@@ -1,101 +0,0 @@
----
-description: Deploy to Azure DevOps with approval
----
-
-# /deploy - Deployment
-
-$ARGUMENTS
-
----
-
-## Purpose
-
-Trigger Azure DevOps deployment with human approval.
-
----
-
-## Pre-Deployment Checklist
-
-```markdown
-## Deployment Checklist
-
-### Code Quality
-- [ ] All tests pass
-- [ ] Code review approved
-- [ ] No lint errors
-
-### Security
-- [ ] Security scan passed
-- [ ] No exposed secrets
-- [ ] Dependencies updated
-
-### Documentation
-- [ ] README updated
-- [ ] API docs current
-- [ ] Changelog updated
-```
-
----
-
-## Protocol
-
-### 1. Verify Prerequisites
-- Tests passing?
-- Review approved?
-- Branch up to date?
-
-### 2. Select Environment
-
-| Environment | Approval |
-|-------------|----------|
-| Dev | Auto |
-| Staging | Auto |
-| Production | **Required** |
-
-### 3. Human Approval (Production)
-
-```markdown
-🚀 **Ready to deploy to PRODUCTION**
-
-Changes:
-- [List of changes]
-
-Pre-flight:
-- [x] Tests pass
-- [x] Review approved
-- [x] Security scan clean
-
-**Approve deployment?**
-```
-
-### 4. Trigger Pipeline
-
-```bash
-# Azure DevOps CLI
-az pipelines run --name "Deploy-Pipeline" --branch main
-```
-
----
-
-## Post-Deployment
-
-```markdown
-✅ **Deployed to [Environment]**
-
-Pipeline: [link]
-Status: Success
-
-Verification:
-- [ ] Health check passed
-- [ ] Smoke tests passed
-- [ ] Monitoring active
-```
-
----
-
-## Rollback
-
-If issues detected:
-```
-az pipelines run --name "Rollback-Pipeline"
-```

package/template/workflows/orchestrate.md

@@ -1,86 +0,0 @@
----
-description: Multi-agent coordination for complex tasks
----
-
-# /orchestrate - Multi-Agent Task
-
-$ARGUMENTS
-
----
-
-## Purpose
-
-Coordinate multiple specialist agents for complex, multi-domain tasks.
-
----
-
-## Protocol
-
-### 1. Analyze Request
-Identify all domains involved:
-- Frontend (Vue3)?
-- Backend (ASP.NET)?
-- Database (SQL Server)?
-- DevOps (Azure)?
-
-### 2. Create Orchestration Plan
-
-```markdown
-## Orchestration Plan: [Task]
-
-### Agents Required
-- @backend-specialist
-- @frontend-specialist
-- @database-architect
-
-### Phases
-1. Database schema [@database-architect]
-2. API endpoints [@backend-specialist]
-3. UI components [@frontend-specialist]
-4. Integration tests [@test-engineer]
-
-### Checkpoints
-- After Phase 2 (backend complete)
-- After Phase 4 (all complete)
-```
-
-### 3. Execute with Checkpoints
-
-After each phase:
-```markdown
-🛑 **Checkpoint: Phase [N] Complete**
-
-Completed:
-- [x] Task 1
-- [x] Task 2
-
-Next: Phase [N+1]
-
-**Continue?**
-```
-
-### 4. Final Verification
-
-```markdown
-✅ **Orchestration Complete**
-
-All phases:
-- [x] Phase 1: Database
-- [x] Phase 2: Backend
-- [x] Phase 3: Frontend
-- [x] Phase 4: Testing
-
-Verification:
-- [x] All tests pass
-- [x] Integration verified
-```
-
----
-
-## When to Orchestrate
-
-| Scenario | Action |
-|----------|--------|
-| Single domain | Direct to specialist |
-| Multi-domain | Orchestrate |
-| Full feature | Orchestrate |

package/template/workflows/plan.md

@@ -1,79 +0,0 @@
----
-description: Create project plan with task breakdown. No code - planning only.
----
-
-# /plan - Project Planning
-
-$ARGUMENTS
-
----
-
-## Purpose
-
-Create a structured plan file with task breakdown. **NO CODE WRITING.**
-
----
-
-## Protocol
-
-### 1. Socratic Gate
-Ask clarifying questions if request is vague.
-
-### 2. Create Plan File
-**Location:** `docs/PLAN-{slug}.md`
-
-**Naming:** Extract 2-3 keywords, lowercase, hyphen-separated.
-
-| Request | File |
-|---------|------|
-| E-commerce cart | PLAN-ecommerce-cart.md |
-| User authentication | PLAN-user-auth.md |
-
-### 3. Plan Structure
-
-```markdown
-# PLAN: [Feature Name]
-
-## Overview
-[Brief description]
-
-## Requirements
-- [ ] Requirement 1
-- [ ] Requirement 2
-
-## Tasks
-
-### Backend
-- [ ] Task 1 [@backend-specialist]
-
-### Frontend
-- [ ] Task 2 [@frontend-specialist]
-
-### Testing
-- [ ] Task 3 [@test-engineer]
-
-## Verification
-- [ ] Run checklist.py
-- [ ] Code review
-```
-
----
-
-## Rules
-
-- ❌ NO code writing
-- ✅ Assign agents to tasks
-- ✅ Order by dependency
-- ✅ Include verification
-
----
-
-## After Planning
-
-```markdown
-✅ **Plan created:** docs/PLAN-{slug}.md
-
-**Next steps:**
-1. Review the plan
-2. Run `/create` to implement
-```

package/template/workflows/review.md

@@ -1,85 +0,0 @@
----
-description: Code review with security checks
----
-
-# /review - Code Review
-
-$ARGUMENTS
-
----
-
-## Purpose
-
-Review code for quality, security, and best practices.
-
----
-
-## Protocol
-
-### 1. Identify Scope
-- Which files to review?
-- Focus areas (security, performance, etc.)?
-
-### 2. Apply Reviewers
-- `@security-auditor` for security
-- Domain specialist for patterns
-
-### 3. Review Checklist
-
-**Code Quality:**
-- [ ] Clean code principles
-- [ ] No code smells
-- [ ] Proper naming
-- [ ] No duplication
-
-**Security:**
-- [ ] No hardcoded secrets
-- [ ] Input validation
-- [ ] Proper auth checks
-- [ ] No SQL injection
-
-**Performance:**
-- [ ] No N+1 queries
-- [ ] Proper async usage
-- [ ] No memory leaks
-
-**Testing:**
-- [ ] Tests exist
-- [ ] Edge cases covered
-- [ ] Tests pass
-
----
-
-## Output Format
-
-```markdown
-## Code Review: [Scope]
-
-### ✅ Passed
-- Clean code standards
-- Security checks
-
-### ⚠️ Suggestions
-- [Improvement 1]
-- [Improvement 2]
-
-### ❌ Issues (Must Fix)
-- [Critical issue]
-
-**Approve for deployment?**
-```
-
----
-
-## Human Approval
-
-Review requires explicit approval before `/deploy`.
-
----
-
-## After Review
-
-```
-Approved: /deploy
-Issues: Fix and re-review
-```

package/template/workflows/status.md

@@ -1,90 +0,0 @@
----
-description: Check project health and status
----
-
-# /status - Project Health
-
-$ARGUMENTS
-
----
-
-## Purpose
-
-Quick overview of project health and status.
-
----
-
-## Protocol
-
-### 1. Gather Metrics
-
-**Code Quality:**
-- Lint errors
-- Type errors
-- Test coverage
-
-**Dependencies:**
-- Outdated packages
-- Security vulnerabilities
-
-**Build:**
-- Last build status
-- Build time
-
----
-
-## Status Report
-
-```markdown
-## Project Status: [Project Name]
-
-### Code Quality
-| Metric | Status |
-|--------|--------|
-| Lint | ✅ Clean |
-| Types | ✅ No errors |
-| Coverage | 85% |
-
-### Dependencies
-| Check | Status |
-|-------|--------|
-| Outdated | ⚠️ 3 packages |
-| Vulnerable | ✅ None |
-
-### Build
-| Metric | Value |
-|--------|-------|
-| Last build | ✅ Passed |
-| Duration | 2m 30s |
-
-### Recommendations
-1. Update outdated packages
-2. Add tests for new features
-```
-
----
-
-## Commands Used
-
-```bash
-# Lint check
-npm run lint
-
-# Type check
-npm run type-check
-
-# Test coverage
-npm run test -- --coverage
-
-# Outdated packages
-npm outdated
-
-# Vulnerabilities
-npm audit
-```
-
----
-
-## No Approval Required
-
-Status check is read-only, no human approval needed.

package/template/workflows/test.md

@@ -1,89 +0,0 @@
----
-description: Generate tests for existing code
----
-
-# /test - Test Generation
-
-$ARGUMENTS
-
----
-
-## Purpose
-
-Generate unit and integration tests for specified code.
-
----
-
-## Protocol
-
-### 1. Analyze Target
-- What code needs testing?
-- Frontend (Vitest) or Backend (xUnit)?
-- Unit or integration tests?
-
-### 2. Apply Testing Agent
-Route to `@test-engineer` with appropriate skills.
-
-### 3. Generate Tests
-
-**Frontend (Vitest):**
-```typescript
-describe('ComponentName', () => {
-  it('should render', () => {
-    // Arrange, Act, Assert
-  })
-})
-```
-
-**Backend (xUnit):**
-```csharp
-[Fact]
-public void Method_Scenario_Expected()
-{
-    // Arrange, Act, Assert
-}
-```
-
-### 4. Run Tests
-
-```bash
-# Frontend
-npm run test
-
-# Backend
-dotnet test
-```
-
----
-
-## Test Coverage
-
-| Target | Minimum |
-|--------|---------|
-| Business logic | 90% |
-| API endpoints | 80% |
-| Components | 70% |
-
----
-
-## Output
-
-```markdown
-✅ **Tests generated**
-
-Files:
-- `tests/UserService.test.ts`
-- `tests/UserController.Tests.cs`
-
-Results:
-- 10 tests passed
-- Coverage: 85%
-```
-
----
-
-## After Testing
-
-```
-Next: `/review` for code review
-```