devstack 0.1.0

package/vendor/skills/skills/kubernetes-specialist/references/workloads.md

@@ -0,0 +1,377 @@
+# Kubernetes Workloads
+
+## Deployment Pattern
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: web-app
+  namespace: production
+  labels:
+    app: web-app
+    tier: frontend
+spec:
+  replicas: 3
+  revisionHistoryLimit: 10
+  strategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxSurge: 1
+      maxUnavailable: 0
+  selector:
+    matchLabels:
+      app: web-app
+  template:
+    metadata:
+      labels:
+        app: web-app
+        tier: frontend
+        version: v1.2.0
+      annotations:
+        prometheus.io/scrape: "true"
+        prometheus.io/port: "8080"
+    spec:
+      serviceAccountName: web-app-sa
+      securityContext:
+        runAsNonRoot: true
+        runAsUser: 1000
+        fsGroup: 2000
+      containers:
+        - name: app
+          image: myregistry.io/web-app:v1.2.0
+          imagePullPolicy: IfNotPresent
+          ports:
+            - name: http
+              containerPort: 8080
+              protocol: TCP
+          env:
+            - name: ENVIRONMENT
+              value: production
+            - name: DB_HOST
+              valueFrom:
+                configMapKeyRef:
+                  name: app-config
+                  key: database.host
+            - name: DB_PASSWORD
+              valueFrom:
+                secretKeyRef:
+                  name: app-secrets
+                  key: db-password
+          resources:
+            requests:
+              cpu: 100m
+              memory: 128Mi
+            limits:
+              cpu: 500m
+              memory: 512Mi
+          livenessProbe:
+            httpGet:
+              path: /health
+              port: http
+            initialDelaySeconds: 30
+            periodSeconds: 10
+            timeoutSeconds: 5
+            failureThreshold: 3
+          readinessProbe:
+            httpGet:
+              path: /ready
+              port: http
+            initialDelaySeconds: 10
+            periodSeconds: 5
+            timeoutSeconds: 3
+            failureThreshold: 2
+          volumeMounts:
+            - name: config
+              mountPath: /etc/config
+              readOnly: true
+            - name: cache
+              mountPath: /var/cache
+      volumes:
+        - name: config
+          configMap:
+            name: app-config
+        - name: cache
+          emptyDir: {}
+```
+
+## StatefulSet Pattern
+
+```yaml
+apiVersion: apps/v1
+kind: StatefulSet
+metadata:
+  name: postgres
+  namespace: database
+spec:
+  serviceName: postgres-headless
+  replicas: 3
+  podManagementPolicy: OrderedReady
+  updateStrategy:
+    type: RollingUpdate
+  selector:
+    matchLabels:
+      app: postgres
+  template:
+    metadata:
+      labels:
+        app: postgres
+    spec:
+      serviceAccountName: postgres-sa
+      securityContext:
+        runAsUser: 999
+        fsGroup: 999
+      containers:
+        - name: postgres
+          image: postgres:15-alpine
+          ports:
+            - name: postgres
+              containerPort: 5432
+          env:
+            - name: POSTGRES_PASSWORD
+              valueFrom:
+                secretKeyRef:
+                  name: postgres-secrets
+                  key: password
+            - name: PGDATA
+              value: /var/lib/postgresql/data/pgdata
+          resources:
+            requests:
+              cpu: 500m
+              memory: 1Gi
+            limits:
+              cpu: 2000m
+              memory: 4Gi
+          volumeMounts:
+            - name: data
+              mountPath: /var/lib/postgresql/data
+          livenessProbe:
+            exec:
+              command:
+                - pg_isready
+                - -U
+                - postgres
+            initialDelaySeconds: 30
+            periodSeconds: 10
+          readinessProbe:
+            exec:
+              command:
+                - pg_isready
+                - -U
+                - postgres
+            initialDelaySeconds: 10
+            periodSeconds: 5
+  volumeClaimTemplates:
+    - metadata:
+        name: data
+      spec:
+        accessModes: ["ReadWriteOnce"]
+        storageClassName: fast-ssd
+        resources:
+          requests:
+            storage: 50Gi
+```
+
+## DaemonSet Pattern
+
+```yaml
+apiVersion: apps/v1
+kind: DaemonSet
+metadata:
+  name: node-exporter
+  namespace: monitoring
+spec:
+  selector:
+    matchLabels:
+      app: node-exporter
+  updateStrategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxUnavailable: 1
+  template:
+    metadata:
+      labels:
+        app: node-exporter
+    spec:
+      hostNetwork: true
+      hostPID: true
+      serviceAccountName: node-exporter-sa
+      tolerations:
+        - effect: NoSchedule
+          operator: Exists
+      containers:
+        - name: node-exporter
+          image: prom/node-exporter:latest
+          args:
+            - --path.procfs=/host/proc
+            - --path.sysfs=/host/sys
+            - --collector.filesystem.mount-points-exclude=^/(sys|proc|dev|host|etc)($$|/)
+          ports:
+            - name: metrics
+              containerPort: 9100
+              protocol: TCP
+          resources:
+            requests:
+              cpu: 50m
+              memory: 64Mi
+            limits:
+              cpu: 200m
+              memory: 128Mi
+          volumeMounts:
+            - name: proc
+              mountPath: /host/proc
+              readOnly: true
+            - name: sys
+              mountPath: /host/sys
+              readOnly: true
+      volumes:
+        - name: proc
+          hostPath:
+            path: /proc
+        - name: sys
+          hostPath:
+            path: /sys
+```
+
+## Job Pattern
+
+```yaml
+apiVersion: batch/v1
+kind: Job
+metadata:
+  name: db-migration-20231214
+  namespace: production
+spec:
+  backoffLimit: 3
+  ttlSecondsAfterFinished: 3600
+  template:
+    metadata:
+      labels:
+        app: db-migration
+    spec:
+      restartPolicy: OnFailure
+      serviceAccountName: migration-sa
+      containers:
+        - name: migrate
+          image: myregistry.io/migrations:v1.2.0
+          command: ["/bin/sh", "-c"]
+          args:
+            - |
+              echo "Starting migration..."
+              /app/migrate up
+              echo "Migration complete"
+          env:
+            - name: DATABASE_URL
+              valueFrom:
+                secretKeyRef:
+                  name: db-secrets
+                  key: connection-string
+          resources:
+            requests:
+              cpu: 100m
+              memory: 128Mi
+            limits:
+              cpu: 500m
+              memory: 512Mi
+```
+
+## CronJob Pattern
+
+```yaml
+apiVersion: batch/v1
+kind: CronJob
+metadata:
+  name: backup-database
+  namespace: production
+spec:
+  schedule: "0 2 * * *" # Daily at 2 AM
+  timeZone: "America/New_York"
+  successfulJobsHistoryLimit: 3
+  failedJobsHistoryLimit: 1
+  concurrencyPolicy: Forbid
+  jobTemplate:
+    spec:
+      backoffLimit: 2
+      ttlSecondsAfterFinished: 86400
+      template:
+        metadata:
+          labels:
+            app: backup
+        spec:
+          restartPolicy: OnFailure
+          serviceAccountName: backup-sa
+          containers:
+            - name: backup
+              image: myregistry.io/backup-tool:latest
+              command: ["/usr/local/bin/backup.sh"]
+              env:
+                - name: S3_BUCKET
+                  valueFrom:
+                    configMapKeyRef:
+                      name: backup-config
+                      key: s3-bucket
+                - name: AWS_ACCESS_KEY_ID
+                  valueFrom:
+                    secretKeyRef:
+                      name: backup-secrets
+                      key: aws-access-key
+                - name: AWS_SECRET_ACCESS_KEY
+                  valueFrom:
+                    secretKeyRef:
+                      name: backup-secrets
+                      key: aws-secret-key
+              resources:
+                requests:
+                  cpu: 200m
+                  memory: 256Mi
+                limits:
+                  cpu: 1000m
+                  memory: 1Gi
+              volumeMounts:
+                - name: backup-volume
+                  mountPath: /backup
+          volumes:
+            - name: backup-volume
+              emptyDir:
+                sizeLimit: 10Gi
+```
+
+## Init Containers
+
+```yaml
+spec:
+  initContainers:
+    - name: wait-for-db
+      image: busybox:latest
+      command: ["sh", "-c"]
+      args:
+        - |
+          until nc -z postgres-service 5432; do
+            echo "Waiting for database..."
+            sleep 2
+          done
+          echo "Database is ready"
+    - name: migrate-schema
+      image: myregistry.io/migrations:latest
+      command: ["/app/migrate", "up"]
+      env:
+        - name: DATABASE_URL
+          valueFrom:
+            secretKeyRef:
+              name: db-secrets
+              key: url
+  containers:
+    - name: app
+      image: myregistry.io/app:latest
+```
+
+## Best Practices
+
+1. **Resource Management**: Always set requests and limits
+2. **Health Checks**: Include both liveness and readiness probes
+3. **Security**: Use non-root users, read-only filesystems when possible
+4. **Labels**: Consistent labeling for organization and selection
+5. **Update Strategy**: Choose appropriate strategy (RollingUpdate, Recreate)
+6. **Service Accounts**: Never use default, create specific SAs
+7. **Image Tags**: Use specific versions, not `latest` in production
+8. **Cleanup**: Set TTL for Jobs to auto-cleanup completed pods

package/vendor/skills/skills/landing-page-design/SKILL.md

@@ -0,0 +1,243 @@
+---
+name: landing-page-design
+description: "Landing page conversion optimization with layout rules, hero section design, and CTA psychology. Covers above-the-fold formula, social proof placement, mobile design, and F-pattern reading. Use for: startup landing pages, product pages, SaaS marketing, conversion optimization. Triggers: landing page, hero section, above the fold, conversion optimization, landing page design, cta button, hero image, landing page layout, saas landing page, product page design, conversion rate, landing page best practices"
+allowed-tools: Bash(infsh *)
+---
+
+# Landing Page Design
+
+Design high-converting landing pages with AI-generated visuals via [inference.sh](https://inference.sh) CLI.
+
+## Quick Start
+
+```bash
+curl -fsSL https://cli.inference.sh | sh && infsh login
+
+# Generate a hero image
+infsh app run falai/flux-dev-lora --input '{
+  "prompt": "professional person smiling while using a laptop showing a clean dashboard interface, bright modern office, natural lighting, warm and productive atmosphere, lifestyle marketing photography",
+  "width": 1248,
+  "height": 832
+}'
+
+# Research competitor landing pages
+infsh app run tavily/search-assistant --input '{
+  "query": "best SaaS landing page examples 2024 conversion rate"
+}'
+```
+
+> **Install note:** The [install script](https://cli.inference.sh) only detects your OS/architecture, downloads the matching binary from `dist.inference.sh`, and verifies its SHA-256 checksum. No elevated permissions or background processes. [Manual install & verification](https://dist.inference.sh/cli/checksums.txt) available.
+
+## Above-the-Fold Formula
+
+Everything visible before scrolling must communicate value in 5 seconds.
+
+```
+┌─────────────────────────────────────────────────┐
+│  [Logo]              [Nav]        [CTA Button]  │
+│                                                 │
+│   Headline (6-12 words)                         │
+│   ─────────────────────────                     │
+│   Subheadline (15-25 words)        [Hero Image] │
+│                                    showing the  │
+│   [Primary CTA Button]            OUTCOME, not  │
+│   "Start Free Trial"              the product   │
+│                                                 │
+│   Social proof: "Trusted by 10,000+ teams"      │
+│   [logo] [logo] [logo] [logo] [logo]            │
+└─────────────────────────────────────────────────┘
+```
+
+### The 5 Elements
+
+| Element          | Rule                               | Example                                                                                |
+| ---------------- | ---------------------------------- | -------------------------------------------------------------------------------------- |
+| **Headline**     | 6-12 words, states the outcome     | "Ship docs in minutes, not days"                                                       |
+| **Subheadline**  | 15-25 words, expands on how        | "AI-powered documentation that writes itself from your codebase. No templates needed." |
+| **Hero image**   | Shows the OUTCOME, not the product | Person looking satisfied at results, not a screenshot of your UI                       |
+| **Primary CTA**  | Action verb + value                | "Start Free Trial" not "Submit" or "Learn More"                                        |
+| **Social proof** | Logos, count, or micro-testimonial | "Trusted by 10,000+ teams at [logos]"                                                  |
+
+## Headlines
+
+### Formulas That Convert
+
+| Formula                           | Example                                    |
+| --------------------------------- | ------------------------------------------ |
+| [Outcome] without [pain]          | "Beautiful docs without the design skills" |
+| [Outcome] in [timeframe]          | "Launch your site in 5 minutes"            |
+| The [better way] to [common task] | "The faster way to build APIs"             |
+| Stop [pain]. Start [outcome].     | "Stop guessing. Start knowing."            |
+| [Number] [things] to [outcome]    | "One tool to manage all your data"         |
+
+### What Makes Headlines Fail
+
+```
+❌ "Welcome to Our Platform" (says nothing about value)
+❌ "The World's Most Advanced AI-Powered Solution" (buzzwords, no specifics)
+❌ "We Help Businesses Grow" (vague, generic)
+❌ "Next-Generation Enterprise Software" (what does it DO?)
+
+✅ "Turn customer feedback into product features, automatically"
+✅ "The spreadsheet that thinks like a database"
+✅ "Find and fix bugs before your users do"
+```
+
+## Hero Images
+
+### Show the Outcome, Not the Product
+
+```
+❌ Screenshot of your dashboard (boring, hard to parse at a glance)
+❌ Abstract geometric background (says nothing)
+❌ Stock photo of a handshake (cliché)
+
+✅ Person looking satisfied at clear results on their screen
+✅ Before/after transformation
+✅ The end result of using your product
+```
+
+```bash
+# Outcome-focused hero
+infsh app run falai/flux-dev-lora --input '{
+  "prompt": "happy professional team celebrating around a laptop showing positive growth charts, bright modern office, natural sunlight, authentic candid moment, marketing photography style, warm tones",
+  "width": 1248,
+  "height": 832
+}'
+
+# Product-in-context hero
+infsh app run bytedance/seedream-4-5 --input '{
+  "prompt": "clean modern laptop on a minimalist desk showing a beautiful analytics dashboard, floating UI elements emerging from the screen, soft gradient background, product marketing style, professional",
+  "size": "2K"
+}'
+```
+
+## CTA Buttons
+
+### Text
+
+| Good CTAs                  | Bad CTAs                      |
+| -------------------------- | ----------------------------- |
+| "Start Free Trial"         | "Submit"                      |
+| "Get Started Free"         | "Click Here"                  |
+| "See It in Action"         | "Learn More" (low commitment) |
+| "Create Your First Report" | "Sign Up" (vague)             |
+| "Try Free for 14 Days"     | "Register"                    |
+
+**Formula:** Action verb + value/outcome + (optional: reduce risk)
+
+### Design
+
+| Element       | Rule                                                             |
+| ------------- | ---------------------------------------------------------------- |
+| Color         | High contrast with background — must be the most visible element |
+| Size          | Minimum 44px height (tap target), wide enough for text + padding |
+| Position      | Above the fold, repeated after each major section                |
+| Whitespace    | Generous padding around button, don't crowd it                   |
+| Secondary CTA | If needed, use text link below ("or watch a demo")               |
+
+## Section Order
+
+The proven sequence for landing pages:
+
+| Section                  | Purpose                 | Key Element                          |
+| ------------------------ | ----------------------- | ------------------------------------ |
+| 1. **Hero**              | Core value, primary CTA | Headline + image + CTA               |
+| 2. **Social Proof**      | Build trust             | Logos, numbers, badges               |
+| 3. **Problem**           | Create empathy          | Pain point they recognize            |
+| 4. **Solution/Features** | Show how you solve it   | 3 key features with visuals          |
+| 5. **How It Works**      | Reduce complexity       | 3 steps: sign up, configure, benefit |
+| 6. **Testimonials**      | Prove it works          | 2-3 specific customer quotes         |
+| 7. **Pricing**           | Enable decision         | Clear tiers, highlight recommended   |
+| 8. **FAQ**               | Handle objections       | 5-7 common questions                 |
+| 9. **Final CTA**         | Capture remainders      | Repeat primary CTA with urgency      |
+
+## Social Proof Types
+
+| Type                 | Impact                         | Placement                   |
+| -------------------- | ------------------------------ | --------------------------- |
+| **Company logos**    | Fastest to process, high trust | Below hero                  |
+| **User count**       | Scale signal                   | Hero or social proof bar    |
+| **Star rating**      | Product quality                | Near CTA                    |
+| **Testimonials**     | Detailed credibility           | Dedicated section           |
+| **Case study stats** | Specific proof                 | Feature sections            |
+| **Trust badges**     | Security/compliance            | Near forms, pricing, footer |
+
+```bash
+# Research for social proof stats
+infsh app run exa/answer --input '{
+  "question": "What is the average conversion rate for SaaS landing pages with social proof vs without?"
+}'
+```
+
+## Form Design
+
+| Rule                                | Impact                                     |
+| ----------------------------------- | ------------------------------------------ |
+| Every field reduces conversion ~11% | Minimize fields                            |
+| Name + Email = maximum for signups  | Don't ask for phone, company, role         |
+| Single-column layout                | Don't use multi-column forms               |
+| Inline validation                   | Show errors immediately, not on submit     |
+| Clear error messages                | "Email is required" not "Error in field 3" |
+| Submit button text = action         | "Create Account" not "Submit"              |
+
+## Mobile Optimization
+
+| Rule                        | Why                         |
+| --------------------------- | --------------------------- |
+| CTA button full width       | Easy to tap with thumbs     |
+| Sticky CTA on scroll        | Always accessible           |
+| No horizontal scrolling     | Breaks mobile layout        |
+| Font minimum 16px           | iOS zooms inputs below 16px |
+| Tap targets minimum 48x48px | Apple HIG, Google Material  |
+| Images responsive           | Don't overflow viewport     |
+| Prioritize headline + CTA   | Simplify above-the-fold     |
+
+## OG Image for Sharing
+
+```bash
+# Generate an OG image for the landing page
+infsh app run falai/flux-dev-lora --input '{
+  "prompt": "clean professional social sharing card, product name and tagline on modern gradient background, minimal design, corporate tech aesthetic, 1200x630 aspect ratio equivalent",
+  "width": 1200,
+  "height": 630
+}'
+
+# Or use html-to-image for a template-based approach
+infsh app run infsh/html-to-image --input '{
+  "html": "<div style=\"width:1200px;height:630px;background:linear-gradient(135deg,#667eea,#764ba2);display:flex;align-items:center;justify-content:center;font-family:sans-serif;color:white\"><div style=\"text-align:center\"><h1 style=\"font-size:48px;margin:0\">DataFlow</h1><p style=\"font-size:24px;opacity:0.9\">Ship docs in minutes, not days</p></div></div>"
+}'
+```
+
+## Page Speed
+
+| Rule                           | Target   | Why                      |
+| ------------------------------ | -------- | ------------------------ |
+| Hero image                     | < 200 KB | First thing to load      |
+| Total page weight              | < 2 MB   | Mobile data, patience    |
+| Lazy load below-fold           | Always   | Only load what's visible |
+| Minimize JavaScript            | < 200 KB | Blocks rendering         |
+| LCP (Largest Contentful Paint) | < 2.5s   | Google Core Web Vitals   |
+
+## Common Mistakes
+
+| Mistake                      | Problem                          | Fix                                     |
+| ---------------------------- | -------------------------------- | --------------------------------------- |
+| No clear headline            | Visitor doesn't know what you do | 6-12 words, outcome-focused             |
+| CTA says "Learn More"        | Too low commitment               | Action verb + specific value            |
+| Hero is a product screenshot | Hard to parse, boring            | Show the outcome, use lifestyle imagery |
+| Multiple competing CTAs      | Decision paralysis               | One primary CTA, one secondary max      |
+| No social proof              | No trust signal                  | Add logos, counts, or testimonials      |
+| Too many form fields         | Conversion drops ~11% per field  | Name + email maximum                    |
+| Desktop-only design          | 60%+ traffic is mobile           | Design mobile-first                     |
+| No urgency in final CTA      | Visitors leave and forget        | "Start your free 14-day trial"          |
+
+## Related Skills
+
+```bash
+npx skills add inference-sh/skills@ai-image-generation
+npx skills add inference-sh/skills@web-search
+npx skills add inference-sh/skills@prompt-engineering
+```
+
+Browse all apps: `infsh app list`

package/vendor/skills/skills/lesson-learned/README.md

@@ -0,0 +1,65 @@
+# Lesson Learned
+
+Extract software engineering takeaways from your recent code changes.
+
+## Purpose
+
+Most developers ship code and move on. But the fastest way to grow is to pause and reflect: what principle did I just apply? What trade-off did I make? What would I do differently?
+
+This skill analyzes recent git history and surfaces the engineering lesson embedded in the work you just did.
+
+## When to Use
+
+- After finishing a feature or PR
+- After a debugging session
+- After a refactor
+- When you want to reflect on recent work
+- Trigger phrases: "what is the lesson here?", "what can I learn from this?", "engineering takeaway"
+
+## How It Works
+
+1. **Determine scope** -- Detects whether you're on a feature branch (analyzes branch vs main) or main (analyzes last 5 commits). You can also specify a commit range or specific SHA.
+2. **Gather changes** -- Reads git log, diffs, and commit messages. For large diffs, selectively reads the most-changed files.
+3. **Analyze patterns** -- Identifies structural decisions, trade-offs, and problems solved. Maps observations to named SE principles.
+4. **Present the lesson** -- Delivers 1-3 specific, code-grounded takeaways with the principle name, how it manifested, why it matters, and an actionable next step.
+
+## Key Features
+
+- **Git-history-driven** -- Works from actual code changes, not hypotheticals
+- **Principle-grounded** -- Maps observations to named SE principles (SOLID, DRY, KISS, YAGNI, etc.)
+- **Specific, not generic** -- Every insight references actual files and lines from your diff
+- **Balanced** -- Recognizes good patterns, not just areas for improvement
+- **Configurable scope** -- Feature branch, last N commits, specific SHA, or working changes
+
+## Output Format
+
+```markdown
+## Lesson: Separation of Concerns
+
+**What happened in the code:**
+The `AuthController` was split into `AuthController` and `UserService` across
+commits abc123 and def456. Authentication logic stayed in the controller while
+user CRUD operations moved to a dedicated service.
+
+**The principle at work:**
+Separation of Concerns -- different responsibilities should live in different
+modules so each can change independently.
+
+**Why it matters:**
+Before the split, any change to user management risked breaking authentication.
+Now each module can evolve independently with a clear interface between them.
+
+**Takeaway for next time:**
+When a file handles two distinct responsibilities, split early -- it's cheaper
+than untangling them later.
+```
+
+## Prerequisites
+
+- Must be in a git repository with commit history
+- Works best with descriptive commit messages
+
+## Related Files
+
+- `references/se-principles.md` -- Curated SE principles catalog
+- `references/anti-patterns.md` -- Common anti-patterns to detect in diffs