xo-cowork-api

Use whenever an agent creates, operates inside, or manages an xo-project. Covers scaffolding a new xo-project via the xo-cowork-api; the boot ritual, canonical file map, and closing conventions for a project folder (AGENTS.md is the operating contract); recording and updating todos across a session; and backing up, restoring, syncing, snapshotting, or migrating xo-projects through the GitHub-backed sync API. Trigger this for any mention of xo-projects, .xo/, xo-cowork-api, or AGENTS.md, and for requests to back up / restore / sync / snapshot / migrate project state — even when the user doesn't name the skill explicitly. Four hard constraints — new xo-projects are created only via the xo-cowork-api; the agent never writes to .xo/ (a watcher service owns that directory); backups and restores happen only through the sync API (never via local tar, zip, cp, rsync, or pushing to an external git remote); and when this skill covers a task, the skill is the way to do it — no improvising with shell commands or ad-hoc c

Build or refactor backend systems using FastAPI and Agno with production-safe architecture, reliability, and testing.

Implement production-ready code changes with clean architecture, backward compatibility, and proper validation.

Troubleshoot production issues by reproducing, isolating root cause, applying minimal fixes, and verifying outcomes.

General production backend engineering behavior for concise, safe, and maintainable implementation.

Perform strict production code review focusing on bugs, regressions, security, reliability, and missing tests.