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, using fileURLToPath() with path.join() causes drive letter duplication (e.g., C:\C:\) in credential file paths.
THENUse path.dirname(fileURLToPath(import.meta.url)) once and avoid joining with absolute paths. Replace path.join() with path.resolve() for absolute paths to prevent duplicate drive letters.
IFUsers unable to authenticate due to path duplication bug on Windows need an immediate workaround.
THENManually create or move the credentials file to the correct path (without the duplicate C:). After completing the OAuth flow, locate the generated file at the erroneous path and copy it to the intended location (e.g., C:\Users\<username>\npm-cache\_npx\...\node_modules\.gdrive-server-credentials.json).
IFPath duplication (C:\C:\) occurs when saving Google Drive credentials on Windows due to improper use of fileURLToPath() and path.join().
THENIn the authenticateAndSaveCredentials function, avoid joining absolute paths. Use path.dirname(fileURLToPath(import.meta.url)) only once to get the base directory, then construct the credential path using path.join() without redundant drive letters. Alternatively, use path.resolve() instead of path.join() for absolute paths.
IFDrive letter duplication in credential file path (C:\C:\) when authenticating Google Drive MCP server on Windows.
THENAvoid using fileURLToPath(import.meta.url) with path.join if the result is already absolute. Use path.resolve() to ensure a single drive letter, or extract the directory path once and join only relative components. As a workaround, manually create the credentials file at the correct path (removing duplicate drive letter).
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