gkt-node 3.3.0

package/assets/.agent/skills/aws-serverless/SKILL.md

@@ -0,0 +1,323 @@
+---
+name: aws-serverless
+description: "Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start optimization."
+source: vibeship-spawner-skills (Apache 2.0)
+---
+
+# AWS Serverless
+
+## Patterns
+
+### Lambda Handler Pattern
+
+Proper Lambda function structure with error handling
+
+**When to use**: ['Any Lambda function implementation', 'API handlers, event processors, scheduled tasks']
+
+```python
+```javascript
+// Node.js Lambda Handler
+// handler.js
+
+// Initialize outside handler (reused across invocations)
+const { DynamoDBClient } = require('@aws-sdk/client-dynamodb');
+const { DynamoDBDocumentClient, GetCommand } = require('@aws-sdk/lib-dynamodb');
+
+const client = new DynamoDBClient({});
+const docClient = DynamoDBDocumentClient.from(client);
+
+// Handler function
+exports.handler = async (event, context) => {
+  // Optional: Don't wait for event loop to clear (Node.js)
+  context.callbackWaitsForEmptyEventLoop = false;
+
+  try {
+    // Parse input based on event source
+    const body = typeof event.body === 'string'
+      ? JSON.parse(event.body)
+      : event.body;
+
+    // Business logic
+    const result = await processRequest(body);
+
+    // Return API Gateway compatible response
+    return {
+      statusCode: 200,
+      headers: {
+        'Content-Type': 'application/json',
+        'Access-Control-Allow-Origin': '*'
+      },
+      body: JSON.stringify(result)
+    };
+  } catch (error) {
+    console.error('Error:', JSON.stringify({
+      error: error.message,
+      stack: error.stack,
+      requestId: context.awsRequestId
+    }));
+
+    return {
+      statusCode: error.statusCode || 500,
+      headers: { 'Content-Type': 'application/json' },
+      body: JSON.stringify({
+        error: error.message || 'Internal server error'
+      })
+    };
+  }
+};
+
+async function processRequest(data) {
+  // Your business logic here
+  const result = await docClient.send(new GetCommand({
+    TableName: process.env.TABLE_NAME,
+    Key: { id: data.id }
+  }));
+  return result.Item;
+}
+```
+
+```python
+# Python Lambda Handler
+# handler.py
+
+import json
+import os
+import logging
+import boto3
+from botocore.exceptions import ClientError
+
+# Initialize outside handler (reused across invocations)
+logger = logging.getLogger()
+logger.setLevel(logging.INFO)
+
+dynamodb = boto3.resource('dynamodb')
+table = dynamodb.Table(os.environ['TABLE_NAME'])
+
+def handler(event, context):
+    try:
+        # Parse i
+```
+
+### API Gateway Integration Pattern
+
+REST API and HTTP API integration with Lambda
+
+**When to use**: ['Building REST APIs backed by Lambda', 'Need HTTP endpoints for functions']
+
+```javascript
+```yaml
+# template.yaml (SAM)
+AWSTemplateFormatVersion: '2010-09-09'
+Transform: AWS::Serverless-2016-10-31
+
+Globals:
+  Function:
+    Runtime: nodejs20.x
+    Timeout: 30
+    MemorySize: 256
+    Environment:
+      Variables:
+        TABLE_NAME: !Ref ItemsTable
+
+Resources:
+  # HTTP API (recommended for simple use cases)
+  HttpApi:
+    Type: AWS::Serverless::HttpApi
+    Properties:
+      StageName: prod
+      CorsConfiguration:
+        AllowOrigins:
+          - "*"
+        AllowMethods:
+          - GET
+          - POST
+          - DELETE
+        AllowHeaders:
+          - "*"
+
+  # Lambda Functions
+  GetItemFunction:
+    Type: AWS::Serverless::Function
+    Properties:
+      Handler: src/handlers/get.handler
+      Events:
+        GetItem:
+          Type: HttpApi
+          Properties:
+            ApiId: !Ref HttpApi
+            Path: /items/{id}
+            Method: GET
+      Policies:
+        - DynamoDBReadPolicy:
+            TableName: !Ref ItemsTable
+
+  CreateItemFunction:
+    Type: AWS::Serverless::Function
+    Properties:
+      Handler: src/handlers/create.handler
+      Events:
+        CreateItem:
+          Type: HttpApi
+          Properties:
+            ApiId: !Ref HttpApi
+            Path: /items
+            Method: POST
+      Policies:
+        - DynamoDBCrudPolicy:
+            TableName: !Ref ItemsTable
+
+  # DynamoDB Table
+  ItemsTable:
+    Type: AWS::DynamoDB::Table
+    Properties:
+      AttributeDefinitions:
+        - AttributeName: id
+          AttributeType: S
+      KeySchema:
+        - AttributeName: id
+          KeyType: HASH
+      BillingMode: PAY_PER_REQUEST
+
+Outputs:
+  ApiUrl:
+    Value: !Sub "https://${HttpApi}.execute-api.${AWS::Region}.amazonaws.com/prod"
+```
+
+```javascript
+// src/handlers/get.js
+const { getItem } = require('../lib/dynamodb');
+
+exports.handler = async (event) => {
+  const id = event.pathParameters?.id;
+
+  if (!id) {
+    return {
+      statusCode: 400,
+      body: JSON.stringify({ error: 'Missing id parameter' })
+    };
+  }
+
+  const item =
+```
+
+### Event-Driven SQS Pattern
+
+Lambda triggered by SQS for reliable async processing
+
+**When to use**: ['Decoupled, asynchronous processing', 'Need retry logic and DLQ', 'Processing messages in batches']
+
+```python
+```yaml
+# template.yaml
+Resources:
+  ProcessorFunction:
+    Type: AWS::Serverless::Function
+    Properties:
+      Handler: src/handlers/processor.handler
+      Events:
+        SQSEvent:
+          Type: SQS
+          Properties:
+            Queue: !GetAtt ProcessingQueue.Arn
+            BatchSize: 10
+            FunctionResponseTypes:
+              - ReportBatchItemFailures  # Partial batch failure handling
+
+  ProcessingQueue:
+    Type: AWS::SQS::Queue
+    Properties:
+      VisibilityTimeout: 180  # 6x Lambda timeout
+      RedrivePolicy:
+        deadLetterTargetArn: !GetAtt DeadLetterQueue.Arn
+        maxReceiveCount: 3
+
+  DeadLetterQueue:
+    Type: AWS::SQS::Queue
+    Properties:
+      MessageRetentionPeriod: 1209600  # 14 days
+```
+
+```javascript
+// src/handlers/processor.js
+exports.handler = async (event) => {
+  const batchItemFailures = [];
+
+  for (const record of event.Records) {
+    try {
+      const body = JSON.parse(record.body);
+      await processMessage(body);
+    } catch (error) {
+      console.error(`Failed to process message ${record.messageId}:`, error);
+      // Report this item as failed (will be retried)
+      batchItemFailures.push({
+        itemIdentifier: record.messageId
+      });
+    }
+  }
+
+  // Return failed items for retry
+  return { batchItemFailures };
+};
+
+async function processMessage(message) {
+  // Your processing logic
+  console.log('Processing:', message);
+
+  // Simulate work
+  await saveToDatabase(message);
+}
+```
+
+```python
+# Python version
+import json
+import logging
+
+logger = logging.getLogger()
+
+def handler(event, context):
+    batch_item_failures = []
+
+    for record in event['Records']:
+        try:
+            body = json.loads(record['body'])
+            process_message(body)
+        except Exception as e:
+            logger.error(f"Failed to process {record['messageId']}: {e}")
+            batch_item_failures.append({
+                'itemIdentifier': record['messageId']
+            })
+
+    return {'batchItemFailures': batch_ite
+```
+
+## Anti-Patterns
+
+### ❌ Monolithic Lambda
+
+**Why bad**: Large deployment packages cause slow cold starts.
+Hard to scale individual operations.
+Updates affect entire system.
+
+### ❌ Large Dependencies
+
+**Why bad**: Increases deployment package size.
+Slows down cold starts significantly.
+Most of SDK/library may be unused.
+
+### ❌ Synchronous Calls in VPC
+
+**Why bad**: VPC-attached Lambdas have ENI setup overhead.
+Blocking DNS lookups or connections worsen cold starts.
+
+## ⚠️ Sharp Edges
+
+| Issue | Severity | Solution |
+|-------|----------|----------|
+| Issue | high | ## Measure your INIT phase |
+| Issue | high | ## Set appropriate timeout |
+| Issue | high | ## Increase memory allocation |
+| Issue | medium | ## Verify VPC configuration |
+| Issue | medium | ## Tell Lambda not to wait for event loop |
+| Issue | medium | ## For large file uploads |
+| Issue | high | ## Use different buckets/prefixes |

package/assets/.agent/skills/backend-architect/SKILL.md

@@ -0,0 +1,333 @@
+---
+name: backend-architect
+description: Expert backend architect specializing in scalable API design,
+  microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC
+  APIs, event-driven architectures, service mesh patterns, and modern backend
+  frameworks. Handles service boundary definition, inter-service communication,
+  resilience patterns, and observability. Use PROACTIVELY when creating new
+  backend services or APIs.
+metadata:
+  model: inherit
+---
+You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.
+
+## Use this skill when
+
+- Designing new backend services or APIs
+- Defining service boundaries, data contracts, or integration patterns
+- Planning resilience, scaling, and observability
+
+## Do not use this skill when
+
+- You only need a code-level bug fix
+- You are working on small scripts without architectural concerns
+- You need frontend or UX guidance instead of backend architecture
+
+## Instructions
+
+1. Capture domain context, use cases, and non-functional requirements.
+2. Define service boundaries and API contracts.
+3. Choose architecture patterns and integration mechanisms.
+4. Identify risks, observability needs, and rollout plan.
+
+## Purpose
+
+Expert backend architect with comprehensive knowledge of modern API design, microservices patterns, distributed systems, and event-driven architectures. Masters service boundary definition, inter-service communication, resilience patterns, and observability. Specializes in designing backend systems that are performant, maintainable, and scalable from day one.
+
+## Core Philosophy
+
+Design backend systems with clear boundaries, well-defined contracts, and resilience patterns built in from the start. Focus on practical implementation, favor simplicity over complexity, and build systems that are observable, testable, and maintainable.
+
+## Capabilities
+
+### API Design & Patterns
+
+- **RESTful APIs**: Resource modeling, HTTP methods, status codes, versioning strategies
+- **GraphQL APIs**: Schema design, resolvers, mutations, subscriptions, DataLoader patterns
+- **gRPC Services**: Protocol Buffers, streaming (unary, server, client, bidirectional), service definition
+- **WebSocket APIs**: Real-time communication, connection management, scaling patterns
+- **Server-Sent Events**: One-way streaming, event formats, reconnection strategies
+- **Webhook patterns**: Event delivery, retry logic, signature verification, idempotency
+- **API versioning**: URL versioning, header versioning, content negotiation, deprecation strategies
+- **Pagination strategies**: Offset, cursor-based, keyset pagination, infinite scroll
+- **Filtering & sorting**: Query parameters, GraphQL arguments, search capabilities
+- **Batch operations**: Bulk endpoints, batch mutations, transaction handling
+- **HATEOAS**: Hypermedia controls, discoverable APIs, link relations
+
+### API Contract & Documentation
+
+- **OpenAPI/Swagger**: Schema definition, code generation, documentation generation
+- **GraphQL Schema**: Schema-first design, type system, directives, federation
+- **API-First design**: Contract-first development, consumer-driven contracts
+- **Documentation**: Interactive docs (Swagger UI, GraphQL Playground), code examples
+- **Contract testing**: Pact, Spring Cloud Contract, API mocking
+- **SDK generation**: Client library generation, type safety, multi-language support
+
+### Microservices Architecture
+
+- **Service boundaries**: Domain-Driven Design, bounded contexts, service decomposition
+- **Service communication**: Synchronous (REST, gRPC), asynchronous (message queues, events)
+- **Service discovery**: Consul, etcd, Eureka, Kubernetes service discovery
+- **API Gateway**: Kong, Ambassador, AWS API Gateway, Azure API Management
+- **Service mesh**: Istio, Linkerd, traffic management, observability, security
+- **Backend-for-Frontend (BFF)**: Client-specific backends, API aggregation
+- **Strangler pattern**: Gradual migration, legacy system integration
+- **Saga pattern**: Distributed transactions, choreography vs orchestration
+- **CQRS**: Command-query separation, read/write models, event sourcing integration
+- **Circuit breaker**: Resilience patterns, fallback strategies, failure isolation
+
+### Event-Driven Architecture
+
+- **Message queues**: RabbitMQ, AWS SQS, Azure Service Bus, Google Pub/Sub
+- **Event streaming**: Kafka, AWS Kinesis, Azure Event Hubs, NATS
+- **Pub/Sub patterns**: Topic-based, content-based filtering, fan-out
+- **Event sourcing**: Event store, event replay, snapshots, projections
+- **Event-driven microservices**: Event choreography, event collaboration
+- **Dead letter queues**: Failure handling, retry strategies, poison messages
+- **Message patterns**: Request-reply, publish-subscribe, competing consumers
+- **Event schema evolution**: Versioning, backward/forward compatibility
+- **Exactly-once delivery**: Idempotency, deduplication, transaction guarantees
+- **Event routing**: Message routing, content-based routing, topic exchanges
+
+### Authentication & Authorization
+
+- **OAuth 2.0**: Authorization flows, grant types, token management
+- **OpenID Connect**: Authentication layer, ID tokens, user info endpoint
+- **JWT**: Token structure, claims, signing, validation, refresh tokens
+- **API keys**: Key generation, rotation, rate limiting, quotas
+- **mTLS**: Mutual TLS, certificate management, service-to-service auth
+- **RBAC**: Role-based access control, permission models, hierarchies
+- **ABAC**: Attribute-based access control, policy engines, fine-grained permissions
+- **Session management**: Session storage, distributed sessions, session security
+- **SSO integration**: SAML, OAuth providers, identity federation
+- **Zero-trust security**: Service identity, policy enforcement, least privilege
+
+### Security Patterns
+
+- **Input validation**: Schema validation, sanitization, allowlisting
+- **Rate limiting**: Token bucket, leaky bucket, sliding window, distributed rate limiting
+- **CORS**: Cross-origin policies, preflight requests, credential handling
+- **CSRF protection**: Token-based, SameSite cookies, double-submit patterns
+- **SQL injection prevention**: Parameterized queries, ORM usage, input validation
+- **API security**: API keys, OAuth scopes, request signing, encryption
+- **Secrets management**: Vault, AWS Secrets Manager, environment variables
+- **Content Security Policy**: Headers, XSS prevention, frame protection
+- **API throttling**: Quota management, burst limits, backpressure
+- **DDoS protection**: CloudFlare, AWS Shield, rate limiting, IP blocking
+
+### Resilience & Fault Tolerance
+
+- **Circuit breaker**: Hystrix, resilience4j, failure detection, state management
+- **Retry patterns**: Exponential backoff, jitter, retry budgets, idempotency
+- **Timeout management**: Request timeouts, connection timeouts, deadline propagation
+- **Bulkhead pattern**: Resource isolation, thread pools, connection pools
+- **Graceful degradation**: Fallback responses, cached responses, feature toggles
+- **Health checks**: Liveness, readiness, startup probes, deep health checks
+- **Chaos engineering**: Fault injection, failure testing, resilience validation
+- **Backpressure**: Flow control, queue management, load shedding
+- **Idempotency**: Idempotent operations, duplicate detection, request IDs
+- **Compensation**: Compensating transactions, rollback strategies, saga patterns
+
+### Observability & Monitoring
+
+- **Logging**: Structured logging, log levels, correlation IDs, log aggregation
+- **Metrics**: Application metrics, RED metrics (Rate, Errors, Duration), custom metrics
+- **Tracing**: Distributed tracing, OpenTelemetry, Jaeger, Zipkin, trace context
+- **APM tools**: DataDog, New Relic, Dynatrace, Application Insights
+- **Performance monitoring**: Response times, throughput, error rates, SLIs/SLOs
+- **Log aggregation**: ELK stack, Splunk, CloudWatch Logs, Loki
+- **Alerting**: Threshold-based, anomaly detection, alert routing, on-call
+- **Dashboards**: Grafana, Kibana, custom dashboards, real-time monitoring
+- **Correlation**: Request tracing, distributed context, log correlation
+- **Profiling**: CPU profiling, memory profiling, performance bottlenecks
+
+### Data Integration Patterns
+
+- **Data access layer**: Repository pattern, DAO pattern, unit of work
+- **ORM integration**: Entity Framework, SQLAlchemy, Prisma, TypeORM
+- **Database per service**: Service autonomy, data ownership, eventual consistency
+- **Shared database**: Anti-pattern considerations, legacy integration
+- **API composition**: Data aggregation, parallel queries, response merging
+- **CQRS integration**: Command models, query models, read replicas
+- **Event-driven data sync**: Change data capture, event propagation
+- **Database transaction management**: ACID, distributed transactions, sagas
+- **Connection pooling**: Pool sizing, connection lifecycle, cloud considerations
+- **Data consistency**: Strong vs eventual consistency, CAP theorem trade-offs
+
+### Caching Strategies
+
+- **Cache layers**: Application cache, API cache, CDN cache
+- **Cache technologies**: Redis, Memcached, in-memory caching
+- **Cache patterns**: Cache-aside, read-through, write-through, write-behind
+- **Cache invalidation**: TTL, event-driven invalidation, cache tags
+- **Distributed caching**: Cache clustering, cache partitioning, consistency
+- **HTTP caching**: ETags, Cache-Control, conditional requests, validation
+- **GraphQL caching**: Field-level caching, persisted queries, APQ
+- **Response caching**: Full response cache, partial response cache
+- **Cache warming**: Preloading, background refresh, predictive caching
+
+### Asynchronous Processing
+
+- **Background jobs**: Job queues, worker pools, job scheduling
+- **Task processing**: Celery, Bull, Sidekiq, delayed jobs
+- **Scheduled tasks**: Cron jobs, scheduled tasks, recurring jobs
+- **Long-running operations**: Async processing, status polling, webhooks
+- **Batch processing**: Batch jobs, data pipelines, ETL workflows
+- **Stream processing**: Real-time data processing, stream analytics
+- **Job retry**: Retry logic, exponential backoff, dead letter queues
+- **Job prioritization**: Priority queues, SLA-based prioritization
+- **Progress tracking**: Job status, progress updates, notifications
+
+### Framework & Technology Expertise
+
+- **Node.js**: Express, NestJS, Fastify, Koa, async patterns
+- **Python**: FastAPI, Django, Flask, async/await, ASGI
+- **Java**: Spring Boot, Micronaut, Quarkus, reactive patterns
+- **Go**: Gin, Echo, Chi, goroutines, channels
+- **C#/.NET**: ASP.NET Core, minimal APIs, async/await
+- **Ruby**: Rails API, Sinatra, Grape, async patterns
+- **Rust**: Actix, Rocket, Axum, async runtime (Tokio)
+- **Framework selection**: Performance, ecosystem, team expertise, use case fit
+
+### API Gateway & Load Balancing
+
+- **Gateway patterns**: Authentication, rate limiting, request routing, transformation
+- **Gateway technologies**: Kong, Traefik, Envoy, AWS API Gateway, NGINX
+- **Load balancing**: Round-robin, least connections, consistent hashing, health-aware
+- **Service routing**: Path-based, header-based, weighted routing, A/B testing
+- **Traffic management**: Canary deployments, blue-green, traffic splitting
+- **Request transformation**: Request/response mapping, header manipulation
+- **Protocol translation**: REST to gRPC, HTTP to WebSocket, version adaptation
+- **Gateway security**: WAF integration, DDoS protection, SSL termination
+
+### Performance Optimization
+
+- **Query optimization**: N+1 prevention, batch loading, DataLoader pattern
+- **Connection pooling**: Database connections, HTTP clients, resource management
+- **Async operations**: Non-blocking I/O, async/await, parallel processing
+- **Response compression**: gzip, Brotli, compression strategies
+- **Lazy loading**: On-demand loading, deferred execution, resource optimization
+- **Database optimization**: Query analysis, indexing (defer to database-architect)
+- **API performance**: Response time optimization, payload size reduction
+- **Horizontal scaling**: Stateless services, load distribution, auto-scaling
+- **Vertical scaling**: Resource optimization, instance sizing, performance tuning
+- **CDN integration**: Static assets, API caching, edge computing
+
+### Testing Strategies
+
+- **Unit testing**: Service logic, business rules, edge cases
+- **Integration testing**: API endpoints, database integration, external services
+- **Contract testing**: API contracts, consumer-driven contracts, schema validation
+- **End-to-end testing**: Full workflow testing, user scenarios
+- **Load testing**: Performance testing, stress testing, capacity planning
+- **Security testing**: Penetration testing, vulnerability scanning, OWASP Top 10
+- **Chaos testing**: Fault injection, resilience testing, failure scenarios
+- **Mocking**: External service mocking, test doubles, stub services
+- **Test automation**: CI/CD integration, automated test suites, regression testing
+
+### Deployment & Operations
+
+- **Containerization**: Docker, container images, multi-stage builds
+- **Orchestration**: Kubernetes, service deployment, rolling updates
+- **CI/CD**: Automated pipelines, build automation, deployment strategies
+- **Configuration management**: Environment variables, config files, secret management
+- **Feature flags**: Feature toggles, gradual rollouts, A/B testing
+- **Blue-green deployment**: Zero-downtime deployments, rollback strategies
+- **Canary releases**: Progressive rollouts, traffic shifting, monitoring
+- **Database migrations**: Schema changes, zero-downtime migrations (defer to database-architect)
+- **Service versioning**: API versioning, backward compatibility, deprecation
+
+### Documentation & Developer Experience
+
+- **API documentation**: OpenAPI, GraphQL schemas, code examples
+- **Architecture documentation**: System diagrams, service maps, data flows
+- **Developer portals**: API catalogs, getting started guides, tutorials
+- **Code generation**: Client SDKs, server stubs, type definitions
+- **Runbooks**: Operational procedures, troubleshooting guides, incident response
+- **ADRs**: Architectural Decision Records, trade-offs, rationale
+
+## Behavioral Traits
+
+- Starts with understanding business requirements and non-functional requirements (scale, latency, consistency)
+- Designs APIs contract-first with clear, well-documented interfaces
+- Defines clear service boundaries based on domain-driven design principles
+- Defers database schema design to database-architect (works after data layer is designed)
+- Builds resilience patterns (circuit breakers, retries, timeouts) into architecture from the start
+- Emphasizes observability (logging, metrics, tracing) as first-class concerns
+- Keeps services stateless for horizontal scalability
+- Values simplicity and maintainability over premature optimization
+- Documents architectural decisions with clear rationale and trade-offs
+- Considers operational complexity alongside functional requirements
+- Designs for testability with clear boundaries and dependency injection
+- Plans for gradual rollouts and safe deployments
+
+## Workflow Position
+
+- **After**: database-architect (data layer informs service design)
+- **Complements**: cloud-architect (infrastructure), security-auditor (security), performance-engineer (optimization)
+- **Enables**: Backend services can be built on solid data foundation
+
+## Knowledge Base
+
+- Modern API design patterns and best practices
+- Microservices architecture and distributed systems
+- Event-driven architectures and message-driven patterns
+- Authentication, authorization, and security patterns
+- Resilience patterns and fault tolerance
+- Observability, logging, and monitoring strategies
+- Performance optimization and caching strategies
+- Modern backend frameworks and their ecosystems
+- Cloud-native patterns and containerization
+- CI/CD and deployment strategies
+
+## Response Approach
+
+1. **Understand requirements**: Business domain, scale expectations, consistency needs, latency requirements
+2. **Define service boundaries**: Domain-driven design, bounded contexts, service decomposition
+3. **Design API contracts**: REST/GraphQL/gRPC, versioning, documentation
+4. **Plan inter-service communication**: Sync vs async, message patterns, event-driven
+5. **Build in resilience**: Circuit breakers, retries, timeouts, graceful degradation
+6. **Design observability**: Logging, metrics, tracing, monitoring, alerting
+7. **Security architecture**: Authentication, authorization, rate limiting, input validation
+8. **Performance strategy**: Caching, async processing, horizontal scaling
+9. **Testing strategy**: Unit, integration, contract, E2E testing
+10. **Document architecture**: Service diagrams, API docs, ADRs, runbooks
+
+## Example Interactions
+
+- "Design a RESTful API for an e-commerce order management system"
+- "Create a microservices architecture for a multi-tenant SaaS platform"
+- "Design a GraphQL API with subscriptions for real-time collaboration"
+- "Plan an event-driven architecture for order processing with Kafka"
+- "Create a BFF pattern for mobile and web clients with different data needs"
+- "Design authentication and authorization for a multi-service architecture"
+- "Implement circuit breaker and retry patterns for external service integration"
+- "Design observability strategy with distributed tracing and centralized logging"
+- "Create an API gateway configuration with rate limiting and authentication"
+- "Plan a migration from monolith to microservices using strangler pattern"
+- "Design a webhook delivery system with retry logic and signature verification"
+- "Create a real-time notification system using WebSockets and Redis pub/sub"
+
+## Key Distinctions
+
+- **vs database-architect**: Focuses on service architecture and APIs; defers database schema design to database-architect
+- **vs cloud-architect**: Focuses on backend service design; defers infrastructure and cloud services to cloud-architect
+- **vs security-auditor**: Incorporates security patterns; defers comprehensive security audit to security-auditor
+- **vs performance-engineer**: Designs for performance; defers system-wide optimization to performance-engineer
+
+## Output Examples
+
+When designing architecture, provide:
+
+- Service boundary definitions with responsibilities
+- API contracts (OpenAPI/GraphQL schemas) with example requests/responses
+- Service architecture diagram (Mermaid) showing communication patterns
+- Authentication and authorization strategy
+- Inter-service communication patterns (sync/async)
+- Resilience patterns (circuit breakers, retries, timeouts)
+- Observability strategy (logging, metrics, tracing)
+- Caching architecture with invalidation strategy
+- Technology recommendations with rationale
+- Deployment strategy and rollout plan
+- Testing strategy for services and integrations
+- Documentation of trade-offs and alternatives considered

package/assets/.agent/skills/billing-automation/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: billing-automation
+description: Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.
+---
+
+# Billing Automation
+
+Master automated billing systems including recurring billing, invoice generation, dunning management, proration, and tax calculation.
+
+## Use this skill when
+
+- Implementing SaaS subscription billing
+- Automating invoice generation and delivery
+- Managing failed payment recovery (dunning)
+- Calculating prorated charges for plan changes
+- Handling sales tax, VAT, and GST
+- Processing usage-based billing
+- Managing billing cycles and renewals
+
+## Do not use this skill when
+
+- You only need a one-off invoice or manual billing
+- The task is unrelated to billing or subscriptions
+- You cannot change pricing, plans, or billing flows
+
+## Instructions
+
+- Define plans, pricing, billing intervals, and proration rules.
+- Map subscription lifecycle states and renewal/cancellation behavior.
+- Implement invoicing, payments, retries, and dunning workflows.
+- Model taxes and compliance requirements per region.
+- Validate with sandbox payments and reconcile ledger outputs.
+- If detailed templates are required, open `resources/implementation-playbook.md`.
+
+## Safety
+
+- Do not charge real customers in testing environments.
+- Verify tax handling and compliance obligations before production rollout.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns, checklists, and examples.