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.
IFCommonJS project fails to import from an ESM-dependent package with 'ERR_REQUIRE_ESM' or 'ERR_REQUIRE_ASYNC_MODULE'
THENReplace static top-level imports with dynamic 'import()' calls. For example, instead of 'import { SSEClientTransport } from "@modelcontextprotocol/sdk/client/sse.js";', use 'const SSEClientTransport = (await import("@modelcontextprotocol/sdk/client/sse.js")).SSEClientTransport;' inside an async function. Alternatively, upgrade to a package version that explicitly handles mixed module systems (e.g., v1.9.0 of the SDK).
IFNode.js throws ERR_PACKAGE_PATH_NOT_EXPORTED when importing @modelcontextprotocol/sdk in an ESM project.
THENUpdate the SDK's package.json to include explicit "exports" fields that map entry points for both ESM and CJS consumers. Define separate exports for ESM (e.g., using a .mjs extension) and CJS (e.g., .cjs or index.js) to satisfy modern Node.js module resolution. Ensure the main entry point is listed under "exports".
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