bascik-compatibility
Installation
SKILL.md
HTML, CSS, and JavaScript Compatibility
Every feature passes two gates: browsers must support it for your audience, and inside a component Bascik's scoping must handle it. Page markup, page <style> and <script> blocks, and global stylesheets are not renamed, so anything a browser supports works there. Requires the bascik skill; bascik-components has the scoping rules.
Gate 1: browser support
node <skills-dir>/bascik-compatibility/scripts/baseline.mjs popover anchor-positioning "invoker commands"
| Status | Decision |
|---|---|
| Widely available | Use it |
| Newly available | Use it when the page still works without it, or behind @supports or a feature check with a fallback |
| Limited availability | Enhancement only, inside @supports or if ('x' in ...), never for content or navigation |
Never guess support from memory; statuses change every few months. The script queries the Web Platform Status API (the web-features data behind MDN and caniuse) and can take several seconds per feature. Prefer features that degrade to something usable.