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.
IFOn Windows, MCP server processes (e.g., npx) fail to start with 'spawn ENOENT' when launched via the TypeScript SDK.
THENModify the spawn call in the client SDK (src/client/stdio.ts) to set `shell: true` when `process.platform === 'win32'`. Alternatively, replace Node's built-in `spawn` with the `cross-spawn` package, which handles Windows path resolution automatically. As a temporary patch, override the options object: `spawn(command, args, { shell: process.platform === 'win32' ? true : false })`.
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