Skip to content

t1k:cocos:omarchy:winpodx

FieldValue
Moduleomarchy
Version0.4.2
Effortmedium
ToolsAskUserQuestion, Bash, Edit, Glob, Grep, Read, Write

Keywords: cocos creator hyprland, cocos creator linux, cocos creator omarchy, cocos on linux, cocos windows guest, hyprland cocos window rules, omarchy cocos, winpodx cocos, winpodx setup

/t1k:cocos:omarchy:winpodx
[init-config | --dry-run | --dest DIR | ack <id> | doctor]

Cocos Creator is Windows-only here, so on an Omarchy host it runs inside a winpodx Windows guest and its windows are composited on the Hyprland desktop. This skill turns one JSON config the user chooses into: the winpodx package, the guest, one winpodx launcher per editor/project, Hyprland window rules, and the editor-bridge port forward. Sibling skills: guest (../t1k-cocos-omarchy-guest/SKILL.md) (Dashboard/Creator inside the guest), editor-bridge (../t1k-cocos-omarchy-editor-bridge/SKILL.md), doctor (../t1k-cocos-omarchy-doctor/SKILL.md).

Host-only: every command exits 3 on a host that is not Linux + Arch-based + has omarchy and hyprctl. Nothing here touches Windows or macOS, and nothing runs against an Omarchy host unless you invoke it.

S=.claude/skills/t1k-cocos-omarchy-winpodx/scripts/cocos-omarchy.cjs (bun only).

  1. bun $S detect - exit 3 means stop: this host is out of scope.
  2. bun $S list-options --json and build the questions from that output, never from memory; skip ask:false keys.
  3. Ask with AskUserQuestion (1-4 per call, recommended option first): (a) guest size: winpodx.cpuCores, ramGb, diskSize, windowsVersion; (b) display: rdpScale, multimon; (c) the ONE host folder to share (hostFolders.share, usually the projects root) and per-project guest vs share mode; (d) Creator versions (default the kit’s pinned 3.8.7); (e) bridge ports - read each project’s port with base’s resolve-mcp-port.cjs; (f) Hyprland workspace/float. Do not write the example unasked.
  4. Write ~/.config/t1k/cocos-omarchy.json (0600) with only the chosen values changed (init-config writes the example).
  5. bun $S apply --dry-run then bun $S apply. Exit 4 means a human step is pending: present the printed handoff (open the URL / run the command), wait for the user, bun $S ack <id>, re-run apply. It resumes; finished steps are skipped. --dest <scratch> renders every file under a scratch root and runs no command.
  • Never read, print, store or ask for: the Windows password, the winpodx agent token, the bridge authToken, a Cocos account, GitHub/CPM/Jenkins tokens, a Windows ISO or licence. The config schema rejects credential-shaped keys. A custom ISO is the user’s own file: winpodx setup --win-iso <path>, run by them.
  • Files are never overwritten wholesale: owned files carry a marker and a foreign file of that name is left alone (conflict); hyprland.lua gets one marked block; pod.extra_ports is unioned with the user’s forwards.
  • The guest runs winpodx setup once (long: dockur downloads and installs Windows). Pod-level key changes on an existing guest need winpodx pod recreate (disk kept) - surfaced as a handoff, never run for the user.
  • Verification of anything inside the guest is not possible without a running guest: see verification (references/verification.md).

detect, list-options, doctor and apply --dry-run are read-only and mechanical (t1k-list-classifier may run and tabulate them). apply, ack and every handoff write files, install packages or need the user, so they stay on the session that holds the AskUserQuestion answers; no cheap-tier agent is given write access to the user’s home.

References: architecture (references/architecture.md), verification (references/verification.md).