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 tensor parallelism (e.g., TP=4,8) with AWQ-quantized MoE models, vLLM fails with RuntimeError: 'size_k must divisible by BLOCK_SIZE_K' during model warm-up due to misaligned K dimensions in MoE layers.
THENPad the K dimension of input activation tensor A and weight tensors (B, B_scale, B_zp) to be a multiple of BLOCK_SIZE_K (typically 128) before calling the moe_wna16_gemm kernel. For weights, perform padding once at load time to avoid dynamic overhead. For activations, use torch.nn.functional.pad dynamically in the fused MoE kernel call.
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