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.
IFAsked to generate or modify Claude API code without an explicit language context
THENInfer the language from project files using the detection rules: `*.py`/`pyproject.toml` → Python; `*.ts`/`package.json` → TypeScript; `*.java`/`pom.xml` → Java; `*.go`/`go.mod` → Go; `*.rb`/`Gemfile` → Ruby; `*.cs`/`*.csproj` → C#; `*.php`/`composer.json` → PHP. If multiple languages detected or none, ask the user or default to Python examples.
IFNeed to generate Claude API code for a project and the language is unknown.
THENInspect project files for language indicators (e.g., *.py → Python, package.json → TypeScript, go.mod → Go). If multiple languages are detected, ask the user. If no files found, offer options: Python, TypeScript, Java, Go, Ruby, cURL, C#, PHP. For unsupported languages, suggest cURL/raw HTTP.
IFNeed to determine which SDK language to use for Claude API integration.
THENCheck project files for language indicators (.py, requirements.txt → Python; .ts, package.json → TypeScript; .java, pom.xml → Java; .go, go.mod → Go; .rb, Gemfile → Ruby; .cs → C#; .php, composer.json → PHP). If ambiguous, ask the user. If unsupported, suggest cURL/raw HTTP.
IFProject language is ambiguous or unknown when integrating Claude API.
THENCheck project files for language indicators (e.g., `*.py`, `requirements.txt` → Python; `*.ts`, `package.json` → TypeScript; etc.). If multiple detected, ask user. If unsupported, default to cURL or suggest Python/TypeScript examples.
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