create-pluginlisted

# Build a Clodex plugin You are building a plugin for Clodex, the app you are running inside. This skill carries the facts that are expensive to rediscover; the authority is the contract, and where they disagree the contract wins. ## Step 0 — find the contract A Clodex **checkout** carries the contract. The installed app does not give you one you can read: its copy is inside the app archive, which your shell cannot list. So look for a checkout first: ```bash find ~/projects /Applications -maxdepth 4 -name plugin-api.md -path '*plugins*' 2>/dev/null | head -3 ``` A checkout also carries the author tools, and they are the fastest path by a wide margin: ```bash node plugins/tools/build-context.js /tmp/plugin-context.md # the full pack node plugins/tools/scaffold.js <id> <target-dir> # a plugin that already passes node plugins/tools/verify.js <dir> # run it against the REAL loader ``` **If `verify.js` exists, you must use it** — it loads the plugin through the host's own loader, so it catches what reading cannot. With no checkout, fetch the four docs from the public repo, and say in your final message that the plugin is unverified — nothing ran it: ``` https://raw.githubusercontent.com/avirtual/clodex/master/plugins/plugin-api.md https://raw.githubusercontent.com/avirtual/clodex/master/plugins/what-plugins-can-do.md https://raw.githubusercontent.com/avirtual/clodex/master/plugins/plugin-sources.md https://raw.githubusercontent.com/