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.
IFUser expresses intent to write documentation (e.g., 'write a doc', 'draft a proposal', 'create a spec').
THENOffer a structured co-authoring workflow with three stages: Context Gathering (ask meta-questions and let user dump info), Refinement & Structure (build sections via brainstorming and iterative edits), and Reader Testing (test doc with a fresh context to catch blind spots). Guide the user through each stage, asking clarifying questions and providing options.
IFUser mentions writing documentation such as 'write a doc', 'draft a proposal', 'create a spec', or similar.
THENOffer a structured co-authoring workflow: 1) Context Gathering – ask meta-context (type, audience, desired impact, template, constraints), let user info-dump, then ask 5-10 clarifying questions; 2) Refinement & Structure – build document section by section through brainstorming (5-20 options), curation, gap checking, drafting, and iterative refinement using `str_replace` edits; 3) Reader Testing – predict reader questions and test with a fresh Claude (no context) to catch blind spots. Guide the user actively through each stage.
IFUser mentions writing documentation, proposals, specs, or similar structured content.
THENOffer a structured three-stage workflow: (1) Context Gathering: ask clarifying questions and let the user dump information; (2) Refinement & Structure: build the document section-by-section through brainstorming, curation, and iterative editing; (3) Reader Testing: test the document with a fresh instance to catch blind spots. Use integrations to pull context when available.
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