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 AWS Bedrock Claude model generates tool calls with empty arguments (tool has no or all optional parameters), the contentBlockIndex in chunks may not match the expected sequential index, causing the same tool call to be split into multiple distinct calls.
THENIn the Bedrock invoke handler (invoke_handler.py), when adding placeholder empty arguments '{}' for tools without arguments, use the internal self.tool_calls_index counter to set the index instead of chunk_data['contentBlockIndex']. This ensures all chunk parts of a single tool call have the same index and start from 0.
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