@neyugn/agent-kits 0.1.0

package/kits/coder/skills/kubernetes-patterns/SKILL.md

@@ -0,0 +1,357 @@
+---
+name: kubernetes-patterns
+description: Kubernetes orchestration principles and decision-making. Use when deploying to K8s, designing cluster architecture, implementing GitOps, or configuring workloads. Covers manifests, Helm, deployments, services, and production patterns.
+allowed-tools: Read, Write, Edit, Bash
+version: 1.0
+priority: HIGH
+---
+
+# Kubernetes Patterns - Cloud-Native Orchestration
+
+> **Philosophy:** Kubernetes is infrastructure as code. Declare what you want, let the system reconcile. **GitOps everything.**
+
+---
+
+## Core Principles
+
+| Principle           | Rule                                                 |
+| ------------------- | ---------------------------------------------------- |
+| **Declarative**     | Define desired state, not imperative steps           |
+| **Immutable**       | Never modify running resources - redeploy instead    |
+| **GitOps**          | Git is the source of truth for all manifests         |
+| **Least Privilege** | RBAC with minimal permissions, pod security policies |
+| **Observable**      | Probes, metrics, logs for every workload             |
+
+---
+
+## Workload Types
+
+| Type            | Use Case                         | Example                    |
+| --------------- | -------------------------------- | -------------------------- |
+| **Deployment**  | Stateless apps, web servers      | API servers, frontend      |
+| **StatefulSet** | Stateful apps needing stable IDs | Databases, message queues  |
+| **DaemonSet**   | One pod per node                 | Log collectors, monitoring |
+| **Job**         | Run-to-completion tasks          | DB migrations, batch jobs  |
+| **CronJob**     | Scheduled tasks                  | Backups, reports           |
+
+---
+
+## Essential Manifest Patterns
+
+### Production Deployment
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: api
+  labels:
+    app: api
+    version: v1.0.0
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app: api
+  strategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxUnavailable: 1
+      maxSurge: 1
+  template:
+    metadata:
+      labels:
+        app: api
+    spec:
+      securityContext:
+        runAsNonRoot: true
+        runAsUser: 1000
+      containers:
+        - name: api
+          image: myapp/api:v1.0.0
+          ports:
+            - containerPort: 3000
+          resources:
+            requests:
+              cpu: "100m"
+              memory: "128Mi"
+            limits:
+              cpu: "500m"
+              memory: "512Mi"
+          livenessProbe:
+            httpGet:
+              path: /health
+              port: 3000
+            initialDelaySeconds: 10
+            periodSeconds: 10
+          readinessProbe:
+            httpGet:
+              path: /ready
+              port: 3000
+            initialDelaySeconds: 5
+            periodSeconds: 5
+          env:
+            - name: DATABASE_URL
+              valueFrom:
+                secretKeyRef:
+                  name: db-credentials
+                  key: url
+```
+
+### Service + Ingress
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: api
+spec:
+  selector:
+    app: api
+  ports:
+    - port: 80
+      targetPort: 3000
+---
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: api
+  annotations:
+    cert-manager.io/cluster-issuer: letsencrypt-prod
+spec:
+  tls:
+    - hosts:
+        - api.example.com
+      secretName: api-tls
+  rules:
+    - host: api.example.com
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: api
+                port:
+                  number: 80
+```
+
+---
+
+## Resource Management
+
+| Resource Type | Requests (min)      | Limits (max)              |
+| ------------- | ------------------- | ------------------------- |
+| **CPU**       | Guaranteed CPU time | CPU throttled if exceeded |
+| **Memory**    | Reserved memory     | OOMKilled if exceeded     |
+
+### Sizing Guidelines
+
+| App Type       | CPU Request | Memory Request | CPU Limit   | Memory Limit |
+| -------------- | ----------- | -------------- | ----------- | ------------ |
+| **API Server** | 100m-200m   | 128Mi-256Mi    | 500m-1000m  | 512Mi-1Gi    |
+| **Worker**     | 200m-500m   | 256Mi-512Mi    | 1000m-2000m | 1Gi-2Gi      |
+| **Database**   | 500m-1000m  | 1Gi-2Gi        | 2000m-4000m | 4Gi-8Gi      |
+
+> 🔴 **Always set requests!** Without requests, K8s can't schedule efficiently.
+
+---
+
+## Health Probes
+
+| Probe Type         | Purpose             | On Failure                     |
+| ------------------ | ------------------- | ------------------------------ |
+| **livenessProbe**  | Is container alive? | Container restarted            |
+| **readinessProbe** | Ready for traffic?  | Removed from Service endpoints |
+| **startupProbe**   | Still starting up?  | Liveness/readiness disabled    |
+
+### Probe Configuration
+
+```yaml
+livenessProbe:
+  httpGet:
+    path: /health
+    port: 3000
+  initialDelaySeconds: 10 # Wait before first check
+  periodSeconds: 10 # Check every 10s
+  timeoutSeconds: 5 # Timeout for check
+  failureThreshold: 3 # Restart after 3 failures
+
+readinessProbe:
+  httpGet:
+    path: /ready
+    port: 3000
+  initialDelaySeconds: 5
+  periodSeconds: 5
+  failureThreshold: 3
+```
+
+---
+
+## Configuration Management
+
+| Method               | Use Case                    | When to Use                 |
+| -------------------- | --------------------------- | --------------------------- |
+| **ConfigMap**        | Non-sensitive config        | App settings, feature flags |
+| **Secret**           | Sensitive data              | API keys, passwords         |
+| **External Secrets** | Production secrets          | Sync from Vault/AWS/GCP     |
+| **Helm Values**      | Environment-specific config | Per-env deployments         |
+
+### Secret Best Practices
+
+```yaml
+# Don't store secrets in manifests!
+# Use External Secrets Operator:
+apiVersion: external-secrets.io/v1beta1
+kind: ExternalSecret
+metadata:
+  name: db-credentials
+spec:
+  refreshInterval: 1h
+  secretStoreRef:
+    name: aws-secrets-manager
+    kind: ClusterSecretStore
+  target:
+    name: db-credentials
+  data:
+    - secretKey: url
+      remoteRef:
+        key: prod/database
+```
+
+---
+
+## Helm Patterns
+
+### Chart Structure
+
+```
+mychart/
+├── Chart.yaml           # Chart metadata
+├── values.yaml          # Default values
+├── values-prod.yaml     # Production overrides
+├── templates/
+│   ├── deployment.yaml
+│   ├── service.yaml
+│   ├── ingress.yaml
+│   └── _helpers.tpl     # Template helpers
+```
+
+### Values Pattern
+
+```yaml
+# values.yaml (base)
+replicaCount: 1
+image:
+  repository: myapp/api
+  tag: latest
+resources:
+  requests:
+    cpu: 100m
+    memory: 128Mi
+
+# values-prod.yaml (override)
+replicaCount: 3
+image:
+  tag: v1.0.0
+resources:
+  requests:
+    cpu: 500m
+    memory: 512Mi
+```
+
+---
+
+## Decision Trees
+
+### Which Workload Type?
+
+```
+Need stable network identity/storage?
+├── Yes → StatefulSet
+└── No → Run on every node?
+    ├── Yes → DaemonSet
+    └── No → One-time task?
+        ├── Yes → Job or CronJob
+        └── No → Deployment
+```
+
+### Ingress vs LoadBalancer?
+
+```
+Multiple services behind one IP?
+├── Yes → Ingress with Ingress Controller
+└── No → Just one service exposed?
+    ├── Yes → LoadBalancer Service
+    └── No → Internal only?
+        └── Yes → ClusterIP Service
+```
+
+---
+
+## GitOps with ArgoCD
+
+```yaml
+apiVersion: argoproj.io/v1alpha1
+kind: Application
+metadata:
+  name: myapp
+  namespace: argocd
+spec:
+  project: default
+  source:
+    repoURL: https://github.com/org/manifests
+    targetRevision: main
+    path: apps/myapp
+  destination:
+    server: https://kubernetes.default.svc
+    namespace: production
+  syncPolicy:
+    automated:
+      prune: true
+      selfHeal: true
+```
+
+---
+
+## Anti-Patterns (DON'T)
+
+| ❌ Anti-Pattern              | ✅ Correct Approach                     |
+| ---------------------------- | --------------------------------------- |
+| `kubectl apply` from laptop  | GitOps - apply from Git repo            |
+| `latest` image tag           | Specific versioned tags                 |
+| No resource requests/limits  | Always set requests, usually set limits |
+| Running as root              | `runAsNonRoot: true`                    |
+| Secrets in ConfigMap         | Use Secrets or External Secrets         |
+| No health probes             | livenessProbe + readinessProbe          |
+| Single replica in prod       | Minimum 2-3 replicas with PDB           |
+| `kubectl edit` in production | Edit in Git, apply via GitOps           |
+
+---
+
+## 🔴 Self-Check Before Deploying
+
+| Check                     | Question                              |
+| ------------------------- | ------------------------------------- |
+| ✅ **Resources set?**     | requests and limits configured?       |
+| ✅ **Probes configured?** | liveness + readiness probes?          |
+| ✅ **Non-root?**          | Pod runs as non-root user?            |
+| ✅ **Image pinned?**      | Specific tag, not `latest`?           |
+| ✅ **Secrets external?**  | No hardcoded secrets in manifests?    |
+| ✅ **Replicas > 1?**      | At least 2 replicas for HA?           |
+| ✅ **PDB defined?**       | PodDisruptionBudget for availability? |
+
+---
+
+## Related Skills
+
+| Need                 | Skill                     |
+| -------------------- | ------------------------- |
+| Container images     | `docker-patterns`         |
+| CI/CD pipelines      | `github-actions` (future) |
+| Server management    | `server-management`       |
+| Deployment workflows | `deployment-procedures`   |
+
+---
+
+> **Remember:** Kubernetes is not magic. It amplifies your practices - good and bad. If your deployments are messy, K8s will make them messier at scale. Start with GitOps, proper manifests, and observability.

package/kits/coder/skills/mermaid-diagrams/SKILL.md

@@ -0,0 +1,351 @@
+---
+name: mermaid-diagrams
+description: Mermaid diagram patterns for documentation. Create flowcharts, sequence diagrams, ERDs, and architecture diagrams. Use when visualizing systems, processes, or data relationships.
+allowed-tools: Read, Write, Edit
+version: 1.0
+priority: LOW
+---
+
+# Mermaid Diagrams - Visual Documentation
+
+> **Philosophy:** A good diagram is worth a thousand words. Keep it simple, readable, and purposeful.
+
+---
+
+## 🎯 Core Principles
+
+| Principle       | Rule                                         |
+| --------------- | -------------------------------------------- |
+| **Clarity**     | One diagram, one concept                     |
+| **Simplicity**  | Avoid overcrowding - less is more            |
+| **Consistency** | Same styling and conventions across diagrams |
+| **Purpose**     | Every element should serve understanding     |
+| **Maintenance** | Easy to update as system evolves             |
+
+---
+
+## 📊 Diagram Types
+
+| Type              | Best For                                |
+| ----------------- | --------------------------------------- |
+| `flowchart`       | Processes, decision trees, workflows    |
+| `sequenceDiagram` | API calls, interactions, timing         |
+| `classDiagram`    | Object relationships, inheritance       |
+| `erDiagram`       | Database schemas, entity relationships  |
+| `stateDiagram-v2` | State machines, lifecycle               |
+| `gantt`           | Project timelines, milestones           |
+| `pie`             | Proportions, distributions              |
+| `gitGraph`        | Branch strategies, merges               |
+| `journey`         | User experience flows                   |
+| `C4Context`       | System architecture (with C4 extension) |
+
+---
+
+## 📈 Flowchart Patterns
+
+### Basic Flowchart
+
+```mermaid
+flowchart TD
+    A[Start] --> B{Is valid?}
+    B -->|Yes| C[Process]
+    B -->|No| D[Error]
+    C --> E[End]
+    D --> E
+```
+
+### Node Shapes
+
+| Shape         | Syntax     | Use For             |
+| ------------- | ---------- | ------------------- |
+| Rectangle     | `[text]`   | Process, action     |
+| Rounded       | `(text)`   | Start/end, terminal |
+| Stadium       | `([text])` | Start/end (alt)     |
+| Diamond       | `{text}`   | Decision            |
+| Hexagon       | `{{text}}` | Preparation         |
+| Parallelogram | `[/text/]` | Input/output        |
+| Circle        | `((text))` | Connector           |
+| Database      | `[(text)]` | Database            |
+
+### Subgraphs for Organization
+
+```mermaid
+flowchart TB
+    subgraph Frontend
+        A[React App] --> B[API Client]
+    end
+
+    subgraph Backend
+        C[API Server] --> D[(Database)]
+    end
+
+    B --> C
+```
+
+---
+
+## 🔄 Sequence Diagram Patterns
+
+### Basic API Flow
+
+```mermaid
+sequenceDiagram
+    participant C as Client
+    participant A as API
+    participant D as Database
+
+    C->>+A: POST /users
+    A->>+D: INSERT user
+    D-->>-A: user record
+    A-->>-C: 201 Created
+```
+
+### Arrow Types
+
+| Arrow   | Meaning                |
+| ------- | ---------------------- |
+| `->>`   | Solid with arrowhead   |
+| `-->`   | Dotted with arrowhead  |
+| `->>+`  | Activate lifeline      |
+| `-->>-` | Deactivate lifeline    |
+| `-x`    | Solid with X (failure) |
+| `--x`   | Dotted with X          |
+
+### Notes and Loops
+
+```mermaid
+sequenceDiagram
+    participant U as User
+    participant S as Server
+
+    Note over U,S: Authentication Flow
+
+    U->>S: Login request
+    activate S
+
+    loop Validate
+        S->>S: Check credentials
+    end
+
+    alt Success
+        S-->>U: JWT Token
+    else Failure
+        S-->>U: 401 Error
+    end
+
+    deactivate S
+```
+
+---
+
+## 🗃️ ER Diagram Patterns
+
+### Database Schema
+
+```mermaid
+erDiagram
+    USER ||--o{ ORDER : places
+    USER {
+        uuid id PK
+        string email UK
+        string name
+        timestamp created_at
+    }
+
+    ORDER ||--|{ ORDER_ITEM : contains
+    ORDER {
+        uuid id PK
+        uuid user_id FK
+        decimal total
+        string status
+    }
+
+    ORDER_ITEM }o--|| PRODUCT : references
+    ORDER_ITEM {
+        uuid id PK
+        uuid order_id FK
+        uuid product_id FK
+        int quantity
+    }
+
+    PRODUCT {
+        uuid id PK
+        string name
+        decimal price
+    }
+```
+
+### Relationship Symbols
+
+| Symbol | Meaning      |
+| ------ | ------------ | ----------- | ----------- |
+| `      |              | `           | Exactly one |
+| `o{`   | Zero or more |
+| `      | {`           | One or more |
+| `o     | `            | Zero or one |
+
+---
+
+## 🔀 State Diagram Patterns
+
+### Lifecycle States
+
+```mermaid
+stateDiagram-v2
+    [*] --> Draft
+
+    Draft --> Pending: Submit
+    Pending --> Approved: Approve
+    Pending --> Rejected: Reject
+
+    Approved --> Published: Publish
+    Published --> Archived: Archive
+
+    Rejected --> Draft: Revise
+    Archived --> [*]
+
+    note right of Pending
+        Awaiting review
+    end note
+```
+
+---
+
+## 🎨 Styling
+
+### Theme Options
+
+```mermaid
+%%{init: {'theme': 'dark'}}%%
+flowchart LR
+    A --> B
+```
+
+| Theme     | Best For                |
+| --------- | ----------------------- |
+| `default` | Light backgrounds       |
+| `dark`    | Dark mode documentation |
+| `forest`  | Calm, professional      |
+| `neutral` | Minimal, clean          |
+
+### Custom Styling
+
+```mermaid
+flowchart TD
+    A[Critical]:::critical --> B[Normal]
+    B --> C[Success]:::success
+
+    classDef critical fill:#ff6b6b,stroke:#c92a2a,color:#fff
+    classDef success fill:#51cf66,stroke:#2b8a3e,color:#fff
+```
+
+---
+
+## 📋 Best Practices
+
+### Do's
+
+| Practice                | Why                              |
+| ----------------------- | -------------------------------- |
+| One concept per diagram | Clarity and focus                |
+| Use descriptive labels  | Self-documenting                 |
+| Consistent direction    | TD/LR - pick one and stick to it |
+| Group with subgraphs    | Visual organization              |
+| Use proper shapes       | Semantic meaning                 |
+
+### Don'ts
+
+| Anti-Pattern          | Problem                          |
+| --------------------- | -------------------------------- |
+| Too many nodes        | Overwhelming, hard to read       |
+| Long text in nodes    | Cluttered diagram                |
+| Crossing lines        | Confusing flow                   |
+| Inconsistent styling  | Unprofessional look              |
+| No legend when needed | Readers can't understand symbols |
+
+---
+
+## 🔧 Common Use Cases
+
+### Architecture Decision
+
+```mermaid
+flowchart TD
+    subgraph Options
+        A[REST API] --> X{Choose}
+        B[GraphQL] --> X
+        C[gRPC] --> X
+    end
+
+    X -->|Web/Mobile| B
+    X -->|Microservices| C
+    X -->|Simple CRUD| A
+```
+
+### Deployment Flow
+
+```mermaid
+flowchart LR
+    subgraph Development
+        A[Code] --> B[PR]
+    end
+
+    subgraph CI/CD
+        B --> C[Build]
+        C --> D[Test]
+        D --> E{Pass?}
+    end
+
+    subgraph Deploy
+        E -->|Yes| F[Staging]
+        F --> G[Production]
+    end
+
+    E -->|No| A
+```
+
+### User Journey
+
+```mermaid
+journey
+    title User Signup Flow
+    section Discovery
+      Visit landing page: 5: User
+      Read features: 4: User
+    section Signup
+      Click signup: 5: User
+      Fill form: 3: User
+      Verify email: 2: User
+    section Onboarding
+      Complete profile: 4: User
+      Start using: 5: User
+```
+
+---
+
+## ✅ Diagram Checklist
+
+Before sharing a diagram:
+
+- [ ] Single clear purpose
+- [ ] All nodes have meaningful labels
+- [ ] No unnecessary complexity
+- [ ] Consistent styling
+- [ ] Renders correctly in target platform
+- [ ] Accessible (add description if needed)
+- [ ] Source stored in version control
+
+---
+
+## 🔗 Related Skills
+
+| Need                   | Skill                     |
+| ---------------------- | ------------------------- |
+| Architecture decisions | `architecture`            |
+| Database design        | `database-design`         |
+| API documentation      | `documentation-templates` |
+| Project planning       | `plan-writing`            |
+
+---
+
+> **Remember:** The purpose of a diagram is to communicate. If it takes longer to understand the diagram than the concept it represents, simplify it.