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.
IFWhen routing Anthropic-style requests (e.g., from Claude Code) to an Ollama model through LiteLLM, completions fail with AttributeError: 'str' object has no attribute 'get' in convert_content_list_to_str.
THENIn the prompt template handler for Ollama, check whether message content is a string or a list. If it's a string, either wrap it in a list with a {'text': content} structure or handle it without calling .get('text'). This prevents the AttributeError when content is unexpectedly a string (e.g., from Anthropic-format messages).
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