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.
IFUsing SemanticSplitterNodeParser's build_semantic_nodes_from_documents produces nodes without text and embedding, causing downstream index building to fail.
THENUpgrade llama_index to version 0.10.12 or later, which includes a fix to populate node.text in the build_semantic_nodes_from_documents method. If upgrading is not immediately possible, manually assign node.text from the splits after parsing. Note that node.embedding is expected to remain None at this stage (set later during index creation).
IFSemanticSplitterNodeParser produces nodes without text, causing index building to fail.
THENUpdate llama_index to a version that includes the fix for issue #11277, which ensures node.text is populated after parsing. Alternatively, manually assign the text from the split to each node after calling build_semantic_nodes_from_documents.
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