Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private
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.
Sample rules shown
1
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
file_exclusion
infrastructure-file-exclusion-you-want-to-exclude-build-artifacts-logs-or-other--b8d5f29f
IFYou want to exclude build artifacts, logs, or other non-essential files from being parsed and extracted by Cortex.
THENUse `cortex config exclude add <pattern>` to exclude specific directories or file patterns (e.g., `cortex config exclude add docs` or `cortex config exclude add "*.log"`). Cortex already ignores common directories like node_modules, dist, .git by default. List exclusions with `cortex config exclude list`.
Tier 170%
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