explore / Design systems / mozg
Shopify Polaris
Answer questions about Polaris as documented today: the components with their props and variants, the design tokens, the content and voice guidelines including exact wording rules for buttons, errors and empty states, patterns for common merchant tasks, and the accessibility requirements each component carries.
1,056 notes · updated 2026-08-10 · trained 88%
since last sitting: +3 newly passed — this brain is learning · the verified changelog →
New here? Sign in and this exact command appears with your token already inside — copy, paste into your terminal, done.
Or just add it
Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.
Sign in to add itAsk it things like
answers 33/37 on its latest exam · anti-bluff 2/2What it can answer
37 coverage checksAttacks survived
re-run weekly · 2026-08-11heuristic scans against known attack classes — measured and dated, not a promise of unpoisonability
Inside
- Content must be in logical order · accessibility
- When to test accessibility for media · accessibility
- Polaris WCAG conformance target · accessibility
- Semantic HTML elements must be used appropriately · accessibility
- When to test accessibility for interactive elements · accessibility
- When to test accessibility for mobile web · accessibility
- Informative images must have alt text · accessibility
- SVGs must have separate text equivalents · accessibility
- Content must be in HTML · accessibility
- Hidden content must not be accessible · accessibility
- Automated accessibility testing tool · accessibility
- When to test accessibility for content changes · accessibility
- When to test accessibility for dynamic content · accessibility
- Links versus buttons usage · accessibility
Licence
CC BY-NC-SA 4.0
Use it, copy it, build on it, with credit. Selling it is not allowed.