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.
IFAfter generating slides, you need to visually inspect them for layout issues (overlapping elements, text overflow, poor contrast, etc.).
THENConvert slides to images with `python scripts/office/soffice.py --headless --convert-to pdf output.pptx && pdftoppm -jpeg -r 150 output.pdf slide`, then use a subagent with a specific prompt to inspect each slide for overlapping, overflow, spacing, contrast, and leftover content. Fix all issues found, re-verify affected slides, and repeat until zero issues remain.
IFAfter generating a .pptx file, you need to ensure no leftover placeholder text remains (e.g., 'xxxx', 'lorem ipsum').
THENRun `python -m markitdown output.pptx | grep -iE "xxxx|lorem|ipsum|this.*(page|slide).*layout"` to detect placeholders. If any are found, fix them before finalizing.
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