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.
IFCannot locate MCP server logs on Windows when following the MCP tutorial.
THENOn Windows, Claude Desktop logs are stored in `%APPDATA%\Claude\logs` (i.e., `C:\Users\YourUsername\AppData\Roaming\Claude\logs`), not in `AppData\Local`. Use `Get-Content "$env:APPDATA\Claude\logs\mcp.log" -Wait -Tail 20` to monitor logs.
IFUnable to locate MCP server logs on Windows when using paths like C:\Users\...\AppData\Local\Claude\Logs
THENUse the correct Windows log path: %APPDATA%\Claude\logs (e.g., C:\Users\<username>\AppData\Roaming\Claude\logs). For continuous monitoring, run: Get-Content "$env:APPDATA\Claude\logs\mcp.log" -Wait -Tail 20.
IFOn Windows, MCP server logs cannot be found at AppData\Local\Claude\Logs.
THENCheck the correct Windows log path: AppData\Roaming\Claude\logs. This is where Claude Desktop stores its log files, including mcp.log and mcp-server-*.log.
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