Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private
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.
Sample rules shown
3
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
package_exports
infrastructure-package-exports-err-package-path-not-exported-when-importing-an-es-5b7e702d
IFERR_PACKAGE_PATH_NOT_EXPORTED when importing an ESM package from a TypeScript/Node.js project using ESM modules.
THENUpdate the package.json of the SDK to include a proper 'exports' field that defines separate entry points for ESM and CJS consumers, ensuring the main entry point is accessible. This resolves module resolution errors for both module systems.
Tier 170%
package_exports
infrastructure-package-exports-when-attempting-to-import-an-npm-package-in-an-esm-2d7ef833
IFWhen attempting to import an npm package in an ESM project, Node.js throws ERR_PACKAGE_PATH_NOT_EXPORTED because the package's package.json lacks a proper 'exports' field.
THENUpdate the package's package.json to include an 'exports' field that defines separate entry points for ESM and CJS, e.g., using an 'import' condition and a 'require' condition, and ensure the main entry point is accessible. This resolves module resolution errors for both module systems.
Tier 170%
package_exports
mcp-package-exports-when-installing-modelcontextprotocol-sdk-directly--d46520a8
IFWhen installing @modelcontextprotocol/sdk directly from a git URL (e.g., npm install ...@github:modelcontextprotocol/typescript-sdk), the dist/ directory is missing, causing ERR_MODULE_NOT_FOUND on import.
THENUse the official npm registry version instead: `npm install @modelcontextprotocol/sdk`. If you must use a git source, build the package locally with `npm run build` before importing. As a temporary workaround, you can mix require() and import() as shown in the code_example.
Tier 170%
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