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.
IFcreate_or_update_file fails with error 'content.encoding: Required' when content is provided as a simple string instead of an object with encoding and base64-encoded payload.
THENModify the function schema to accept content as an object with fields 'encoding' (e.g., 'base64') and 'content' (base64-encoded string), and ensure the implementation encodes the file content in base64 before sending to GitHub API.
IFcreate_or_update_file fails with error 'content.encoding: Required, content.content: Required' when called with a simple string for content.
THENModify the create_or_update_file function to accept a content object with 'encoding' and 'content' fields, and automatically base64 encode the input string. The function schema should require content to be an object with 'encoding' (string) and 'content' (string) where content is base64-encoded. Alternatively, update the implementation to automatically encode and structure the content as expected by GitHub's API.
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