We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFClaude Desktop starts the MCP server process twice on startup, causing conflicts for Docker containers with fixed names or socket listeners.
THENUse a bash script that first attempts to attach to an existing container (or check for a running process) before starting a new one. For Docker, wrap the command in a conditional: `docker attach <name> || docker run -i --rm --name <name> <image> <args>`. Alternatively, implement a lockfile or process-id check inside the server itself to prevent multiple instances from running simultaneously.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site