add-adapterAdd support to a Natterjack dashboard for an issue tracker it doesn't have yet (e.g. Azure Boards, Shortcut, GitLab Issues, YouTrack, ClickUp, Asana, Monday), or another code host for the Needs-you inbox, or another place to publish read-only code snapshots (SharePoint, Google Drive, Notion). Use wh
contributeSend improvements a team made to its Natterjack dashboard engine (natterjack/, or wherever engine.json `dir` says) back upstream as a pull request to the natterjack plugin, so every team gets them on upgrade. Use when the user wants to contribute, upstream, share or send back a dashboard change, a n
createSet up Natterjack for a team in the current workspace - a multi-repo Claude Code workspace plus a local web dashboard (Claude runs with in-page questions, issue board with Explain/Implement, one-click app start/stop, machine setup checks, docs, links, quick reference, usage) tailored to the team's s
doctorCheck a workspace's Natterjack dashboard end to end - config valid and consistent, Node version, dashboard built and running on its port, engine up to date, repos cloned, machine requirements, issue tracker connected - and fix what's wrong. Use when the dashboard won't start, a page is empty or brok
hostSet up, or finish setting up, hosted Natterjack dashboards for people without a dev machine (product, operations, support) - one shared address, a container per person, managed from the People page - on Kubernetes (GKE, EKS, AKS) or Azure App Service. Walks through the platform, images, snapshot, re
upgradeUpdate a workspace's Natterjack dashboard engine (natterjack/, or wherever engine.json `dir` says) to the engine version this plugin ships, keeping the team's own changes via a three-way merge. Use when the user wants to upgrade, update or refresh the dashboard engine, pull in new dashboard features