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
2
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
timezone_config
mcp-timezone-config-mcp-time-server-fails-with-zoneinfonotfounderror-w-11a8aaba
IFMCP time server fails with ZoneInfoNotFoundError when local timezone is set to an abbreviation like EDT, PDT, CST, or BST.
THENSet the --local-timezone argument to a valid IANA timezone identifier (e.g., 'America/New_York') instead of an abbreviation. If using a system that provides abbreviations, map them to IANA keys or install the tzdata package with proper zoneinfo files. Alternatively, the server code should be updated to handle abbreviations by converting to IANA keys where possible.
Tier 170%
timezone_config
mcp-timezone-config-time-server-fails-with-zoneinfonotfounderror-when--8f956cd3
IFTime server fails with ZoneInfoNotFoundError when local timezone abbreviation (e.g., EDT, PDT) is used instead of IANA timezone key.
THENExplicitly set the --local-timezone option to a valid IANA timezone identifier (e.g., 'America/New_York', 'US/Eastern') instead of relying on the local timezone abbreviation. This avoids the 'No time zone found with key' error caused by three-letter codes like EDT.
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