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.
IFUser attempts to add Claude API features to a file that imports non-Anthropic SDKs (e.g., import openai, gpt-4) or is labeled provider-neutral.
THENStop and ask user to confirm switch to Claude or request a non-Claude implementation. Do not edit the file with Anthropic SDK calls without confirmation.
IFUser asks to add/modify Claude features in a file that may already use another provider.
THENScan the file for non-Anthropic provider markers (import openai, gpt-4, etc.). If found, stop and ask the user whether they want to switch to Claude or use a non-Claude implementation. Do not edit a non-Anthropic file with Anthropic SDK calls.
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