9pm.ai

Product guidance for working with 9pm.ai after the CLI is installed and the user has authorized access. Not the one-time setup prompt.

If this skill is not installed where your harness reads skills (or needs updating), run npx skills add tmrw-realityos/9pm-skill --skill 9pm -g — a user-level install with a shared copy at ~/.agents/skills/9pm/SKILL.md (needs npm-registry and github.com egress; a trailing PromptScript "Failed to install" line is noise — the install succeeded). Keep the -g: without it the installer writes into the user's project, and this file must never be copied into a user's project directory.

Operating Rules

• Inspect before changing.
• Ask before creating files for a new app or modifying an existing app.
• Deploy what the user built. Prefer the smallest compatibility change that preserves their stack and intent.
• Deploy the working copy the user is editing — 9pm uploads the directory you point at, not a git branch. When the user is on a branch or in a git worktree, confirm the deploy path resolves to that checkout before running (see Previews and Branches).
• Never refactor an app — especially its storage layer — to fit 9pm.ai without explicit user approval. If an app already has a working database, attach storage to it (see Persistence) rather than rewriting it.
• Run the app's existing build/test checks before deploying when available.
• Run 9pm deploy <dir> --check before the real deploy when supported.
• An app can belong to an organisation instead of the person deploying it. Deploy into one with --owner <organisation-slug> (the account must be an admin or owner of it) and list its apps with 9pm apps --owner <organisation-slug>; without the flag, everything is the account's own. Organisations are created and their members invited from the dashboard.
• 9pm deploy runs the project's own build locally — for framework apps that means npm install (and its lifecycle scripts), the framework build, or docker build execute on your machine. Only deploy directories you trust, the same way you'd trust running that project's build.
• Report the deployed URL and any follow-up risks clearly.