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.
IFText recognition accuracy is poor when detected text regions have excessive whitespace (e.g., 5px padding) compared to training data (1-2px padding).
THENAfter text detection, apply tight cropping to each detected text region using OpenCV to remove extra whitespace, reducing padding to 1-2 pixels around the text. This aligns the input with training data characteristics and improves recognition accuracy.
IFText detection cropped regions have excessive whitespace (>2px) around text, causing poor recognition accuracy.
THENTighten the crop around the detected text to leave only 1-2 pixels of whitespace. Use OpenCV to find the bounding rectangle of the text contours (e.g., cv2.boundingRect) and crop accordingly. Ensure the cropped image margins match the training data's whitespace distribution.
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