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 creating bullet or numbered lists with docx-js, manually inserting Unicode bullet characters (e.g., \u2022) instead of using the numbering configuration causes inconsistent rendering across platforms, especially in Google Docs where bullets may appear as garbage.
THENDefine a numbering configuration with a reference (e.g., 'bullets') and use LevelFormat.BULLET with the bullet character as text. Then apply the numbering reference to each paragraph instead of manually inserting bullet characters.
IFManually inserting bullet characters (e.g., •) in Paragraph children causes incorrect list formatting.
THENAvoid manual bullet strings. Define numbering configuration with reference and LevelFormat.BULLET, then use Paragraph({ numbering: { reference: "bullets", level: 0 } }). Same reference continues numbering; different reference restarts.
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