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.
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
cursor and windsurf write a standalone rules file and leave an existing one
alone, reporting Already installed. Delete the file first to refresh it.
copilot, gemini and codex append to a file that is usually yours, so they
manage a single ## NeetoForm CLI section: the first run adds it, and later
runs replace that section and leave the rest of the file untouched.