القائمة
Schema reference for `kind: pod` and deploy entities — charly.yml entry shape, tree-position nesting, sidecars, pod networking. For verb-level operations see /charly-core:deploy.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
MUST be invoked before any work involving: the `charly migrate` command (the single idempotent migration that brings any opencharly config up to the latest schema CalVer), the CalVer schema-version stamp (`version: YYYY.DDD.HHMM`), the CUE-anchored HEAD/floor (`charly/schema/version.cue` → `#SchemaVersion`/`#SchemaFloor`), the declarative migration table (`charly/migrations.cue`, applied by the core op-walker in `charly/migrate_engine.go`), the `LatestSchemaVersion()` load-time gate, or adding a new schema cutover as a migration-table entry.
MUST be invoked before any work involving: charly secrets commands, Secret Service / config-file credential management, GPG-encrypted .secrets files, credential import/export, or secret administration.
Authoritative reference for the "Hard Cutover by Default" policy governing schema changes, API renames, and deprecations. Forbidden patterns, required deliverables, rationale, examples from this repo, and the no-exception enforcement: plans are authored as full-scope single-phase cutovers and executed end-to-end regardless of estimated time, context, or scope. MUST be invoked when planning or reviewing any breaking change to Go types, YAML field names, CLI flags, or OCI labels.
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + box/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.
Go CLI development: building the charly binary, running tests, understanding the source code structure. MUST be invoked before reading or modifying any Go source file in charly/.
the `libvirt:` libvirt-RPC check verb for VMs — domain info, framebuffer screenshots, send-key, passwd, QMP, qemu-guest-agent client, snapshots, events — served out-of-process by candy/plugin-vm.
| name | pod |
| description | Schema reference for `kind: pod` and deploy entities — charly.yml entry shape, tree-position nesting, sidecars, pod networking. For verb-level operations see /charly-core:deploy. |
kind: pod and deploy entities — Schema ReferenceThis skill is a thin schema pointer. For runtime verbs (charly bundle add, charly bundle del, charly update), see /charly-core:deploy.
kind: pod / a deploy nodeA pod entity declares a co-scheduled set of containers and the volumes / network / sidecars they share. A deploy node is the bind site — its first child key is the substrate kind at the EDGE (pod: the default, or vm: / k8s: / local: / android:, or group: for a targetless member group), carrying image: (the box a pod/k8s/android runs) or from: (inherit a same-kind template), plus the runtime knobs (encrypted volumes, tunnels, env, ports).
A host/remote deploy MUST use the host: FIELD on a local: (or pod:) deploy (local: {from: <template>, host: <user@machine>}) — there is NO host: venue KIND. group: here is EXCLUSIVELY the targetless deploy group; a Calamares package group is the separate package-group: kind, never group:.
Schema sources (read these for the canonical truth):
charly/deploy.go — BundleConfig + BundleNode Go types, the deploy entry shape, target discriminator.charly/spec/cue_types_gen.go (generated) — the PodSpec Go type / kind: pod shape./charly-core:deploy — the verb-level skill covering charly bundle add / charly bundle del / charly update.Nesting is expressed by tree position, not a nested: field: a resource node placed UNDER another resource node deploys INTO it (the migrated nested: — e.g. a pod → android tree), and the parent and its nested entries share the pod and the tunnel; each nested entry is a separate quadlet/process inside the same pod namespace. A resource node placed directly under a deploy is instead a sibling member (the migrated peer:). There are no authored nested: / peer: / target: / on: fields — membership is read from the tree.
sidecar: declares co-running containers with their own env-var routing (env_accept / env_require). See /charly-automation:sidecar for the topic skill.
/charly-core:deploy, /charly-core:charly-update, /charly-core:remove./charly-image:image, /charly-vm:vm, /charly-kubernetes:kubernetes, /charly-local:local-spec./charly-automation:sidecar, /charly-automation:enc.