@ruaruababa/vibe-kit 1.0.0

package/skills/distributed-tracing/SKILL.md

@@ -0,0 +1,450 @@
+---
+name: distributed-tracing
+description: Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
+---
+
+# Distributed Tracing
+
+Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices.
+
+## Do not use this skill when
+
+- The task is unrelated to distributed tracing
+- 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`.
+
+## Purpose
+
+Track requests across distributed systems to understand latency, dependencies, and failure points.
+
+## Use this skill when
+
+- Debug latency issues
+- Understand service dependencies
+- Identify bottlenecks
+- Trace error propagation
+- Analyze request paths
+
+## Distributed Tracing Concepts
+
+### Trace Structure
+```
+Trace (Request ID: abc123)
+  ↓
+Span (frontend) [100ms]
+  ↓
+Span (api-gateway) [80ms]
+  ├→ Span (auth-service) [10ms]
+  └→ Span (user-service) [60ms]
+      └→ Span (database) [40ms]
+```
+
+### Key Components
+- **Trace** - End-to-end request journey
+- **Span** - Single operation within a trace
+- **Context** - Metadata propagated between services
+- **Tags** - Key-value pairs for filtering
+- **Logs** - Timestamped events within a span
+
+## Jaeger Setup
+
+### Kubernetes Deployment
+
+```bash
+# Deploy Jaeger Operator
+kubectl create namespace observability
+kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/download/v1.51.0/jaeger-operator.yaml -n observability
+
+# Deploy Jaeger instance
+kubectl apply -f - <<EOF
+apiVersion: jaegertracing.io/v1
+kind: Jaeger
+metadata:
+  name: jaeger
+  namespace: observability
+spec:
+  strategy: production
+  storage:
+    type: elasticsearch
+    options:
+      es:
+        server-urls: http://elasticsearch:9200
+  ingress:
+    enabled: true
+EOF
+```
+
+### Docker Compose
+
+```yaml
+version: '3.8'
+services:
+  jaeger:
+    image: jaegertracing/all-in-one:latest
+    ports:
+      - "5775:5775/udp"
+      - "6831:6831/udp"
+      - "6832:6832/udp"
+      - "5778:5778"
+      - "16686:16686"  # UI
+      - "14268:14268"  # Collector
+      - "14250:14250"  # gRPC
+      - "9411:9411"    # Zipkin
+    environment:
+      - COLLECTOR_ZIPKIN_HOST_PORT=:9411
+```
+
+**Reference:** See `references/jaeger-setup.md`
+
+## Application Instrumentation
+
+### OpenTelemetry (Recommended)
+
+#### Python (Flask)
+```python
+from opentelemetry import trace
+from opentelemetry.exporter.jaeger.thrift import JaegerExporter
+from opentelemetry.sdk.resources import SERVICE_NAME, Resource
+from opentelemetry.sdk.trace import TracerProvider
+from opentelemetry.sdk.trace.export import BatchSpanProcessor
+from opentelemetry.instrumentation.flask import FlaskInstrumentor
+from flask import Flask
+
+# Initialize tracer
+resource = Resource(attributes={SERVICE_NAME: "my-service"})
+provider = TracerProvider(resource=resource)
+processor = BatchSpanProcessor(JaegerExporter(
+    agent_host_name="jaeger",
+    agent_port=6831,
+))
+provider.add_span_processor(processor)
+trace.set_tracer_provider(provider)
+
+# Instrument Flask
+app = Flask(__name__)
+FlaskInstrumentor().instrument_app(app)
+
+@app.route('/api/users')
+def get_users():
+    tracer = trace.get_tracer(__name__)
+
+    with tracer.start_as_current_span("get_users") as span:
+        span.set_attribute("user.count", 100)
+        # Business logic
+        users = fetch_users_from_db()
+        return {"users": users}
+
+def fetch_users_from_db():
+    tracer = trace.get_tracer(__name__)
+
+    with tracer.start_as_current_span("database_query") as span:
+        span.set_attribute("db.system", "postgresql")
+        span.set_attribute("db.statement", "SELECT * FROM users")
+        # Database query
+        return query_database()
+```
+
+#### Node.js (Express)
+```javascript
+const { NodeTracerProvider } = require('@opentelemetry/sdk-trace-node');
+const { JaegerExporter } = require('@opentelemetry/exporter-jaeger');
+const { BatchSpanProcessor } = require('@opentelemetry/sdk-trace-base');
+const { registerInstrumentations } = require('@opentelemetry/instrumentation');
+const { HttpInstrumentation } = require('@opentelemetry/instrumentation-http');
+const { ExpressInstrumentation } = require('@opentelemetry/instrumentation-express');
+
+// Initialize tracer
+const provider = new NodeTracerProvider({
+  resource: { attributes: { 'service.name': 'my-service' } }
+});
+
+const exporter = new JaegerExporter({
+  endpoint: 'http://jaeger:14268/api/traces'
+});
+
+provider.addSpanProcessor(new BatchSpanProcessor(exporter));
+provider.register();
+
+// Instrument libraries
+registerInstrumentations({
+  instrumentations: [
+    new HttpInstrumentation(),
+    new ExpressInstrumentation(),
+  ],
+});
+
+const express = require('express');
+const app = express();
+
+app.get('/api/users', async (req, res) => {
+  const tracer = trace.getTracer('my-service');
+  const span = tracer.startSpan('get_users');
+
+  try {
+    const users = await fetchUsers();
+    span.setAttributes({ 'user.count': users.length });
+    res.json({ users });
+  } finally {
+    span.end();
+  }
+});
+```
+
+#### Go
+```go
+package main
+
+import (
+    "context"
+    "go.opentelemetry.io/otel"
+    "go.opentelemetry.io/otel/exporters/jaeger"
+    "go.opentelemetry.io/otel/sdk/resource"
+    sdktrace "go.opentelemetry.io/otel/sdk/trace"
+    semconv "go.opentelemetry.io/otel/semconv/v1.4.0"
+)
+
+func initTracer() (*sdktrace.TracerProvider, error) {
+    exporter, err := jaeger.New(jaeger.WithCollectorEndpoint(
+        jaeger.WithEndpoint("http://jaeger:14268/api/traces"),
+    ))
+    if err != nil {
+        return nil, err
+    }
+
+    tp := sdktrace.NewTracerProvider(
+        sdktrace.WithBatcher(exporter),
+        sdktrace.WithResource(resource.NewWithAttributes(
+            semconv.SchemaURL,
+            semconv.ServiceNameKey.String("my-service"),
+        )),
+    )
+
+    otel.SetTracerProvider(tp)
+    return tp, nil
+}
+
+func getUsers(ctx context.Context) ([]User, error) {
+    tracer := otel.Tracer("my-service")
+    ctx, span := tracer.Start(ctx, "get_users")
+    defer span.End()
+
+    span.SetAttributes(attribute.String("user.filter", "active"))
+
+    users, err := fetchUsersFromDB(ctx)
+    if err != nil {
+        span.RecordError(err)
+        return nil, err
+    }
+
+    span.SetAttributes(attribute.Int("user.count", len(users)))
+    return users, nil
+}
+```
+
+**Reference:** See `references/instrumentation.md`
+
+## Context Propagation
+
+### HTTP Headers
+```
+traceparent: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01
+tracestate: congo=t61rcWkgMzE
+```
+
+### Propagation in HTTP Requests
+
+#### Python
+```python
+from opentelemetry.propagate import inject
+
+headers = {}
+inject(headers)  # Injects trace context
+
+response = requests.get('http://downstream-service/api', headers=headers)
+```
+
+#### Node.js
+```javascript
+const { propagation } = require('@opentelemetry/api');
+
+const headers = {};
+propagation.inject(context.active(), headers);
+
+axios.get('http://downstream-service/api', { headers });
+```
+
+## Tempo Setup (Grafana)
+
+### Kubernetes Deployment
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: tempo-config
+data:
+  tempo.yaml: |
+    server:
+      http_listen_port: 3200
+
+    distributor:
+      receivers:
+        jaeger:
+          protocols:
+            thrift_http:
+            grpc:
+        otlp:
+          protocols:
+            http:
+            grpc:
+
+    storage:
+      trace:
+        backend: s3
+        s3:
+          bucket: tempo-traces
+          endpoint: s3.amazonaws.com
+
+    querier:
+      frontend_worker:
+        frontend_address: tempo-query-frontend:9095
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: tempo
+spec:
+  replicas: 1
+  template:
+    spec:
+      containers:
+      - name: tempo
+        image: grafana/tempo:latest
+        args:
+          - -config.file=/etc/tempo/tempo.yaml
+        volumeMounts:
+        - name: config
+          mountPath: /etc/tempo
+      volumes:
+      - name: config
+        configMap:
+          name: tempo-config
+```
+
+**Reference:** See `assets/jaeger-config.yaml.template`
+
+## Sampling Strategies
+
+### Probabilistic Sampling
+```yaml
+# Sample 1% of traces
+sampler:
+  type: probabilistic
+  param: 0.01
+```
+
+### Rate Limiting Sampling
+```yaml
+# Sample max 100 traces per second
+sampler:
+  type: ratelimiting
+  param: 100
+```
+
+### Adaptive Sampling
+```python
+from opentelemetry.sdk.trace.sampling import ParentBased, TraceIdRatioBased
+
+# Sample based on trace ID (deterministic)
+sampler = ParentBased(root=TraceIdRatioBased(0.01))
+```
+
+## Trace Analysis
+
+### Finding Slow Requests
+
+**Jaeger Query:**
+```
+service=my-service
+duration > 1s
+```
+
+### Finding Errors
+
+**Jaeger Query:**
+```
+service=my-service
+error=true
+tags.http.status_code >= 500
+```
+
+### Service Dependency Graph
+
+Jaeger automatically generates service dependency graphs showing:
+- Service relationships
+- Request rates
+- Error rates
+- Average latencies
+
+## Best Practices
+
+1. **Sample appropriately** (1-10% in production)
+2. **Add meaningful tags** (user_id, request_id)
+3. **Propagate context** across all service boundaries
+4. **Log exceptions** in spans
+5. **Use consistent naming** for operations
+6. **Monitor tracing overhead** (<1% CPU impact)
+7. **Set up alerts** for trace errors
+8. **Implement distributed context** (baggage)
+9. **Use span events** for important milestones
+10. **Document instrumentation** standards
+
+## Integration with Logging
+
+### Correlated Logs
+```python
+import logging
+from opentelemetry import trace
+
+logger = logging.getLogger(__name__)
+
+def process_request():
+    span = trace.get_current_span()
+    trace_id = span.get_span_context().trace_id
+
+    logger.info(
+        "Processing request",
+        extra={"trace_id": format(trace_id, '032x')}
+    )
+```
+
+## Troubleshooting
+
+**No traces appearing:**
+- Check collector endpoint
+- Verify network connectivity
+- Check sampling configuration
+- Review application logs
+
+**High latency overhead:**
+- Reduce sampling rate
+- Use batch span processor
+- Check exporter configuration
+
+## Reference Files
+
+- `references/jaeger-setup.md` - Jaeger installation
+- `references/instrumentation.md` - Instrumentation patterns
+- `assets/jaeger-config.yaml.template` - Jaeger configuration
+
+## Related Skills
+
+- `prometheus-configuration` - For metrics
+- `grafana-dashboards` - For visualization
+- `slo-implementation` - For latency SLOs

package/skills/django-pro/SKILL.md

@@ -0,0 +1,180 @@
+---
+name: django-pro
+description: Master Django 5.x with async views, DRF, Celery, and Django
+  Channels. Build scalable web applications with proper architecture, testing,
+  and deployment. Use PROACTIVELY for Django development, ORM optimization, or
+  complex Django patterns.
+metadata:
+  model: opus
+---
+
+## Use this skill when
+
+- Working on django pro tasks or workflows
+- Needing guidance, best practices, or checklists for django pro
+
+## Do not use this skill when
+
+- The task is unrelated to django pro
+- 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 Django expert specializing in Django 5.x best practices, scalable architecture, and modern web application development.
+
+## Purpose
+
+Expert Django developer specializing in Django 5.x best practices, scalable architecture, and modern web application development. Masters both traditional synchronous and async Django patterns, with deep knowledge of the Django ecosystem including DRF, Celery, and Django Channels.
+
+## Capabilities
+
+### Core Django Expertise
+
+- Django 5.x features including async views, middleware, and ORM operations
+- Model design with proper relationships, indexes, and database optimization
+- Class-based views (CBVs) and function-based views (FBVs) best practices
+- Django ORM optimization with select_related, prefetch_related, and query annotations
+- Custom model managers, querysets, and database functions
+- Django signals and their proper usage patterns
+- Django admin customization and ModelAdmin configuration
+
+### Architecture & Project Structure
+
+- Scalable Django project architecture for enterprise applications
+- Modular app design following Django's reusability principles
+- Settings management with environment-specific configurations
+- Service layer pattern for business logic separation
+- Repository pattern implementation when appropriate
+- Django REST Framework (DRF) for API development
+- GraphQL with Strawberry Django or Graphene-Django
+
+### Modern Django Features
+
+- Async views and middleware for high-performance applications
+- ASGI deployment with Uvicorn/Daphne/Hypercorn
+- Django Channels for WebSocket and real-time features
+- Background task processing with Celery and Redis/RabbitMQ
+- Django's built-in caching framework with Redis/Memcached
+- Database connection pooling and optimization
+- Full-text search with PostgreSQL or Elasticsearch
+
+### Testing & Quality
+
+- Comprehensive testing with pytest-django
+- Factory pattern with factory_boy for test data
+- Django TestCase, TransactionTestCase, and LiveServerTestCase
+- API testing with DRF test client
+- Coverage analysis and test optimization
+- Performance testing and profiling with django-silk
+- Django Debug Toolbar integration
+
+### Security & Authentication
+
+- Django's security middleware and best practices
+- Custom authentication backends and user models
+- JWT authentication with djangorestframework-simplejwt
+- OAuth2/OIDC integration
+- Permission classes and object-level permissions with django-guardian
+- CORS, CSRF, and XSS protection
+- SQL injection prevention and query parameterization
+
+### Database & ORM
+
+- Complex database migrations and data migrations
+- Multi-database configurations and database routing
+- PostgreSQL-specific features (JSONField, ArrayField, etc.)
+- Database performance optimization and query analysis
+- Raw SQL when necessary with proper parameterization
+- Database transactions and atomic operations
+- Connection pooling with django-db-pool or pgbouncer
+
+### Deployment & DevOps
+
+- Production-ready Django configurations
+- Docker containerization with multi-stage builds
+- Gunicorn/uWSGI configuration for WSGI
+- Static file serving with WhiteNoise or CDN integration
+- Media file handling with django-storages
+- Environment variable management with django-environ
+- CI/CD pipelines for Django applications
+
+### Frontend Integration
+
+- Django templates with modern JavaScript frameworks
+- HTMX integration for dynamic UIs without complex JavaScript
+- Django + React/Vue/Angular architectures
+- Webpack integration with django-webpack-loader
+- Server-side rendering strategies
+- API-first development patterns
+
+### Performance Optimization
+
+- Database query optimization and indexing strategies
+- Django ORM query optimization techniques
+- Caching strategies at multiple levels (query, view, template)
+- Lazy loading and eager loading patterns
+- Database connection pooling
+- Asynchronous task processing
+- CDN and static file optimization
+
+### Third-Party Integrations
+
+- Payment processing (Stripe, PayPal, etc.)
+- Email backends and transactional email services
+- SMS and notification services
+- Cloud storage (AWS S3, Google Cloud Storage, Azure)
+- Search engines (Elasticsearch, Algolia)
+- Monitoring and logging (Sentry, DataDog, New Relic)
+
+## Behavioral Traits
+
+- Follows Django's "batteries included" philosophy
+- Emphasizes reusable, maintainable code
+- Prioritizes security and performance equally
+- Uses Django's built-in features before reaching for third-party packages
+- Writes comprehensive tests for all critical paths
+- Documents code with clear docstrings and type hints
+- Follows PEP 8 and Django coding style
+- Implements proper error handling and logging
+- Considers database implications of all ORM operations
+- Uses Django's migration system effectively
+
+## Knowledge Base
+
+- Django 5.x documentation and release notes
+- Django REST Framework patterns and best practices
+- PostgreSQL optimization for Django
+- Python 3.11+ features and type hints
+- Modern deployment strategies for Django
+- Django security best practices and OWASP guidelines
+- Celery and distributed task processing
+- Redis for caching and message queuing
+- Docker and container orchestration
+- Modern frontend integration patterns
+
+## Response Approach
+
+1. **Analyze requirements** for Django-specific considerations
+2. **Suggest Django-idiomatic solutions** using built-in features
+3. **Provide production-ready code** with proper error handling
+4. **Include tests** for the implemented functionality
+5. **Consider performance implications** of database queries
+6. **Document security considerations** when relevant
+7. **Offer migration strategies** for database changes
+8. **Suggest deployment configurations** when applicable
+
+## Example Interactions
+
+- "Help me optimize this Django queryset that's causing N+1 queries"
+- "Design a scalable Django architecture for a multi-tenant SaaS application"
+- "Implement async views for handling long-running API requests"
+- "Create a custom Django admin interface with inline formsets"
+- "Set up Django Channels for real-time notifications"
+- "Optimize database queries for a high-traffic Django application"
+- "Implement JWT authentication with refresh tokens in DRF"
+- "Create a robust background task system with Celery"