neetoform setup writes a NeetoForm instruction file into an assistant’s
configuration. The assistant then knows the command tree, the global flags, the
output envelope and the errors to expect, so it can run neetoform for you
instead of guessing at flags.
Every target is installed the same way:
Run the command from the root of the project you want the rules to apply to.
Everything except
setup claude writes into the working directory. These
commands take no flags of their own.
Claude Code
Claude Code installs plugins through interactive slash commands, so the setup command extracts the plugin and prints the two commands to run:~/.claude/ to exist, so install Claude Code first.
Rerunning setup
The instructions are built into the binary, so runsetup again after every
upgrade to pick up the commands and flags the new version has.
cursor and windsurf own their rules file outright. The first run prints
Wrote <path> and every later run overwrites the file and prints
Updated <path>.
copilot, gemini and codex write into a file that is usually yours, so
they manage a single block between <!-- neetoform:start --> and
<!-- neetoform:end --> marker lines. The first run appends it, and later runs
replace only that block and leave the rest of the file untouched. If the file
has a start marker with no end marker the command stops before writing anything
and asks you to fix the markers.
claude removes and re-extracts the plugin directory each time. Claude Code
picks up the new files when it next loads the plugin.
The command catalog
The instruction file lists the commands that shipped with the binary. For the full tree with every flag, an assistant can run:command, description, flags
and subcommands, and is what the instruction file tells the assistant to use
for anything it does not cover. See commands.