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.
IFAfter calling index.storage_context.persist(), FaissVectorStore.from_persist_dir() fails with file not found error for vector_store.json because the file is saved as default__vector_store.json due to namespace changes.
THENRename the persisted file default__vector_store.json to vector_store.json in the storage directory, or avoid using from_persist_dir() and instead load via StorageContext.from_defaults(persist_dir='./storage') which handles the namespaced filename correctly.
IFCalling FaissVectorStore.from_persist_dir() after index.storage_context.persist() fails with ValueError: No existing vector_store.json found
THENRename the persisted file from default__vector_store.json to vector_store.json in the storage directory, or ensure that both persist and load use the same naming convention. This mismatch occurs because newer LlamaIndex versions add a namespace prefix to vector store filenames.
IFFaissVectorStore.from_persist_dir fails because the persisted file is named 'default__vector_store.json' instead of 'vector_store.json'.
THENRename the file from 'default__vector_store.json' to 'vector_store.json' in the storage directory, or specify the correct path like `FaissVectorStore.from_persist_dir('./storage/default__vector_store.json')` (although that may still fail due to internal directory expectation; renaming is the confirmed workaround).
IFFaissVectorStore.from_persist_dir fails with file not found error after calling index.storage_context.persist()
THENRename the persisted file from 'default__vector_store.json' to 'vector_store.json' in the storage directory, or specify the correct path to 'default__vector_store.json' when calling from_persist_dir.
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