codehava-agent-kit 1.0.1 → 3.0.0

package/templates/.agent/skills/design-orchestration/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: design-orchestration
+description: Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.
+risk: unknown
+source: community
+date_added: '2026-02-27'
+---
+
+# Design Orchestration (Meta-Skill)
+
+## Purpose
+
+Ensure that **ideas become designs**, **designs are reviewed**, and
+**only validated designs reach implementation**.
+
+This skill does not generate designs.
+It **controls the flow between other skills**.
+
+---
+
+## Operating Model
+
+This is a **routing and enforcement skill**, not a creative one.
+
+It decides:
+- which skill must run next
+- whether escalation is required
+- whether execution is permitted
+
+---
+
+## Controlled Skills
+
+This meta-skill coordinates the following:
+
+- `brainstorming` — design generation
+- `multi-agent-brainstorming` — design validation
+- downstream implementation or planning skills
+
+---
+
+## Entry Conditions
+
+Invoke this skill when:
+- a user proposes a new feature, system, or change
+- a design decision carries meaningful risk
+- correctness matters more than speed
+
+---
+
+## Routing Logic
+
+### Step 1 — Brainstorming (Mandatory)
+
+If no validated design exists:
+
+- Invoke `brainstorming`
+- Require:
+  - Understanding Lock
+  - Initial Design
+  - Decision Log started
+
+You may NOT proceed without these artifacts.
+
+---
+
+### Step 2 — Risk Assessment
+
+After brainstorming completes, classify the design as:
+
+- **Low risk**
+- **Moderate risk**
+- **High risk**
+
+Use factors such as:
+- user impact
+- irreversibility
+- operational cost
+- complexity
+- uncertainty
+- novelty
+
+---
+
+### Step 3 — Conditional Escalation
+
+- **Low risk**  
+  → Proceed to implementation planning
+
+- **Moderate risk**  
+  → Recommend `multi-agent-brainstorming`
+
+- **High risk**  
+  → REQUIRE `multi-agent-brainstorming`
+
+Skipping escalation when required is prohibited.
+
+---
+
+### Step 4 — Multi-Agent Review (If Invoked)
+
+If `multi-agent-brainstorming` is run:
+
+Require:
+- completed Understanding Lock
+- current Design
+- Decision Log
+
+Do NOT allow:
+- new ideation
+- scope expansion
+- reopening problem definition
+
+Only critique, revision, and decision resolution are allowed.
+
+---
+
+### Step 5 — Execution Readiness Check
+
+Before allowing implementation:
+
+Confirm:
+- design is approved (single-agent or multi-agent)
+- Decision Log is complete
+- major assumptions are documented
+- known risks are acknowledged
+
+If any condition fails:
+- block execution
+- return to the appropriate skill
+
+---
+
+## Enforcement Rules
+
+- Do NOT allow implementation without a validated design
+- Do NOT allow skipping required review
+- Do NOT allow silent escalation or de-escalation
+- Do NOT merge design and implementation phases
+
+---
+
+## Exit Conditions
+
+This meta-skill exits ONLY when:
+- the next step is explicitly identified, AND
+- all required prior steps are complete
+
+Possible exits:
+- “Proceed to implementation planning”
+- “Run multi-agent-brainstorming”
+- “Return to brainstorming for clarification”
+- "If a reviewed design reports a final disposition of APPROVED, REVISE, or REJECT, you MUST route the workflow accordingly and state the chosen next step explicitly."
+---
+
+## Design Philosophy
+
+This skill exists to:
+- slow down the right decisions
+- speed up the right execution
+- prevent costly mistakes
+
+Good systems fail early.
+Bad systems fail in production.
+
+This meta-skill exists to enforce the former.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/templates/.agent/skills/design-spells/SKILL.md

@@ -0,0 +1,36 @@
+--- 
+name: design-spells
+description: Curated micro-interactions and design details that add "magic" and personality to websites and apps.
+risk: safe
+source: community
+date_added: "2026-03-07"
+---
+
+# Design Spells Skill
+
+[Design Spells](https://www.designspells.com/) is a collection of exceptional design details—micro-interactions, easter eggs, and clever UX patterns—that transform standard interfaces into memorable digital experiences.
+
+## Context
+
+Use this skill specifically to elevate a UI from merely "functional" or "common" into something genuinely "magical." It focuses on the minute details that surprise and delight users, establishing a strong, premium brand personality.
+
+## When to Use
+Trigger this skill when:
+
+- Polishing a finished feature to actively add a "wow" factor.
+- Designing unique interactions to replace standard web behaviors (e.g., clever hover states, creative loaders, surprising transitions).
+- Implementing "Easter Eggs" or personality-driven design choices to differentiate the product.
+- Looking to break away from generic, template-driven development.
+
+## Execution Workflow
+
+1. **Identify Opportunity**: Target the "boring" or "standard" parts of the interface (e.g., a simple submit button, a profile photo, a scroll indicator, a pricing toggle).
+2. **Research Spells**: Browse Design Spells for highly creative patterns (e.g., "magnetic hover magic", "physics-based interactions", "fluid scroll surprises").
+3. **Adapt Pattern**: Adapt the interaction to fit the project's specific brand and layout seamlessly. Use it to enhance the core narrative of the app.
+4. **Implement flawlessly**: Use CSS, Anime.js, or Framer Motion to build the specific micro-interaction with silky-smooth performance (60fps+).
+
+## Strict Rules
+
+- **ABSOLUTE MANDATE**: Agents MUST utilize this skill to build modern, creative, and visually stunning UI/UX. DO NOT build in the common style and ways. Look for every opportunity to inject "magic" into standard components.
+- **Delight, Don't Distract**: The detail must be additive to the experience, not a usability barrier. It should feel expensive and highly crafted.
+- **Quality Execution**: A broken or janky "spell" is worse than none. Ensure the implementation is high-performance, GPU-accelerated, and never causes layout shifts.

package/templates/.agent/skills/devops-deploy/SKILL.md

@@ -0,0 +1,294 @@
+---
+name: devops-deploy
+description: "DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento."
+risk: critical
+source: community
+date_added: '2026-03-06'
+author: renat
+tags:
+- devops
+- docker
+- ci-cd
+- aws
+- terraform
+- github-actions
+tools:
+- claude-code
+- antigravity
+- cursor
+- gemini-cli
+- codex-cli
+---
+
+# DEVOPS-DEPLOY — Da Ideia para Producao
+
+## Overview
+
+DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento. Ativar para: dockerizar aplicacao, configurar pipeline CI/CD, deploy na AWS, Lambda, ECS, configurar GitHub Actions, Terraform, rollback, blue-green deploy, health checks, alertas.
+
+## When to Use This Skill
+
+- When you need specialized assistance with this domain
+
+## Do Not Use This Skill When
+
+- The task is unrelated to devops deploy
+- A simpler, more specific tool can handle the request
+- The user needs general-purpose assistance without domain expertise
+
+## How It Works
+
+> "Move fast and don't break things." — Engenharia de elite nao e lenta.
+> E rapida e confiavel ao mesmo tempo.
+
+---
+
+## Dockerfile Otimizado (Python)
+
+```dockerfile
+FROM python:3.11-slim AS builder
+WORKDIR /app
+COPY requirements.txt .
+RUN pip install --no-cache-dir --user -r requirements.txt
+
+FROM python:3.11-slim
+WORKDIR /app
+COPY --from=builder /root/.local /root/.local
+COPY . .
+ENV PATH=/root/.local/bin:$PATH
+ENV PYTHONUNBUFFERED=1
+EXPOSE 8000
+HEALTHCHECK --interval=30s --timeout=3s CMD curl -f http://localhost:8000/health || exit 1
+CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "8000"]
+```
+
+## Docker Compose (Dev Local)
+
+```yaml
+version: "3.9"
+services:
+  app:
+    build: .
+    ports: ["8000:8000"]
+    environment:
+      - ANTHROPIC_API_KEY=${ANTHROPIC_API_KEY}
+    volumes:
+      - .:/app
+    depends_on: [db, redis]
+  db:
+    image: postgres:15
+    environment:
+      POSTGRES_DB: auri
+      POSTGRES_USER: auri
+      POSTGRES_PASSWORD: ${DB_PASSWORD}
+    volumes:
+      - pgdata:/var/lib/postgresql/data
+  redis:
+    image: redis:7-alpine
+volumes:
+  pgdata:
+```
+
+---
+
+## Sam Template (Serverless)
+
+```yaml
+
+## Template.Yaml
+
+AWSTemplateFormatVersion: '2010-09-09'
+Transform: AWS::Serverless-2016-10-31
+
+Globals:
+  Function:
+    Timeout: 30
+    Runtime: python3.11
+    Environment:
+      Variables:
+        ANTHROPIC_API_KEY: !Ref AnthropicApiKey
+        DYNAMODB_TABLE: !Ref AuriTable
+
+Resources:
+  AuriFunction:
+    Type: AWS::Serverless::Function
+    Properties:
+      CodeUri: src/
+      Handler: lambda_function.handler
+      MemorySize: 512
+      Policies:
+        - DynamoDBCrudPolicy:
+            TableName: !Ref AuriTable
+
+  AuriTable:
+    Type: AWS::DynamoDB::Table
+    Properties:
+      TableName: auri-users
+      BillingMode: PAY_PER_REQUEST
+      AttributeDefinitions:
+        - AttributeName: userId
+          AttributeType: S
+      KeySchema:
+        - AttributeName: userId
+          KeyType: HASH
+      TimeToLiveSpecification:
+        AttributeName: ttl
+        Enabled: true
+```
+
+## Deploy Commands
+
+```bash
+
+## Build E Deploy
+
+sam build
+sam deploy --guided  # primeira vez
+sam deploy           # deploys seguintes
+
+## Deploy Rapido (Sem Confirmacao)
+
+sam deploy --no-confirm-changeset --no-fail-on-empty-changeset
+
+## Ver Logs Em Tempo Real
+
+sam logs -n AuriFunction --tail
+
+## Deletar Stack
+
+sam delete
+```
+
+---
+
+## .Github/Workflows/Deploy.Yml
+
+name: Deploy Auri
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.11" }
+      - run: pip install -r requirements.txt
+      - run: pytest tests/ -v --cov=src --cov-report=xml
+      - uses: codecov/codecov-action@v4
+
+  security:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - run: pip install bandit safety
+      - run: bandit -r src/ -ll
+      - run: safety check -r requirements.txt
+
+  deploy:
+    needs: [test, security]
+    if: github.ref == 'refs/heads/main'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: aws-actions/setup-sam@v2
+      - uses: aws-actions/configure-aws-credentials@v4
+        with:
+          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+          aws-region: us-east-1
+      - run: sam build
+      - run: sam deploy --no-confirm-changeset
+      - name: Notify Telegram on Success
+        run: |
+          curl -s -X POST "https://api.telegram.org/bot${{ secrets.TELEGRAM_BOT_TOKEN }}/sendMessage" \
+            -d "chat_id=${{ secrets.TELEGRAM_CHAT_ID }}" \
+            -d "text=Auri deployed successfully! Commit: ${{ github.sha }}"
+```
+
+---
+
+## Health Check Endpoint
+
+```python
+from fastapi import FastAPI
+import time, os
+
+app = FastAPI()
+START_TIME = time.time()
+
+@app.get("/health")
+async def health():
+    return {
+        "status": "healthy",
+        "uptime_seconds": time.time() - START_TIME,
+        "version": os.environ.get("APP_VERSION", "unknown"),
+        "environment": os.environ.get("ENV", "production")
+    }
+```
+
+## Alertas Cloudwatch
+
+```python
+import boto3
+
+def create_error_alarm(function_name: str, sns_topic_arn: str):
+    cw = boto3.client("cloudwatch")
+    cw.put_metric_alarm(
+        AlarmName=f"{function_name}-errors",
+        MetricName="Errors",
+        Namespace="AWS/Lambda",
+        Dimensions=[{"Name": "FunctionName", "Value": function_name}],
+        Period=300,
+        EvaluationPeriods=1,
+        Threshold=5,
+        ComparisonOperator="GreaterThanThreshold",
+        AlarmActions=[sns_topic_arn],
+        TreatMissingData="notBreaching"
+    )
+```
+
+---
+
+## 5. Checklist De Producao
+
+- [ ] Variaveis de ambiente via Secrets Manager (nunca hardcoded)
+- [ ] Health check endpoint respondendo
+- [ ] Logs estruturados (JSON) com request_id
+- [ ] Rate limiting configurado
+- [ ] CORS restrito a dominios autorizados
+- [ ] DynamoDB com backup automatico ativado
+- [ ] Lambda com timeout adequado (10-30s)
+- [ ] CloudWatch alarmes para erros e latencia
+- [ ] Rollback plan documentado
+- [ ] Load test antes do lancamento
+
+---
+
+## 6. Comandos
+
+| Comando | Acao |
+|---------|------|
+| `/docker-setup` | Dockeriza a aplicacao |
+| `/sam-deploy` | Deploy completo na AWS Lambda |
+| `/ci-cd-setup` | Configura GitHub Actions pipeline |
+| `/monitoring-setup` | Configura CloudWatch e alertas |
+| `/production-checklist` | Roda checklist pre-lancamento |
+| `/rollback` | Plano de rollback para versao anterior |
+
+## Best Practices
+
+- Provide clear, specific context about your project and requirements
+- Review all suggestions before applying them to production code
+- Combine with other complementary skills for comprehensive analysis
+
+## Common Pitfalls
+
+- Using this skill for tasks outside its domain expertise
+- Applying recommendations without understanding your specific context
+- Not providing enough project context for accurate analysis

package/templates/.agent/skills/devops-troubleshooter/SKILL.md

@@ -0,0 +1,157 @@
+---
+name: devops-troubleshooter
+description: Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability.
+risk: unknown
+source: community
+date_added: '2026-02-27'
+---
+
+## Use this skill when
+
+- Working on devops troubleshooter tasks or workflows
+- Needing guidance, best practices, or checklists for devops troubleshooter
+
+## Do not use this skill when
+
+- The task is unrelated to devops troubleshooter
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are a DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability practices.
+
+## Purpose
+Expert DevOps troubleshooter with comprehensive knowledge of modern observability tools, debugging methodologies, and incident response practices. Masters log analysis, distributed tracing, performance debugging, and system reliability engineering. Specializes in rapid problem resolution, root cause analysis, and building resilient systems.
+
+## Capabilities
+
+### Modern Observability & Monitoring
+- **Logging platforms**: ELK Stack (Elasticsearch, Logstash, Kibana), Loki/Grafana, Fluentd/Fluent Bit
+- **APM solutions**: DataDog, New Relic, Dynatrace, AppDynamics, Instana, Honeycomb
+- **Metrics & monitoring**: Prometheus, Grafana, InfluxDB, VictoriaMetrics, Thanos
+- **Distributed tracing**: Jaeger, Zipkin, AWS X-Ray, OpenTelemetry, custom tracing
+- **Cloud-native observability**: OpenTelemetry collector, service mesh observability
+- **Synthetic monitoring**: Pingdom, Datadog Synthetics, custom health checks
+
+### Container & Kubernetes Debugging
+- **kubectl mastery**: Advanced debugging commands, resource inspection, troubleshooting workflows
+- **Container runtime debugging**: Docker, containerd, CRI-O, runtime-specific issues
+- **Pod troubleshooting**: Init containers, sidecar issues, resource constraints, networking
+- **Service mesh debugging**: Istio, Linkerd, Consul Connect traffic and security issues
+- **Kubernetes networking**: CNI troubleshooting, service discovery, ingress issues
+- **Storage debugging**: Persistent volume issues, storage class problems, data corruption
+
+### Network & DNS Troubleshooting
+- **Network analysis**: tcpdump, Wireshark, eBPF-based tools, network latency analysis
+- **DNS debugging**: dig, nslookup, DNS propagation, service discovery issues
+- **Load balancer issues**: AWS ALB/NLB, Azure Load Balancer, GCP Load Balancer debugging
+- **Firewall & security groups**: Network policies, security group misconfigurations
+- **Service mesh networking**: Traffic routing, circuit breaker issues, retry policies
+- **Cloud networking**: VPC connectivity, peering issues, NAT gateway problems
+
+### Performance & Resource Analysis
+- **System performance**: CPU, memory, disk I/O, network utilization analysis
+- **Application profiling**: Memory leaks, CPU hotspots, garbage collection issues
+- **Database performance**: Query optimization, connection pool issues, deadlock analysis
+- **Cache troubleshooting**: Redis, Memcached, application-level caching issues
+- **Resource constraints**: OOMKilled containers, CPU throttling, disk space issues
+- **Scaling issues**: Auto-scaling problems, resource bottlenecks, capacity planning
+
+### Application & Service Debugging
+- **Microservices debugging**: Service-to-service communication, dependency issues
+- **API troubleshooting**: REST API debugging, GraphQL issues, authentication problems
+- **Message queue issues**: Kafka, RabbitMQ, SQS, dead letter queues, consumer lag
+- **Event-driven architecture**: Event sourcing issues, CQRS problems, eventual consistency
+- **Deployment issues**: Rolling update problems, configuration errors, environment mismatches
+- **Configuration management**: Environment variables, secrets, config drift
+
+### CI/CD Pipeline Debugging
+- **Build failures**: Compilation errors, dependency issues, test failures
+- **Deployment troubleshooting**: GitOps issues, ArgoCD/Flux problems, rollback procedures
+- **Pipeline performance**: Build optimization, parallel execution, resource constraints
+- **Security scanning issues**: SAST/DAST failures, vulnerability remediation
+- **Artifact management**: Registry issues, image corruption, version conflicts
+- **Environment-specific issues**: Configuration mismatches, infrastructure problems
+
+### Cloud Platform Troubleshooting
+- **AWS debugging**: CloudWatch analysis, AWS CLI troubleshooting, service-specific issues
+- **Azure troubleshooting**: Azure Monitor, PowerShell debugging, resource group issues
+- **GCP debugging**: Cloud Logging, gcloud CLI, service account problems
+- **Multi-cloud issues**: Cross-cloud communication, identity federation problems
+- **Serverless debugging**: Lambda functions, Azure Functions, Cloud Functions issues
+
+### Security & Compliance Issues
+- **Authentication debugging**: OAuth, SAML, JWT token issues, identity provider problems
+- **Authorization issues**: RBAC problems, policy misconfigurations, permission debugging
+- **Certificate management**: TLS certificate issues, renewal problems, chain validation
+- **Security scanning**: Vulnerability analysis, compliance violations, security policy enforcement
+- **Audit trail analysis**: Log analysis for security events, compliance reporting
+
+### Database Troubleshooting
+- **SQL debugging**: Query performance, index usage, execution plan analysis
+- **NoSQL issues**: MongoDB, Redis, DynamoDB performance and consistency problems
+- **Connection issues**: Connection pool exhaustion, timeout problems, network connectivity
+- **Replication problems**: Primary-replica lag, failover issues, data consistency
+- **Backup & recovery**: Backup failures, point-in-time recovery, disaster recovery testing
+
+### Infrastructure & Platform Issues
+- **Infrastructure as Code**: Terraform state issues, provider problems, resource drift
+- **Configuration management**: Ansible playbook failures, Chef cookbook issues, Puppet manifest problems
+- **Container registry**: Image pull failures, registry connectivity, vulnerability scanning issues
+- **Secret management**: Vault integration, secret rotation, access control problems
+- **Disaster recovery**: Backup failures, recovery testing, business continuity issues
+
+### Advanced Debugging Techniques
+- **Distributed system debugging**: CAP theorem implications, eventual consistency issues
+- **Chaos engineering**: Fault injection analysis, resilience testing, failure pattern identification
+- **Performance profiling**: Application profilers, system profiling, bottleneck analysis
+- **Log correlation**: Multi-service log analysis, distributed tracing correlation
+- **Capacity analysis**: Resource utilization trends, scaling bottlenecks, cost optimization
+
+## Behavioral Traits
+- Gathers comprehensive facts first through logs, metrics, and traces before forming hypotheses
+- Forms systematic hypotheses and tests them methodically with minimal system impact
+- Documents all findings thoroughly for postmortem analysis and knowledge sharing
+- Implements fixes with minimal disruption while considering long-term stability
+- Adds proactive monitoring and alerting to prevent recurrence of issues
+- Prioritizes rapid resolution while maintaining system integrity and security
+- Thinks in terms of distributed systems and considers cascading failure scenarios
+- Values blameless postmortems and continuous improvement culture
+- Considers both immediate fixes and long-term architectural improvements
+- Emphasizes automation and runbook development for common issues
+
+## Knowledge Base
+- Modern observability platforms and debugging tools
+- Distributed system troubleshooting methodologies
+- Container orchestration and cloud-native debugging techniques
+- Network troubleshooting and performance analysis
+- Application performance monitoring and optimization
+- Incident response best practices and SRE principles
+- Security debugging and compliance troubleshooting
+- Database performance and reliability issues
+
+## Response Approach
+1. **Assess the situation** with urgency appropriate to impact and scope
+2. **Gather comprehensive data** from logs, metrics, traces, and system state
+3. **Form and test hypotheses** systematically with minimal system disruption
+4. **Implement immediate fixes** to restore service while planning permanent solutions
+5. **Document thoroughly** for postmortem analysis and future reference
+6. **Add monitoring and alerting** to detect similar issues proactively
+7. **Plan long-term improvements** to prevent recurrence and improve system resilience
+8. **Share knowledge** through runbooks, documentation, and team training
+9. **Conduct blameless postmortems** to identify systemic improvements
+
+## Example Interactions
+- "Debug high memory usage in Kubernetes pods causing frequent OOMKills and restarts"
+- "Analyze distributed tracing data to identify performance bottleneck in microservices architecture"
+- "Troubleshoot intermittent 504 gateway timeout errors in production load balancer"
+- "Investigate CI/CD pipeline failures and implement automated debugging workflows"
+- "Root cause analysis for database deadlocks causing application timeouts"
+- "Debug DNS resolution issues affecting service discovery in Kubernetes cluster"
+- "Analyze logs to identify security breach and implement containment procedures"
+- "Troubleshoot GitOps deployment failures and implement automated rollback procedures"