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 organizing a skill that exceeds 500 lines or supports multiple domains/frameworks.
THENUse progressive disclosure: keep SKILL.md under 500 lines. If approaching the limit, add hierarchy with clear pointers. Reference large files from SKILL.md with guidance on when to read them. For large reference files (>300 lines), include a table of contents. For multi‑domain skills, organize by variant with a selection workflow in SKILL.md and separate reference files (e.g., cloud-deploy/references/aws.md, gcp.md, azure.md). Claude reads only the relevant reference file.
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