Skip to main content
neetoplaydash setup writes NeetoPlaydash guidance into the assistant you already use, so it knows which commands exist, which flags they take, and which output format to ask for. Run the one for your tool:
You only need the ones you actually use. Each writes the same body of guidance in the format that assistant reads.

​
Where each command writes

The four project-scoped targets are files in your repository. Check them in if you want the whole team’s assistants to pick up the same guidance.

​
Claude Code

setup claude extracts the plugin rather than installing it, because Claude Code installs plugins through interactive slash commands. It prints the two commands to paste:

​
Keeping the guidance current

The written guidance is a snapshot taken from the binary that wrote it. After neetoplaydash update, re-run the setup command for your assistant to refresh it. Whatever the guidance says, the always-accurate command tree is available from the CLI itself:
That emits every command, description, and flag as JSON, which an assistant can read when it needs a flag the guidance does not mention.
The CLI is not the only way to connect an assistant. The MCP server exposes the same data over the Model Context Protocol, which suits assistants that run outside a terminal - Claude and ChatGPT on the web, for instance.