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 using a custom GitLab domain (e.g., gitlab.company.com) for SSO, clicking the GitLab sign-in button redirects to gitlab.com instead of the custom domain, because the authorization URL is not set.
THENAdd an explicit `authorization` URL to the GitLabProvider in server/auth.ts using the `AUTH_GITLAB_ISSUER` environment variable to construct the correct OAuth authorize endpoint, e.g., `${env.AUTH_GITLAB_ISSUER}/oauth/authorize`. Alternatively, add a separate environment variable `AUTH_GITLAB_AUTH_URL` for explicit control.
IFWhen configuring Gitlab SSO with a custom Gitlab domain (not gitlab.com) using AUTH_GITLAB_ISSUER, the sign-in button redirects to gitlab.com instead of the custom domain.
THENExplicitly add an authorization URL to the GitLabProvider configuration in server/auth.ts, pointing to the custom Gitlab domain's /oauth/authorize endpoint. This overrides the default gitlab.com URL. For example, set a new environment variable AUTH_GITLAB_AUTH_URL with the custom authorization endpoint and reference it in the provider options.
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