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, the credentials file fails to load due to a duplicate drive letter prefix (e.g., 'C:\C:\...') in the resolved path.
THENModify the path construction logic to check if the path is already absolute (e.g., starts with a drive letter on Windows) before prepending a root. Use `path.resolve()` with `fileURLToPath(import.meta.url)` to compute the directory, then join relative paths normally. This ensures correct resolution on both Windows and Unix.
IFOn Windows, when running server-gdrive authentication, the package fails with 'Cannot find module C:\C:\...\gcp-oauth.keys.json' because it prepends a drive letter to an already absolute path.
THENUse fileURLToPath and path.dirname to compute __dirname from import.meta.url, then use path.resolve with relative paths ('../../../gcp-oauth.keys.json') instead of naive string concatenation. Alternatively, set the environment variables GDRIVE_OAUTH_PATH and GDRIVE_CREDENTIALS_PATH to absolute paths to bypass the bug entirely.
IFOn Windows, MCP server-gdrive fails to locate credentials file because the path resolution incorrectly prepends 'C:\' to already absolute paths, causing 'Cannot find module C:\C:\...' error.
THENReplace plain path.join or concatenation with path.resolve and fileURLToPath(import.meta.url) to compute paths based on module location. Use path.dirname + path.resolve to always produce a normalized absolute path on any OS, avoiding drive-letter duplication.
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