Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private
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.
Sample rules shown
1
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
mcp_publishing_automation
infrastructure-mcp-publishing-autom-a-fix-for-server-memory-is-committed-but-not-publi-1788e96f
IFA fix for server-memory is committed but not published to npm because the publish workflow is gated on the 'release' event only.
THENUpdate the GitHub Actions publish workflow to trigger on version changes (e.g., when a commit changes package.json version) or ensure that a release is cut after merging a fix. Consider adding a job that publishes on push to main if the version has been incremented, or adding a manual workflow_dispatch trigger to allow maintainers to publish fixes without a formal release.
Tier 170%
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