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 a dependency extra is removed but the extra entry remains in setup.py, package managers like Poetry may fail with 'Could not parse version constraint: <empty>'.
THENEnsure that when removing a dependency extra, all corresponding entries in setup.py (or equivalent metadata files) are also removed or replaced with a valid version constraint. Perform a comprehensive cherry-pick of all changes from the PR that removes the dependency.
IFPackaging metadata for an optional dependency has an empty version constraint (e.g., '<empty>'), causing Poetry or other PEP 508 parsers to fail during install.
THENWhen removing a dependency from extras, ensure the corresponding entry is fully removed from setup.py and any other configuration files. Verify that PR cherry-picks include all relevant changes. After cleanup, validate the package metadata with tools like `pip check` or `poetry lock`.
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