Skill: Compose-to-Kubernetes migration guide

Parent

Part of #16552 (Claude AI Skills for Podman Desktop)

Problem

Users face issues coming to Podman Desktop because they prefer Docker Compose. This preference, in turn, makes it more difficult for them to transition to Kubernetes concepts (Pods, Deployments, Services, etc.). The Podman Desktop team doesn't own the Compose experience, which limits our ability to provide hands-on guidance within the product. Users are left to piece together the mapping between Compose constructs and their Kubernetes equivalents on their own.

Proposed Skill

An agent skill that helps users migrate from Compose to Kubernetes by:

• Accepting a docker-compose.yml (pasted or file path) and explaining each service/volume/network in Kubernetes terms
• Generating equivalent Kubernetes manifests (Pod, Deployment, Service, ConfigMap, PVC) with inline explanations of why each resource maps to the corresponding Compose concept
• Calling out Compose features that don't have a direct Kubernetes equivalent and suggesting idiomatic alternatives
• Providing guidance on iterating locally with Podman Desktop's Kubernetes support (e.g. Kind/Minikube clusters, pod management UI)

Acceptance Criteria

• Skill accepts a Compose file as input and produces valid Kubernetes YAML
• Output includes explanatory annotations mapping each K8s resource back to its Compose origin
• Skill warns on unsupported or lossy translations (e.g. build: context, depends_on ordering)
• Works with Compose v2 and v3 file formats