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.
IFCode uses long, verbose variable names in internal non-API logic.
THENReplace with single or double letter abbreviations meaningful in context, such as 'd' for data, 'cb' for callback. Keep full names only in exported APIs, type definitions, and security-critical code.
IFWhen writing code intended for LLM processing or token-sensitive contexts, using long variable names increases token count.
THENReplace descriptive variable names with single- or double-letter abbreviations that are domain-meaningful (e.g., 'd' for data, 'u' for user, 'tx' for transaction). Reserve full names for exported APIs, type definitions, and security-critical code.
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