Instruction file imported from pockethost/pockethost (.cursor/rules/phio.mdc). Copyright stays with the author.

phio compatibility

Name: phio
Author: pockethost

packages/phio/ is the customer-facing CLI. It deploys via SFTP (port 2222, Ed25519 deploy key) using the vendored Kirkland sync engine (vendor/ftp-deploy/) against InstanceVfs.

Before landing changes to file access, VFS guards, SFTP key auth, or instance paths:

Read .cursor/skills/phio/SKILL.md.
Confirm phio deploy / dev still work (especially instance-root writes like .ftp-deploy-sync-state.json).
Legacy FTPS (edge ftp) changes do not affect phio unless FTPS protocol is re-enabled in phio.

phio is a pnpm workspace package (Node >=18 + tsx). The hosting stack (pockethost) requires Node 24.

phio feature documentation

Ship user-facing phio commands, flags, or behavior changes in the same change set as docs in both places:

Doc	Path
Package README	`packages/phio/README.md`
Dashboard docs	`packages/dashboard/src/routes/(static)/docs/phio/+page.md`

Update the commands list, options, and any quick-start examples in both files. Keep them aligned (same command names, flags, defaults).

Skip for internal-only work (refactors, deps, tests) with no CLI surface change.

Blog posts are separate. Use .cursor/skills/feature-blog/SKILL.md for customer announcements, not as a substitute for README or /docs/phio.

{ "ocm": "1", "id": "pockethost-pockethost-phio-rule", "kind": "skill", "name": "phio", "description": "phio customer CLI — compatibility, docs, and deploy contract", "publisher": "pockethost", "version": "1.0.0", "capabilities": { "domains": [ "legal", "customer_support" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "phio customer CLI — compatibility, docs, and deploy contract" ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/pockethost/pockethost", "path": ".cursor/rules/phio.mdc", "ref": "1f9fecfb268a24f6478444effdacdf64d3514fe9", "url": "https://github.com/pockethost/pockethost/blob/1f9fecfb268a24f6478444effdacdf64d3514fe9/.cursor/rules/phio.mdc", "key": "pockethost/pockethost/.cursor/rules/phio.mdc" }, "applies_to": [ "packages/phio/**", "packages/dashboard/src/routes/(static)/docs/phio/**", "packages/pockethost/src/services/InstanceFileAccess/**", "packages/pockethost/src/cli/commands/EdgeCommand/FtpCommand/**", "packages/pockethost/src/cli/commands/SftpCommand/**" ] }, "instructions": "# phio compatibility\n\n`packages/phio/` is the **customer-facing CLI**. It deploys via **SFTP** (port 2222, Ed25519 deploy key) using the vendored Kirkland sync engine (`vendor/ftp-deploy/`) against `InstanceVfs`.\n\nBefore landing changes to file access, VFS guards, SFTP key auth, or instance paths:\n\n1. Read [`.cursor/skills/phio/SKILL.md`](../skills/phio/SKILL.md).\n2. Confirm `phio deploy` / `dev` still work (especially instance-root writes like `.ftp-deploy-sync-state.json`).\n3. Legacy FTPS (`edge ftp`) changes do not affect phio unless FTPS protocol is re-enabled in phio.\n\nphio is a pnpm work", "cost": { "context_tokens": 349 } }

phio

About

phio compatibility

phio feature documentation

Use it

Manifest

Reviews