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.
IFOpensearchVectorStore.delete_doc_id uses the auto-generated node chunk UUID as the document ID (_id) instead of the original doc_id field, so documents are not deleted correctly.
THENModify delete_doc_id to use delete_by_query with a term filter on the doc_id field. Note that Amazon OpenSearch Serverless does not support delete_by_query, so an alternative approach (e.g., retrieve IDs by query and then delete by ID) may be required on AOSS.
IFOpensearchVectorClient.delete_doc_id(doc_id) tries to delete by internal `_id`, not by the original document `doc_id`, leading to incorrect deletion behavior.
THENChange the `delete_doc_id` method to use OpenSearch's `delete_by_query` to match on the stored `doc_id` field instead of the auto-generated document ID. If the backend (e.g., AOSS) does not support `delete_by_query`, implement a workaround like fetching the document first and then deleting by its `_id`.
IFOpensearchVectorStore's delete_doc_id method uses the auto-generated OpenSearch document ID instead of the stored doc_id, and lacks delete-by-query support on AWS OpenSearch Serverless.
THENImplement delete by query using the stored doc_id field, or provide a fallback for environments (like AOSS) that do not support delete by query. Ensure the method correctly identifies and removes documents by the 'doc_id' attribute.
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