casdk-harness

Write commit messages following the Conventional Commits format. Use when composing, reviewing, or fixing git commit messages.

Amazon Web Services CLI operations and infrastructure patterns for AWS resource management. Activate when user mentions: aws, AWS, Amazon Web Services, EC2, EKS, ECS, S3, RDS, Lambda, CloudFormation, CloudWatch, IAM roles, IAM policies, aws cli commands, AWS deployment, AWS infrastructure, ECR, ALB, NLB, VPC, Route53, DynamoDB, SQS, SNS, EventBridge, Systems Manager, Secrets Manager, CloudTrail, AWS Organizations. Use for: AWS resource provisioning, aws cli commands, AWS service configuration, infrastructure-as-code for AWS, AWS best practices, OIDC authentication, IAM roles for service accounts (IRSA), AWS security patterns, multi-region deployments, high availability configurations, cost optimization, disaster recovery, Spot instances. Do NOT use for: GCP-specific resources, Azure-specific resources, Kubernetes manifests (use kubernetes-native skill), generic shell scripting unrelated to AWS, Terraform/Pulumi DSL syntax (use terraform-modules or pulumi-cdk skills for IaC DSLs).

AWS EKS cluster provisioning, configuration best practices, security hardening, cost optimization, IRSA (IAM Roles for Service Accounts), VPC CNI networking, node group management, cluster addons, and Kubernetes 1.31+ features including Gateway API v1 and native sidecar containers. Activate when user mentions: AWS EKS, Elastic Kubernetes Service, EKS cluster, eksctl, EKS node groups, managed node groups, self-managed nodes, Fargate profiles, EKS addons, VPC CNI, CoreDNS, kube-proxy, EKS OIDC provider, IRSA, IAM roles for service accounts, EKS security groups, pod security groups, EKS encryption, KMS encryption, EKS logging, control plane logs, EKS access entries, EKS cluster autoscaler, Karpenter, Gateway API on EKS, AWS Load Balancer Controller, EBS CSI driver, EFS CSI driver. Use for: EKS cluster architecture design, Terraform/Pulumi EKS provisioning, security configuration, IRSA setup, VPC networking for EKS, node group optimization, spot instance integration, cluster addon management, multi-AZ high availa

Dockerfile best practices, multi-stage builds, security scanning patterns, CI/CD validation pipelines, and container optimization strategies. Activate when user mentions: Dockerfile, container image, multi-stage build, container security, image optimization, docker build, container layers, base image, distroless, alpine, scratch image, container scanning, vulnerability scanning, dockerfile lint, hadolint, trivy, security pipeline, SBOM generation, container validation, CI/CD security gates, image attestation. Use for: Dockerfile generation patterns, security hardening, build optimization, layer caching strategies, CI/CD security integration, vulnerability management, SBOM generation, policy-as-code validation. Do NOT use for: Runtime orchestration (use kubernetes-native skill), CI/CD pipelines (use github-actions-iac skill), infrastructure provisioning (use terraform-patterns skill).

Crossplane composition patterns for cloud-native infrastructure provisioning. Provides XRD (CompositeResourceDefinition), Composition, and Claim patterns for AWS, Azure, GCP resources with security best practices, validation pipelines, and hallucination detection for AI-generated compositions. Activate when user mentions: crossplane, XRD, composite resource, composition, claim, provider config, managed resources, crossplane composition, infrastructure composition, declarative infrastructure, control plane. Use for: Generating Crossplane compositions, XRDs, Claims, ProviderConfigs, and managed resource patterns following cloud-native best practices with multi-phase validation and cost optimization. Do NOT use for: Direct Terraform/Pulumi code, CloudFormation templates, Kubernetes operators (unless Crossplane-specific), raw cloud provider APIs.

GitHub Actions CI/CD pipeline patterns for IaC deployments. Provides secure workflow configurations with OIDC authentication, multi-environment deployment strategies, reusable workflow architectures, and infrastructure validation with modern security scanning tools. Activate when user mentions: GitHub Actions, CI/CD, workflow, pipeline, deployment, OIDC, GitHub workflow, actions workflow, CI pipeline, continuous deployment, automated deployment, workflow file, .github/workflows, reusable workflows Use for: Generating GitHub Actions workflows for Terraform, Kubernetes, Helm deployments with security best practices (OIDC, Trivy scanning, validation gates, reusable patterns). Do NOT use for: GitLab CI, Jenkins, CircleCI, or other CI/CD platforms. For those, recommend platform-specific tooling.

GitLab CI/CD pipeline patterns for Infrastructure-as-Code deployments. Provides secure .gitlab-ci.yml configurations with OIDC authentication, DAG pipeline optimization, GitLab Agent for Kubernetes GitOps integration, reusable job templates, multi-environment deployment strategies, and security scanning with modern validation tools. Activate when user mentions: GitLab CI, .gitlab-ci.yml, GitLab pipelines, DAG pipelines, GitLab Agent, GitLab Runner, GitLab GitOps, CI/CD pipelines, stages, jobs, rules, needs, artifacts, GitLab deployment, GitLab security scanning, parent-child pipelines, pipeline efficiency, Flux integration with GitLab Agent. Use for: Generating GitLab CI/CD pipelines for Terraform, Kubernetes, Helm, Docker builds with security best practices (OIDC, workload identity, DAG optimization, security scanning, validation gates, artifact management, and GitLab Agent for GitOps). Do NOT use for: GitHub Actions, Jenkins, CircleCI, or other CI/CD platforms. For those, recommend platform-specific tooling

GitOps patterns and best practices for Argo CD continuous delivery. Provides Argo CD Application and ApplicationSet manifests, multi-environment deployment strategies, sync wave orchestration, security hardening patterns, and cost optimization configurations with CI/CD integration. Activate when user mentions: Argo CD, ArgoCD, GitOps, Application manifest, ApplicationSet, sync waves, progressive rollouts, image updater, App of Apps, declarative deployment, automated sync, Argo Rollouts integration, GitHub Actions GitOps, GitLab Agent, Flux integration. Use for: Generating Argo CD resources, multi-tenant patterns, progressive delivery, dependency management via sync waves, health checks, automated image updates, OIDC authentication, security scanning integration, cost-optimized workload deployment, CI/CD pipeline integration with GitHub Actions and GitLab. Do NOT use for: Standalone Kubernetes manifests (use kubernetes-native skill), Flux CD patterns, Jenkins pipelines, or non-GitOps deployment strategies.

GitOps patterns and best practices for Flux CD continuous delivery. Provides Flux manifests, HelmRelease configurations, Kustomization patterns, multi-environment deployment strategies, security hardening, and cost optimization. Activate when user mentions: Flux, FluxCD, GitOps, HelmRelease, Kustomization, image automation, git reconciliation, continuous delivery, helm controller, source controller, notification controller, flux bootstrap, Gateway API with Flux. Use for: Generating Flux resources, multi-tenant patterns, progressive delivery, dependency ordering, health checks, post-build variable substitution, OIDC authentication, security scanning integration, cost-optimized workload management. Do NOT use for: Standalone Kubernetes manifests (use kubernetes-native skill), Argo CD patterns, Jenkins pipelines, or non-GitOps deployment strategies.

Helm chart development patterns, template best practices, values schema validation, chart testing, OCI registry publishing, library charts, Helmfile orchestration, security hardening, and multi-environment deployment strategies. Activate when user mentions: Helm, Helm chart, values.yaml, Chart.yaml, helm template, helm install, helm upgrade, helm lint, helm test, Helmfile, chart dependencies, subchart, umbrella chart, library chart, OCI registry, helm hooks, chart museum, values schema, values.schema.json, chart testing, ct lint, helm package, helm push, chart signing, provenance, Sigstore, cosign, helm secrets, helm diff. Use for: Generating Helm charts, chart templates, values files, schema validation, chart testing patterns, multi-environment value overlays, Helmfile orchestration, library chart patterns, OCI registry workflows, chart security and signing, umbrella chart composition, hook lifecycle management. Do NOT use for: Raw Kubernetes manifests (use kubernetes-native skill), Kustomize overlays (use k

Kubernetes native resource patterns, Gateway API v1 implementations, native sidecar containers, workload best practices, resource optimization, security hardening, and multi-environment deployment strategies. Activate when user mentions: Kubernetes manifests, Deployment, StatefulSet, Service, ConfigMap, Secret, Gateway API, HTTPRoute, native sidecars, init containers, Pod lifecycle, resource requests/limits, HPA (Horizontal Pod Autoscaler), VPA (Vertical Pod Autoscaler), PDB (Pod Disruption Budget), RBAC, ServiceAccount, NetworkPolicy, PodSecurityPolicy, SecurityContext, kubeconform validation, Kustomize overlays, spot instance tolerations, node affinity, taints and tolerations. Use for: Native Kubernetes resource generation, Gateway API v1 migration, lifecycle management, security contexts, resource optimization, cost-effective scheduling, multi-environment configurations. Do NOT use for: Helm charts (use helm-charts skill), GitOps patterns (use gitops-flux or gitops-argocd skills), container image generatio

Pulumi and AWS CDK patterns for Infrastructure-as-Code using modern programming languages (TypeScript, Python, Go). Type-safe infrastructure with real language features (loops, conditionals, functions), reusable components, multi-cloud abstractions, and GitOps integration patterns. Includes AI-assisted generation validation and security-first deployment workflows. Activate when user mentions: Pulumi, AWS CDK, CDK for Terraform (CDKTF), infrastructure as real code, TypeScript infrastructure, Python infrastructure, Go infrastructure, Pulumi stacks, CDK constructs, ComponentResource, pulumi up, cdk deploy, cdk diff, Pulumi ESC, Pulumi Automation API, CDK Pipelines, L1/L2/L3 constructs, CrossGuard policies, pulumi preview, infrastructure components, multi-cloud abstractions, AI-generated infrastructure, policy-as-code validation. Use for: Type-safe infrastructure code generation, component library development, multi-cloud abstractions, testing infrastructure with real language test frameworks (Jest, pytest, Go te

Codebase analysis patterns for infrastructure projects. Identifies dependencies, service architecture, resource patterns, IaC tool usage, security posture, and cost optimization opportunities across repositories. Activate when user mentions: analyze repository, scan codebase, dependency mapping, service discovery, infrastructure audit, IaC detection, analyze project structure, understand services, map dependencies, detect frameworks, security assessment, cost analysis Use for: Understanding existing infrastructure codebases, identifying patterns, mapping service dependencies, detecting IaC tools and frameworks, assessing security posture, identifying cost optimization opportunities Do NOT use for: Generating new infrastructure code, modifying existing resources, deployment operations, runtime debugging, active penetration testing

Security scanning, policy validation, compliance enforcement, and vulnerability management for IaC resources. Integrates Trivy (2026 standard), Checkov, OPA/Conftest, and automated threat detection with CI/CD workflows. Activate when user mentions: security scan, vulnerability scanning, policy validation, compliance check, security hardening, Trivy, Checkov, tfsec (migrate to Trivy), OPA, Conftest, policy-as-code, secret scanning, SBOM generation, CVE detection, security gate, compliance framework, CIS benchmark, PCI-DSS, GDPR, HIPAA, SOC2, security baseline, threat detection, misconfig detection, CRITICAL/HIGH severity, .trivyignore, exception handling, false positives, security posture. Use for: Pre-deployment security validation, policy enforcement, vulnerability detection, compliance verification, secret detection, SBOM generation for audit trails, CI/CD security gates, multi-phase validation pipelines, hallucination detection in AI-generated IaC, hardened defaults enforcement. Do NOT use for: Runtime sec

Terraform and OpenTofu module patterns, best practices, and code generation. Provides reusable infrastructure patterns for AWS, GCP, Azure, and Kubernetes. Activate when user mentions: terraform, opentofu, HCL, tf files, module development, terraform modules, infrastructure modules, terraform best practices, terraform security, provider configuration, state management, terraform workspaces, remote state, terraform testing, terraform mocking, infrastructure cost optimization, spot instances. Use for: Generating terraform modules, terraform code patterns, provider configurations, variable definitions, output blocks, module composition, security patterns, native testing, cost optimization strategies, AI-assisted IaC validation. Do NOT use for: Kubernetes-native manifests (use kubernetes-native skill), repository analysis (use iac-analyzer agent), or executing terraform commands.

Start or resume CGF (Claude Gradient Feedback) optimization on a context-engineering resource. Supports agents, skills, commands, and other resource types. Invoke with resource name/path and optimization goal. Add --review for checkpoint mode where you can review and approve intermediate artifacts. Supports two modes: - **Optimization mode**: Optimize an existing resource - **Creation mode**: Create and optimize a new resource from description (use /cgf-create) <examples> - "/cgf-optimize python-expert async programming" - Optimize for async patterns - "/cgf-optimize typescript-expert --review" - With human review checkpoints - "/cgf-optimize research-team:research-specialist Context7 integration" - "/cgf-create Python async expert that helps with asyncio patterns" - "/cgf-create Kubernetes deployment agent --review" </examples>

Comprehensive code review practices including checklists, automated tools, and effective feedback

Systematic debugging, troubleshooting, and problem-solving strategies

Technical documentation, API docs, README creation, and documentation generation