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 asked to write an internal communication (e.g., status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports, project updates).
THENIdentify the communication type from the request, load the appropriate guideline file from the `examples/` directory for that type (e.g., 3P-updates.md, company-newsletter.md), and follow the specific formatting, tone, and content instructions in that file. If the type doesn't match any existing guideline, ask for clarification or more context about the desired format.
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