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.
IFQdrantVectorStore's collection existence check treats HTTP errors (500, timeout) as 'collection does not exist', causing recreate_collection (delete+create) on add(); also stale cached state triggers the same if collection is created out-of-band after init().
THENModify _collection_exists() to raise or properly handle exceptions instead of returning False. In add(), re-check collection existence with the client rather than relying on the cached _collection_initialized flag; if the collection already exists, skip recreate_collection and use create_collection only when guaranteed absent. This prevents unintended deletion and data loss.
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