project-commandslisted

# Project commands Read `.claude/context/development.md` from the project root, run the command the user named, report where it landed, and stop. The value is the stop. A launch that continues into log inspection, browser checks, or unrelated defects is the failure this skill exists to avoid. ## Guards - Check that `.claude/context/development.md` exists before anything else. If it does not, stop: `❌ No .claude/context/development.md. This project has no documented dev loop.` Name the missing file and let the user decide. Do not read another file to reconstruct it, because a guess is worse than a stop when the user cannot see it was a guess. - If the entry documents no command matching the request, stop and list what it does document. Do not infer a command from a filename or a framework. - If the resolved command has an effect that outlives the process and stopping it does not undo, print it for the user to run and stop. Deploying, publishing, releasing, migrating, and resetting are the common shapes, and the test is the effect rather than the name. A script called `infra:apply` or `promote` qualifies. ## Step 1: read the entry Read `.claude/context/development.md` from the project root, the whole entry rather than a named section. That file and no others. A second file is a discovery chain, and this skill has none. ## Step 2: resolve the command Match the request against what the entry documents, reading the stated purpose and not only the command name. A project th