Draft CLI Dev

Use this skill when the task is about developing or testing Draft CLI from this repository rather than using the installed global draft binary.

This skill exists to isolate the Draft CLI development lane from other Draft workflows on the same machine.

Use This Skill When

• working on products/notion-editor/cli
• testing Draft CLI changes from the repo
• starting a local Draft daemon for CLI development
• opening workspace files through the repo-local CLI
• avoiding conflicts with OpenClaw or another account using a different Draft daemon

Do Not Use This Skill When

• the user wants the installed global draft CLI on PATH
• the task is normal Draft page automation unrelated to CLI development
• the task is headless page automation for CI or remote agents; use draft-headless-pages instead