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.
IFUploads containing Git LFS pointer files (small text files referencing large blobs) are accepted and later cause errors in the workflow.
THENReject uploads that contain Git LFS pointer files, presumably by detecting the LFS pointer format in file content, to prevent downstream failures.
IFCancelled tasks from the UI do not stop the backend processing promptly, wasting computational resources.
THENEnsure that cancelled tasks stop backend work immediately, terminating any ongoing LLM calls or tool executions.
IFThe planner step may defer or incorrectly call tools, causing the workflow to fail without a fallback plan.
THENWhen the planner retries, fall back to a minimal valid plan if the model defers or makes incorrect tool calls, preventing complete workflow failure.
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