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.
IFElicitResultSchema validation fails when `content: null` is used for cancel/decline responses, even though the MCP spec allows flexibility.
THENModify the ElicitResultSchema to accept `content: null` for cancel/decline actions. The schema should treat content as optional for these actions, allowing both omission and explicit null, while still requiring it for accept actions. Use a discriminated union: for 'accept' require content object; for 'cancel' and 'decline' make content optional with `z.any()`.
IFMCP GitLab server fails when parsing GitLab project API response because the Zod schema requires a 'fork' boolean field that is not always present in the API response.
THENRemove the 'fork' field from the GitLabRepositorySchema in schemas.ts. The GitLab API only includes 'fork' when the project is a fork, and it requires authentication to access. Also consider removing the 'owner' field if the self-managed instance does not return it. Alternatively, make these fields optional (e.g., z.boolean().optional()).
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