tech-hub-skills 1.2.0 → 1.5.2

package/{tech_hub_skills → .claude}/roles/platform-engineer/skills/01-internal-developer-platform/README.md

@@ -1,153 +1,153 @@
-# pe-01: Internal Developer Platform (IDP)
-
-## Overview
-
-Build developer portals using Backstage for service catalog, golden path templates, self-service provisioning, and platform documentation.
-
-## Key Capabilities
-
-- **Developer Portal**: Centralized platform UI (Backstage)
-- **Service Catalog**: All services, APIs, documentation
-- **Golden Path Templates**: Scaffolding for new services
-- **Self-Service Provisioning**: One-click infrastructure
-- **Platform Documentation**: Unified docs portal
-
-## Tools & Technologies
-
-- **Backstage**: Open-source developer portal
-- **Port**: Developer portal platform
-- **Humanitec**: Platform orchestrator
-- **Kratix**: Platform-as-a-product framework
-
-## Implementation
-
-### 1. Backstage Setup
-
-```yaml
-# app-config.yaml
-app:
-  title: Tech Hub Platform
-  baseUrl: http://localhost:3000
-
-organization:
-  name: Tech Innovation Hub
-
-backend:
-  baseUrl: http://localhost:7007
-  listen:
-    port: 7007
-  database:
-    client: pg
-    connection:
-      host: ${POSTGRES_HOST}
-      port: ${POSTGRES_PORT}
-
-catalog:
-  providers:
-    github:
-      organization: 'your-org'
-      catalogPath: '/catalog-info.yaml'
-```
-
-### 2. Service Catalog
-
-```yaml
-# catalog-info.yaml
-apiVersion: backstage.io/v1alpha1
-kind: Component
-metadata:
-  name: customer-api
-  description: Customer management API
-  annotations:
-    github.com/project-slug: your-org/customer-api
-    sonarqube.org/project-key: customer-api
-spec:
-  type: service
-  lifecycle: production
-  owner: team-platform
-  system: customer-domain
-  providesApis:
-    - customer-api
-  consumesApis:
-    - auth-api
-```
-
-### 3. Golden Path Template
-
-```yaml
-# template.yaml
-apiVersion: scaffolder.backstage.io/v1beta3
-kind: Template
-metadata:
-  name: python-fastapi-service
-  title: Python FastAPI Service
-  description: Create a new Python FastAPI microservice
-spec:
-  owner: platform-team
-  type: service
-
-  parameters:
-    - title: Service Information
-      required:
-        - name
-        - owner
-      properties:
-        name:
-          title: Service Name
-          type: string
-          description: Unique name for the service
-        owner:
-          title: Owner
-          type: string
-          description: Team that owns this service
-
-  steps:
-    - id: fetch-template
-      name: Fetch Template
-      action: fetch:template
-      input:
-        url: ./skeleton
-        values:
-          name: ${{ parameters.name }}
-          owner: ${{ parameters.owner }}
-
-    - id: publish
-      name: Publish to GitHub
-      action: publish:github
-      input:
-        repoUrl: github.com?owner=your-org&repo=${{ parameters.name }}
-
-    - id: register
-      name: Register Component
-      action: catalog:register
-      input:
-        repoContentsUrl: ${{ steps.publish.output.repoContentsUrl }}
-        catalogInfoPath: '/catalog-info.yaml'
-```
-
-## Best Practices
-
-1. **Start Small**: Begin with service catalog, add features iteratively
-2. **Golden Paths**: Create templates for 80% of use cases
-3. **Self-Service**: Minimize manual ticket workflows
-4. **Measure Adoption**: Track active users and template usage
-5. **Documentation**: Keep docs updated and searchable
-
-## Cost Optimization
-
-- Host Backstage on Kubernetes spot instances
-- Use PostgreSQL managed service (cheaper than self-hosted)
-- Cache plugin data to reduce API calls
-- Right-size backend resources
-
-## Integration
-
-**Connects with:**
-- do-01 (CI/CD): Link to deployment pipelines
-- do-02 (Kubernetes): Service deployment info
-- pe-03 (SLO): Display SLO status
-- dg-01 (Catalog): Link to data catalog
-
-## Quick Win
-
-Deploy Backstage with GitHub integration, import 5 services to catalog, show team the unified view of their services.
+# pe-01: Internal Developer Platform (IDP)
+
+## Overview
+
+Build developer portals using Backstage for service catalog, golden path templates, self-service provisioning, and platform documentation.
+
+## Key Capabilities
+
+- **Developer Portal**: Centralized platform UI (Backstage)
+- **Service Catalog**: All services, APIs, documentation
+- **Golden Path Templates**: Scaffolding for new services
+- **Self-Service Provisioning**: One-click infrastructure
+- **Platform Documentation**: Unified docs portal
+
+## Tools & Technologies
+
+- **Backstage**: Open-source developer portal
+- **Port**: Developer portal platform
+- **Humanitec**: Platform orchestrator
+- **Kratix**: Platform-as-a-product framework
+
+## Implementation
+
+### 1. Backstage Setup
+
+```yaml
+# app-config.yaml
+app:
+  title: Tech Hub Platform
+  baseUrl: http://localhost:3000
+
+organization:
+  name: Tech Innovation Hub
+
+backend:
+  baseUrl: http://localhost:7007
+  listen:
+    port: 7007
+  database:
+    client: pg
+    connection:
+      host: ${POSTGRES_HOST}
+      port: ${POSTGRES_PORT}
+
+catalog:
+  providers:
+    github:
+      organization: 'your-org'
+      catalogPath: '/catalog-info.yaml'
+```
+
+### 2. Service Catalog
+
+```yaml
+# catalog-info.yaml
+apiVersion: backstage.io/v1alpha1
+kind: Component
+metadata:
+  name: customer-api
+  description: Customer management API
+  annotations:
+    github.com/project-slug: your-org/customer-api
+    sonarqube.org/project-key: customer-api
+spec:
+  type: service
+  lifecycle: production
+  owner: team-platform
+  system: customer-domain
+  providesApis:
+    - customer-api
+  consumesApis:
+    - auth-api
+```
+
+### 3. Golden Path Template
+
+```yaml
+# template.yaml
+apiVersion: scaffolder.backstage.io/v1beta3
+kind: Template
+metadata:
+  name: python-fastapi-service
+  title: Python FastAPI Service
+  description: Create a new Python FastAPI microservice
+spec:
+  owner: platform-team
+  type: service
+
+  parameters:
+    - title: Service Information
+      required:
+        - name
+        - owner
+      properties:
+        name:
+          title: Service Name
+          type: string
+          description: Unique name for the service
+        owner:
+          title: Owner
+          type: string
+          description: Team that owns this service
+
+  steps:
+    - id: fetch-template
+      name: Fetch Template
+      action: fetch:template
+      input:
+        url: ./skeleton
+        values:
+          name: ${{ parameters.name }}
+          owner: ${{ parameters.owner }}
+
+    - id: publish
+      name: Publish to GitHub
+      action: publish:github
+      input:
+        repoUrl: github.com?owner=your-org&repo=${{ parameters.name }}
+
+    - id: register
+      name: Register Component
+      action: catalog:register
+      input:
+        repoContentsUrl: ${{ steps.publish.output.repoContentsUrl }}
+        catalogInfoPath: '/catalog-info.yaml'
+```
+
+## Best Practices
+
+1. **Start Small**: Begin with service catalog, add features iteratively
+2. **Golden Paths**: Create templates for 80% of use cases
+3. **Self-Service**: Minimize manual ticket workflows
+4. **Measure Adoption**: Track active users and template usage
+5. **Documentation**: Keep docs updated and searchable
+
+## Cost Optimization
+
+- Host Backstage on Kubernetes spot instances
+- Use PostgreSQL managed service (cheaper than self-hosted)
+- Cache plugin data to reduce API calls
+- Right-size backend resources
+
+## Integration
+
+**Connects with:**
+- do-01 (CI/CD): Link to deployment pipelines
+- do-02 (Kubernetes): Service deployment info
+- pe-03 (SLO): Display SLO status
+- dg-01 (Catalog): Link to data catalog
+
+## Quick Win
+
+Deploy Backstage with GitHub integration, import 5 services to catalog, show team the unified view of their services.

package/{tech_hub_skills → .claude}/roles/platform-engineer/skills/02-self-service-infrastructure/README.md

@@ -1,57 +1,57 @@
-# pe-02: Self-Service Infrastructure
-
-## Overview
-
-Enable developers to provision namespaces, databases, secrets, and environments through self-service automation.
-
-## Key Capabilities
-
-- **Namespace Provisioning**: Auto-create K8s namespaces
-- **Database Provisioning**: Self-service DB creation
-- **Secret Management**: Automated secret injection
-- **Resource Quotas**: Automatic quota management
-- **Environment Management**: Dev/staging/prod provisioning
-
-## Implementation
-
-```python
-# Self-service namespace provisioning
-from kubernetes import client, config
-
-def provision_namespace(team_name, environment):
-    """Create namespace with quotas and RBAC"""
-    config.load_kube_config()
-    v1 = client.CoreV1Api()
-
-    # Create namespace
-    namespace = client.V1Namespace(
-        metadata=client.V1ObjectMeta(
-            name=f"{team_name}-{environment}",
-            labels={
-                "team": team_name,
-                "environment": environment
-            }
-        )
-    )
-    v1.create_namespace(namespace)
-
-    # Apply resource quota
-    quota = client.V1ResourceQuota(
-        metadata=client.V1ObjectMeta(name="default-quota"),
-        spec=client.V1ResourceQuotaSpec(
-            hard={
-                "requests.cpu": "10",
-                "requests.memory": "20Gi",
-                "pods": "50"
-            }
-        )
-    )
-    v1.create_namespaced_resource_quota(
-        namespace=namespace.metadata.name,
-        body=quota
-    )
-```
-
-## Integration
-
-**Connects with:** do-02 (Kubernetes), sa-06 (Secrets), pe-01 (IDP)
+# pe-02: Self-Service Infrastructure
+
+## Overview
+
+Enable developers to provision namespaces, databases, secrets, and environments through self-service automation.
+
+## Key Capabilities
+
+- **Namespace Provisioning**: Auto-create K8s namespaces
+- **Database Provisioning**: Self-service DB creation
+- **Secret Management**: Automated secret injection
+- **Resource Quotas**: Automatic quota management
+- **Environment Management**: Dev/staging/prod provisioning
+
+## Implementation
+
+```python
+# Self-service namespace provisioning
+from kubernetes import client, config
+
+def provision_namespace(team_name, environment):
+    """Create namespace with quotas and RBAC"""
+    config.load_kube_config()
+    v1 = client.CoreV1Api()
+
+    # Create namespace
+    namespace = client.V1Namespace(
+        metadata=client.V1ObjectMeta(
+            name=f"{team_name}-{environment}",
+            labels={
+                "team": team_name,
+                "environment": environment
+            }
+        )
+    )
+    v1.create_namespace(namespace)
+
+    # Apply resource quota
+    quota = client.V1ResourceQuota(
+        metadata=client.V1ObjectMeta(name="default-quota"),
+        spec=client.V1ResourceQuotaSpec(
+            hard={
+                "requests.cpu": "10",
+                "requests.memory": "20Gi",
+                "pods": "50"
+            }
+        )
+    )
+    v1.create_namespaced_resource_quota(
+        namespace=namespace.metadata.name,
+        body=quota
+    )
+```
+
+## Integration
+
+**Connects with:** do-02 (Kubernetes), sa-06 (Secrets), pe-01 (IDP)

package/{tech_hub_skills → .claude}/roles/platform-engineer/skills/03-slo-sli-management/README.md

@@ -1,59 +1,59 @@
-# pe-03: SLO/SLI Management
-
-## Overview
-
-Define and track Service Level Objectives (SLOs), manage error budgets, instrument SLIs, and create SLO-based alerting.
-
-## Key Capabilities
-
-- **SLO Definition**: Availability, latency, error rate targets
-- **Error Budget Management**: Track remaining error budget
-- **SLI Instrumentation**: Collect service-level indicators
-- **SLO-Based Alerting**: Alert on error budget burn
-- **SLO Dashboards**: Visualize SLO compliance
-
-## Implementation
-
-```yaml
-# SLO definition (Sloth)
-version: prometheus/v1
-service: customer-api
-slos:
-  - name: requests-availability
-    objective: 99.9
-    description: 99.9% of requests successful
-    sli:
-      events:
-        error_query: |
-          sum(rate(http_requests_total{job="customer-api",code=~"5.."}[5m]))
-        total_query: |
-          sum(rate(http_requests_total{job="customer-api"}[5m]))
-    alerting:
-      name: CustomerAPIHighErrorRate
-      labels:
-        severity: page
-      annotations:
-        summary: High error rate on customer API
-```
-
-```python
-# Error budget calculation
-def calculate_error_budget(slo_target, time_window_days=30):
-    """Calculate remaining error budget"""
-    total_minutes = time_window_days * 24 * 60
-    allowed_downtime = total_minutes * (1 - slo_target/100)
-
-    actual_downtime = get_actual_downtime(time_window_days)
-    remaining_budget = allowed_downtime - actual_downtime
-
-    return {
-        'allowed_downtime_minutes': allowed_downtime,
-        'actual_downtime_minutes': actual_downtime,
-        'remaining_budget_minutes': remaining_budget,
-        'budget_consumed_percent': (actual_downtime / allowed_downtime) * 100
-    }
-```
-
-## Integration
-
-**Connects with:** do-08 (Monitoring), pe-01 (IDP), pe-05 (Incident Management)
+# pe-03: SLO/SLI Management
+
+## Overview
+
+Define and track Service Level Objectives (SLOs), manage error budgets, instrument SLIs, and create SLO-based alerting.
+
+## Key Capabilities
+
+- **SLO Definition**: Availability, latency, error rate targets
+- **Error Budget Management**: Track remaining error budget
+- **SLI Instrumentation**: Collect service-level indicators
+- **SLO-Based Alerting**: Alert on error budget burn
+- **SLO Dashboards**: Visualize SLO compliance
+
+## Implementation
+
+```yaml
+# SLO definition (Sloth)
+version: prometheus/v1
+service: customer-api
+slos:
+  - name: requests-availability
+    objective: 99.9
+    description: 99.9% of requests successful
+    sli:
+      events:
+        error_query: |
+          sum(rate(http_requests_total{job="customer-api",code=~"5.."}[5m]))
+        total_query: |
+          sum(rate(http_requests_total{job="customer-api"}[5m]))
+    alerting:
+      name: CustomerAPIHighErrorRate
+      labels:
+        severity: page
+      annotations:
+        summary: High error rate on customer API
+```
+
+```python
+# Error budget calculation
+def calculate_error_budget(slo_target, time_window_days=30):
+    """Calculate remaining error budget"""
+    total_minutes = time_window_days * 24 * 60
+    allowed_downtime = total_minutes * (1 - slo_target/100)
+
+    actual_downtime = get_actual_downtime(time_window_days)
+    remaining_budget = allowed_downtime - actual_downtime
+
+    return {
+        'allowed_downtime_minutes': allowed_downtime,
+        'actual_downtime_minutes': actual_downtime,
+        'remaining_budget_minutes': remaining_budget,
+        'budget_consumed_percent': (actual_downtime / allowed_downtime) * 100
+    }
+```
+
+## Integration
+
+**Connects with:** do-08 (Monitoring), pe-01 (IDP), pe-05 (Incident Management)

package/{tech_hub_skills → .claude}/roles/platform-engineer/skills/04-developer-experience/README.md

@@ -1,57 +1,57 @@
-# pe-04: Developer Experience
-
-## Overview
-
-Improve developer velocity through automated onboarding, documentation-as-code, CLI tools, and DORA metrics tracking.
-
-## Key Capabilities
-
-- **Automated Onboarding**: Zero-to-commit in < 1 hour
-- **Documentation-as-Code**: Docs in git, versioned
-- **Developer CLI**: Unified command-line tools
-- **DORA Metrics**: Deployment frequency, lead time, MTTR, change fail rate
-- **Feedback Collection**: Regular developer surveys
-
-## Implementation
-
-```bash
-# Developer CLI
-#!/bin/bash
-# platform-cli
-
-case $1 in
-  create-service)
-    backstage scaffold $2 --template python-fastapi
-    ;;
-  deploy)
-    kubectl apply -f k8s/ --namespace=$2
-    ;;
-  logs)
-    kubectl logs -f deployment/$2 -n $3
-    ;;
-  metrics)
-    open "https://grafana.company.com/d/dora-metrics"
-    ;;
-esac
-```
-
-```python
-# DORA metrics collection
-def calculate_dora_metrics(team_name, days=30):
-    """Calculate DORA metrics"""
-    deployments = get_deployments(team_name, days)
-    incidents = get_incidents(team_name, days)
-
-    metrics = {
-        'deployment_frequency': len(deployments) / days,
-        'lead_time_hours': sum(d.lead_time for d in deployments) / len(deployments),
-        'mttr_hours': sum(i.resolution_time for i in incidents) / len(incidents) if incidents else 0,
-        'change_fail_rate': len([d for d in deployments if d.failed]) / len(deployments)
-    }
-
-    return metrics
-```
-
-## Integration
-
-**Connects with:** pe-01 (IDP), do-01 (CI/CD), pe-05 (Incident Management)
+# pe-04: Developer Experience
+
+## Overview
+
+Improve developer velocity through automated onboarding, documentation-as-code, CLI tools, and DORA metrics tracking.
+
+## Key Capabilities
+
+- **Automated Onboarding**: Zero-to-commit in < 1 hour
+- **Documentation-as-Code**: Docs in git, versioned
+- **Developer CLI**: Unified command-line tools
+- **DORA Metrics**: Deployment frequency, lead time, MTTR, change fail rate
+- **Feedback Collection**: Regular developer surveys
+
+## Implementation
+
+```bash
+# Developer CLI
+#!/bin/bash
+# platform-cli
+
+case $1 in
+  create-service)
+    backstage scaffold $2 --template python-fastapi
+    ;;
+  deploy)
+    kubectl apply -f k8s/ --namespace=$2
+    ;;
+  logs)
+    kubectl logs -f deployment/$2 -n $3
+    ;;
+  metrics)
+    open "https://grafana.company.com/d/dora-metrics"
+    ;;
+esac
+```
+
+```python
+# DORA metrics collection
+def calculate_dora_metrics(team_name, days=30):
+    """Calculate DORA metrics"""
+    deployments = get_deployments(team_name, days)
+    incidents = get_incidents(team_name, days)
+
+    metrics = {
+        'deployment_frequency': len(deployments) / days,
+        'lead_time_hours': sum(d.lead_time for d in deployments) / len(deployments),
+        'mttr_hours': sum(i.resolution_time for i in incidents) / len(incidents) if incidents else 0,
+        'change_fail_rate': len([d for d in deployments if d.failed]) / len(deployments)
+    }
+
+    return metrics
+```
+
+## Integration
+
+**Connects with:** pe-01 (IDP), do-01 (CI/CD), pe-05 (Incident Management)