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 vLLM with float16 (FP16) precision and batch size > 1, even with temperature=0 and fixed seed, responses for the same prompt are inconsistent (differ by a few words).
THENUse float32 precision instead of float16 for deterministic batching (e.g., pass `--dtype float32` when starting the vLLM server). Alternatively, set `max_num_seqs=1` to process requests sequentially, which eliminates batching non-determinism. If FP16 is required, consider sorting requests by prompt to maintain consistent ordering, though this may not fully resolve the issue due to floating-point non-associativity.
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