wegho-agentes 7.0.3 → 7.0.6

package/.agent/skills/deployment-procedures/SKILL.md

@@ -0,0 +1,241 @@
+---
+name: deployment-procedures
+description: Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
+allowed-tools: Read, Glob, Grep, Bash
+---
+
+# Deployment Procedures
+
+> Deployment principles and decision-making for safe production releases.
+> **Learn to THINK, not memorize scripts.**
+
+---
+
+## ⚠️ How to Use This Skill
+
+This skill teaches **deployment principles**, not bash scripts to copy.
+
+- Every deployment is unique
+- Understand the WHY behind each step
+- Adapt procedures to your platform
+
+---
+
+## 1. Platform Selection
+
+### Decision Tree
+
+```
+What are you deploying?
+│
+├── Static site / JAMstack
+│   └── Vercel, Netlify, Cloudflare Pages
+│
+├── Simple web app
+│   ├── Managed → Railway, Render, Fly.io
+│   └── Control → VPS + PM2/Docker
+│
+├── Microservices
+│   └── Container orchestration
+│
+└── Serverless
+    └── Edge functions, Lambda
+```
+
+### Each Platform Has Different Procedures
+
+| Platform | Deployment Method |
+|----------|------------------|
+| **Vercel/Netlify** | Git push, auto-deploy |
+| **Railway/Render** | Git push or CLI |
+| **VPS + PM2** | SSH + manual steps |
+| **Docker** | Image push + orchestration |
+| **Kubernetes** | kubectl apply |
+
+---
+
+## 2. Pre-Deployment Principles
+
+### The 4 Verification Categories
+
+| Category | What to Check |
+|----------|--------------|
+| **Code Quality** | Tests passing, linting clean, reviewed |
+| **Build** | Production build works, no warnings |
+| **Environment** | Env vars set, secrets current |
+| **Safety** | Backup done, rollback plan ready |
+
+### Pre-Deployment Checklist
+
+- [ ] All tests passing
+- [ ] Code reviewed and approved
+- [ ] Production build successful
+- [ ] Environment variables verified
+- [ ] Database migrations ready (if any)
+- [ ] Rollback plan documented
+- [ ] Team notified
+- [ ] Monitoring ready
+
+---
+
+## 3. Deployment Workflow Principles
+
+### The 5-Phase Process
+
+```
+1. PREPARE
+   └── Verify code, build, env vars
+
+2. BACKUP
+   └── Save current state before changing
+
+3. DEPLOY
+   └── Execute with monitoring open
+
+4. VERIFY
+   └── Health check, logs, key flows
+
+5. CONFIRM or ROLLBACK
+   └── All good? Confirm. Issues? Rollback.
+```
+
+### Phase Principles
+
+| Phase | Principle |
+|-------|-----------|
+| **Prepare** | Never deploy untested code |
+| **Backup** | Can't rollback without backup |
+| **Deploy** | Watch it happen, don't walk away |
+| **Verify** | Trust but verify |
+| **Confirm** | Have rollback trigger ready |
+
+---
+
+## 4. Post-Deployment Verification
+
+### What to Verify
+
+| Check | Why |
+|-------|-----|
+| **Health endpoint** | Service is running |
+| **Error logs** | No new errors |
+| **Key user flows** | Critical features work |
+| **Performance** | Response times acceptable |
+
+### Verification Window
+
+- **First 5 minutes**: Active monitoring
+- **15 minutes**: Confirm stable
+- **1 hour**: Final verification
+- **Next day**: Review metrics
+
+---
+
+## 5. Rollback Principles
+
+### When to Rollback
+
+| Symptom | Action |
+|---------|--------|
+| Service down | Rollback immediately |
+| Critical errors | Rollback |
+| Performance >50% degraded | Consider rollback |
+| Minor issues | Fix forward if quick |
+
+### Rollback Strategy by Platform
+
+| Platform | Rollback Method |
+|----------|----------------|
+| **Vercel/Netlify** | Redeploy previous commit |
+| **Railway/Render** | Rollback in dashboard |
+| **VPS + PM2** | Restore backup, restart |
+| **Docker** | Previous image tag |
+| **K8s** | kubectl rollout undo |
+
+### Rollback Principles
+
+1. **Speed over perfection**: Rollback first, debug later
+2. **Don't compound errors**: One rollback, not multiple changes
+3. **Communicate**: Tell team what happened
+4. **Post-mortem**: Understand why after stable
+
+---
+
+## 6. Zero-Downtime Deployment
+
+### Strategies
+
+| Strategy | How It Works |
+|----------|--------------|
+| **Rolling** | Replace instances one by one |
+| **Blue-Green** | Switch traffic between environments |
+| **Canary** | Gradual traffic shift |
+
+### Selection Principles
+
+| Scenario | Strategy |
+|----------|----------|
+| Standard release | Rolling |
+| High-risk change | Blue-green (easy rollback) |
+| Need validation | Canary (test with real traffic) |
+
+---
+
+## 7. Emergency Procedures
+
+### Service Down Priority
+
+1. **Assess**: What's the symptom?
+2. **Quick fix**: Restart if unclear
+3. **Rollback**: If restart doesn't help
+4. **Investigate**: After stable
+
+### Investigation Order
+
+| Check | Common Issues |
+|-------|--------------|
+| **Logs** | Errors, exceptions |
+| **Resources** | Disk full, memory |
+| **Network** | DNS, firewall |
+| **Dependencies** | Database, APIs |
+
+---
+
+## 8. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Deploy on Friday | Deploy early in week |
+| Rush deployment | Follow the process |
+| Skip staging | Always test first |
+| Deploy without backup | Backup before deploy |
+| Walk away after deploy | Monitor for 15+ min |
+| Multiple changes at once | One change at a time |
+
+---
+
+## 9. Decision Checklist
+
+Before deploying:
+
+- [ ] **Platform-appropriate procedure?**
+- [ ] **Backup strategy ready?**
+- [ ] **Rollback plan documented?**
+- [ ] **Monitoring configured?**
+- [ ] **Team notified?**
+- [ ] **Time to monitor after?**
+
+---
+
+## 10. Best Practices
+
+1. **Small, frequent deploys** over big releases
+2. **Feature flags** for risky changes
+3. **Automate** repetitive steps
+4. **Document** every deployment
+5. **Review** what went wrong after issues
+6. **Test rollback** before you need it
+
+---
+
+> **Remember:** Every deployment is a risk. Minimize risk through preparation, not speed.

package/.agent/skills/doc.md

@@ -0,0 +1,177 @@
+# Antigravity Skills
+
+> **Guide to creating and using Skills in the Antigravity Kit**
+
+---
+
+## 📋 Overview
+
+While Antigravity's base models (like Gemini) are powerful generalists, they don't know your specific project context or your team's standards. Loading every rule or tool into the agent's context window leads to "tool bloat," higher costs, latency, and confusion.
+
+**Antigravity Skills** solve this through **Progressive Disclosure**. A Skill is a package of specialized knowledge that remains dormant until needed. This information is only loaded into the agent's context when your specific request matches the skill's description.
+
+---
+
+## 📁 Structure and Scope
+
+Skills are folder-based packages. You can define these scopes based on your needs:
+
+| Scope         | Path                              | Description                          |
+| ------------- | --------------------------------- | ------------------------------------ |
+| **Workspace** | `<workspace-root>/.agent/skills/` | Available only in a specific project |
+
+### Skill Directory Structure
+
+```
+my-skill/
+├── SKILL.md      # (Required) Metadata & instructions
+├── scripts/      # (Optional) Python or Bash scripts
+├── references/   # (Optional) Text, documentation, templates
+└── assets/       # (Optional) Images or logos
+```
+
+---
+
+## 🔍 Example 1: Code Review Skill
+
+This is an instruction-only skill; you only need to create the `SKILL.md` file.
+
+### Step 1: Create the directory
+
+```bash
+mkdir -p .agent/skills/code-review
+```
+
+### Step 2: Create SKILL.md
+
+```markdown
+---
+name: code-review
+description: Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
+---
+
+# Code Review Skill
+
+When reviewing code, follow these steps:
+
+## Review checklist
+
+1. **Correctness**: Does the code do what it's supposed to?
+2. **Edge cases**: Are error conditions handled?
+3. **Style**: Does it follow project conventions?
+4. **Performance**: Are there obvious inefficiencies?
+
+## How to provide feedback
+
+- Be specific about what needs to change
+- Explain why, not just what
+- Suggest alternatives when possible
+```
+
+> **Note**: The `SKILL.md` file contains metadata (name, description) at the top, followed by the instructions. The agent will only read the metadata and load the full instructions only when needed.
+
+### Try it out
+
+Create a file `demo_bad_code.py`:
+
+```python
+import time
+
+def get_user_data(users, id):
+    # Find user by ID
+    for u in users:
+        if u['id'] == id:
+            return u
+    return None
+
+def process_payments(items):
+    total = 0
+    for i in items:
+        # Calculate tax
+        tax = i['price'] * 0.1
+        total = total + i['price'] + tax
+        time.sleep(0.1)  # Simulate slow network call
+    return total
+
+def run_batch():
+    users = [{'id': 1, 'name': 'Alice'}, {'id': 2, 'name': 'Bob'}]
+    items = [{'price': 10}, {'price': 20}, {'price': 100}]
+
+    u = get_user_data(users, 3)
+    print("User found: " + u['name'])  # Will crash if None
+
+    print("Total: " + str(process_payments(items)))
+
+if __name__ == "__main__":
+    run_batch()
+```
+
+**Prompt**: `review the @demo_bad_code.py file`
+
+The Agent will automatically identify the `code-review` skill, load the information, and follow the instructions.
+
+---
+
+## 📄 Example 2: License Header Skill
+
+This skill uses a reference file in the `resources/` (or `references/`) directory.
+
+### Step 1: Create the directory
+
+```bash
+mkdir -p .agent/skills/license-header-adder/resources
+```
+
+### Step 2: Create the template file
+
+**`.agent/skills/license-header-adder/resources/HEADER.txt`**:
+
+```
+/*
+ * Copyright (c) 2026 YOUR_COMPANY_NAME LLC.
+ * All rights reserved.
+ * This code is proprietary and confidential.
+ */
+```
+
+### Step 3: Create SKILL.md
+
+**`.agent/skills/license-header-adder/SKILL.md`**:
+
+```markdown
+---
+name: license-header-adder
+description: Adds the standard corporate license header to new source files.
+---
+
+# License Header Adder
+
+This skill ensures that all new source files have the correct copyright header.
+
+## Instructions
+
+1. **Read the Template**: Read the content of `resources/HEADER.txt`.
+2. **Apply to File**: When creating a new file, prepend this exact content.
+3. **Adapt Syntax**:
+   - For C-style languages (Java, TS), keep the `/* */` block.
+   - For Python/Shell, convert to `#` comments.
+```
+
+### Try it out
+
+**Prompt**: `Create a new Python script named data_processor.py that prints 'Hello World'.`
+
+The Agent will read the template, convert the comments to Python style, and automatically add it to the top of the file.
+
+---
+
+## 🎯 Conclusion
+
+By creating Skills, you transform a general AI model into an expert for your project:
+
+- ✅ Systematize best practices
+- ✅ Adhere to code review rules
+- ✅ Automatically add license headers
+- ✅ The Agent automatically knows how to work with your team
+
+Instead of constantly reminding the AI to "remember to add the license" or "fix the commit format," now the Agent will do it automatically!

package/.agent/skills/documentation-templates/SKILL.md

@@ -0,0 +1,194 @@
+---
+name: documentation-templates
+description: Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
+allowed-tools: Read, Glob, Grep
+---
+
+# Documentation Templates
+
+> Templates and structure guidelines for common documentation types.
+
+---
+
+## 1. README Structure
+
+### Essential Sections (Priority Order)
+
+| Section | Purpose |
+|---------|---------|
+| **Title + One-liner** | What is this? |
+| **Quick Start** | Running in <5 min |
+| **Features** | What can I do? |
+| **Configuration** | How to customize |
+| **API Reference** | Link to detailed docs |
+| **Contributing** | How to help |
+| **License** | Legal |
+
+### README Template
+
+```markdown
+# Project Name
+
+Brief one-line description.
+
+## Quick Start
+
+[Minimum steps to run]
+
+## Features
+
+- Feature 1
+- Feature 2
+
+## Configuration
+
+| Variable | Description | Default |
+|----------|-------------|---------|
+| PORT | Server port | 3000 |
+
+## Documentation
+
+- [API Reference](./docs/api.md)
+- [Architecture](./docs/architecture.md)
+
+## License
+
+MIT
+```
+
+---
+
+## 2. API Documentation Structure
+
+### Per-Endpoint Template
+
+```markdown
+## GET /users/:id
+
+Get a user by ID.
+
+**Parameters:**
+| Name | Type | Required | Description |
+|------|------|----------|-------------|
+| id | string | Yes | User ID |
+
+**Response:**
+- 200: User object
+- 404: User not found
+
+**Example:**
+[Request and response example]
+```
+
+---
+
+## 3. Code Comment Guidelines
+
+### JSDoc/TSDoc Template
+
+```typescript
+/**
+ * Brief description of what the function does.
+ * 
+ * @param paramName - Description of parameter
+ * @returns Description of return value
+ * @throws ErrorType - When this error occurs
+ * 
+ * @example
+ * const result = functionName(input);
+ */
+```
+
+### When to Comment
+
+| ✅ Comment | ❌ Don't Comment |
+|-----------|-----------------|
+| Why (business logic) | What (obvious) |
+| Complex algorithms | Every line |
+| Non-obvious behavior | Self-explanatory code |
+| API contracts | Implementation details |
+
+---
+
+## 4. Changelog Template (Keep a Changelog)
+
+```markdown
+# Changelog
+
+## [Unreleased]
+### Added
+- New feature
+
+## [1.0.0] - 2025-01-01
+### Added
+- Initial release
+### Changed
+- Updated dependency
+### Fixed
+- Bug fix
+```
+
+---
+
+## 5. Architecture Decision Record (ADR)
+
+```markdown
+# ADR-001: [Title]
+
+## Status
+Accepted / Deprecated / Superseded
+
+## Context
+Why are we making this decision?
+
+## Decision
+What did we decide?
+
+## Consequences
+What are the trade-offs?
+```
+
+---
+
+## 6. AI-Friendly Documentation (2025)
+
+### llms.txt Template
+
+For AI crawlers and agents:
+
+```markdown
+# Project Name
+> One-line objective.
+
+## Core Files
+- [src/index.ts]: Main entry
+- [src/api/]: API routes
+- [docs/]: Documentation
+
+## Key Concepts
+- Concept 1: Brief explanation
+- Concept 2: Brief explanation
+```
+
+### MCP-Ready Documentation
+
+For RAG indexing:
+- Clear H1-H3 hierarchy
+- JSON/YAML examples for data structures
+- Mermaid diagrams for flows
+- Self-contained sections
+
+---
+
+## 7. Structure Principles
+
+| Principle | Why |
+|-----------|-----|
+| **Scannable** | Headers, lists, tables |
+| **Examples first** | Show, don't just tell |
+| **Progressive detail** | Simple → Complex |
+| **Up to date** | Outdated = misleading |
+
+---
+
+> **Remember:** Templates are starting points. Adapt to your project's needs.

package/.agent/skills/file-doc-sync/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: file-doc-sync
+description: Generate and keep technical `.md` documentation synchronized beside each supported source or configuration file in the project. Use when the system needs a first-pass documentation sweep, when code changes require updating sibling docs, or when every file must maintain an always-current technical `.md` in the same folder.
+---
+
+# File Doc Sync
+
+Keep per-file technical documentation synchronized with the codebase.
+
+This skill creates one sibling `.md` file for each supported file and refreshes that documentation whenever the original file changes. The generated docs must stay short, technical, objective, and focused on the real role of the file in the system.
+
+## Workflow
+
+1. Run `tsx .agents/sync-docs.ts`.
+2. Scan the workspace recursively.
+3. Ignore generated directories, markdown files, and binaries.
+4. Create or update each sibling `.md`.
+5. Rerun after every implementation change before finalizing work.
+
+## Required sections
+
+Every generated `.md` must contain, in this order:
+- `## O que este arquivo faz`
+- `## Principais Responsabilidades`
+- `## Como funciona`
+- `## Dependências`
+- `## Integrações`
+- `## Segurança`
+- `## Impacto da Remoção`
+- `## Resumo Técnico`
+
+## Rules
+
+- Explain the real function of the file in the system.
+- Avoid line-by-line commentary.
+- Prefer short paragraphs and 3-5 bullets when list-shaped.
+- Mention only real dependencies, integrations, and security controls detected in the file.
+- If no direct security rule exists, say that security depends on external layers.
+- Keep the `.md` beside the original file.
+
+## Resources
+
+- Script: `scripts/sync-file-docs.ts`
+- Reference: `references/document-structure.md`

package/.agent/skills/file-doc-sync/references/document-structure.md

@@ -0,0 +1,20 @@
+# Estrutura da Documentação por Arquivo
+
+Use sempre esta ordem:
+
+1. `## O que este arquivo faz`
+2. `## Principais Responsabilidades`
+3. `## Como funciona`
+4. `## Dependências`
+5. `## Integrações`
+6. `## Segurança`
+7. `## Impacto da Remoção`
+8. `## Resumo Técnico`
+
+Regras:
+- Texto curto, técnico e objetivo.
+- Sem explicação linha por linha.
+- Sem repetição desnecessária.
+- Sempre gerar a documentação na mesma pasta do arquivo original.
+- O nome do arquivo deve trocar apenas a extensão para `.md` quando possível.
+- Para arquivos iniciados por ponto, manter o nome original e adicionar `.md` ao final.

package/.agent/skills/file-doc-sync/scripts/sync-file-docs.md

@@ -0,0 +1,45 @@
+# sync-file-docs.ts
+
+> Arquivo fonte: `.agent/skills/file-doc-sync/scripts/sync-file-docs.ts`
+
+## O que este arquivo faz
+Este arquivo expõe lógica reutilizável para outras partes do sistema, centralizando comportamento, configuração ou execução especializada.
+
+## Principais Responsabilidades
+- Expor 2 item(ns) reutilizável(is) para outras partes do sistema.
+- Definir classes ou estruturas centrais para encapsular comportamento.
+- Concentrar funções que executam a lógica principal deste arquivo.
+- Servir como ponto de manutenção para esta parte da funcionalidade.
+
+## Como funciona
+1. Carrega definições locais e dependências necessárias.
+2. Expõe a interface pública consumida por outros arquivos do projeto.
+3. Executa etapas assíncronas quando precisa consultar arquivos, serviços ou processos externos.
+4. Processa a responsabilidade principal do arquivo e retorna ou aplica o resultado esperado.
+5. Entrega a saída esperada para os consumidores diretos deste arquivo.
+
+## Dependências
+- fs
+- path
+- url
+
+## Integrações
+- Supabase
+- PostgreSQL
+- HostGator
+- HTTP APIs externas
+- Variáveis de ambiente
+- Sistema de arquivos
+
+## Segurança
+- Aplica ou referencia regras de RLS.
+- Inclui verificação ou dependência de autenticação/autorização.
+- Manipula dados sensíveis e exige cuidado com exposição em logs e cliente.
+- Utiliza mecanismos de proteção criptográfica ou hashing.
+- Define ou consome regras de acesso baseadas em policy.
+
+## Impacto da Remoção
+Sem este arquivo, consumidores diretos perdem a lógica ou a configuração que ele centraliza, causando erro funcional ou regressão de comportamento.
+
+## Resumo Técnico
+Arquivo técnico de suporte ao sistema, responsável por fornecer lógica, configuração ou interface reutilizável para outros módulos.