[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DEV2XTM37B9S0QV8X9SNSW":3,"skill-same:01M7DEV2XTM37B9S0QV8X9SNSW":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7DEV2XTM37B9S0QV8X9SNSW","web-standards",null,"Use when writing or reviewing HTML, CSS, or browser JavaScript — covers semantic markup, native platform features over libraries, Baseline browser support, accessibility and APCA contrast, and optional validation with vnu, axe, and Lighthouse","kejadlen\u002Fdotfiles","kejadlen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8639?v=4","01M7DEPV4SN2WBW50SBF2KG7D1","Alpha Chen","01M7DEPV5FBX0YWCBKEVHKT8E2",10,"MIT","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fweb-standards\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: web-standards\ndescription: Use when writing or reviewing HTML, CSS, or browser JavaScript — covers semantic markup, native platform features over libraries, Baseline browser support, accessibility and APCA contrast, and optional validation with vnu, axe, and Lighthouse\n---\n\n# Web standards\n\nBuild on what the platform already does, and check claims about it\nagainst a primary source rather than memory. Browser support moves\nfaster than training data, so a feature remembered as unsupported may\nhave shipped everywhere since.\n\nFor visual design, fluid type, and Alpine.js, use `web-design`. For alt\ntext and inclusive language, use `writing-for-accessibility`.\n\n## Semantic HTML\n\nLead with semantic HTML. Reach for meaningful elements — `main`,\n`article`, `nav`, `kbd`, `details`, `dl`\u002F`dt` — before wrapping content\nin generic `div`s. Semantic markup gives the CSS something to target and\ncarries accessibility along with it.\n\n## Native before JavaScript\n\nBefore adding a library or hand-rolling behavior, check whether the\nplatform has a built-in. The following replace common dependencies:\n\n| Need | Platform feature |\n|------|------------------|\n| Modals | `\u003Cdialog>` with `showModal()` |\n| Menus, tooltips, toasts | `popover` attribute |\n| Disclosure, accordions | `\u003Cdetails>` and `\u003Csummary>`, grouped with `name` |\n| Form validation | Constraint validation: `required`, `pattern`, `:user-invalid` |\n| Parent and state selectors | `:has()` |\n| Component-level responsiveness | Container queries |\n| Preprocessor nesting | Native CSS nesting |\n| Page and state transitions | View transitions |\n| Positioning relative to another element | Anchor positioning |\n| Date, number, and list formatting | `Intl.*` |\n| URL parsing and query strings | `URL`, `URLSearchParams` |\n| Cancellable requests | `fetch` with `AbortController` |\n| Deep copies | `structuredClone()` |\n\nSome of these are newer than others. Check support before relying on\none, as described in the next section.\n\n## Browser support\n\nDefault to [Baseline] \"widely available\": features that have worked in\nevery major browser for at least 30 months. Use \"newly available\"\nfeatures only as progressive enhancement, behind `@supports` or feature\ndetection, so the page still works without them.\n\nLook up the current status on [Baseline] or [caniuse] instead of\nrecalling it. MDN pages also show a Baseline badge near the top.\n\n## Progressive enhancement\n\nForms submit and links navigate without JavaScript. JavaScript layers\nbehavior on top of working HTML, not in place of it. Keep state worth\nsharing — filters, tabs, search terms — in the URL so it survives a\nreload and a copied link.\n\n## Accessibility\n\nTarget [WCAG 2.2] level AA. It's the current W3C Recommendation, and\nthe regulations that cite WCAG 2.1 AA are satisfied by 2.2 AA too.\nWCAG 3 is still a Working Draft; don't target it.\n\nFollow the first rule of ARIA: when a native element has the semantics\nand behavior you need, use it instead of adding `role` and `aria-*` to\na `div`. A `\u003Cbutton>` is focusable, activates on Enter and Space, and\nannounces itself as a button for free.\n\nKeep focus visible and in a logical order. When a `\u003Cdialog>` or popover\ncloses, focus returns to whatever opened it. Respect\n`prefers-reduced-motion` for animation and `prefers-color-scheme` for\ntheming.\n\n## Color contrast\n\nPass WCAG 2.2 AA (4.5:1 for body text, 3:1 for large text and UI\ncomponents), then check [APCA] as a perceptual floor. APCA handles dark\nmode and thin fonts better than the WCAG 2 ratio, which overstates\ncontrast for light text on dark backgrounds. APCA is a candidate for\nWCAG 3, not a standard, so it supplements WCAG 2.2 and doesn't replace\nit.\n\nAPCA reports a lightness contrast (Lc) value that's negative for light\ntext on dark backgrounds; compare its absolute value against the\nfollowing thresholds:\n\n| Lc | Use |\n|----|-----|\n| 90 | Preferred for body text |\n| 75 | Minimum for body text (18px\u002F400, 16px\u002F500, 14px\u002F700) |\n| 60 | Minimum for other content text (24px\u002F400, 16px\u002F700) |\n| 45 | Headlines (36px\u002F400, 24px\u002F700) |\n| 30 | Minimum for any other text, and non-text elements |\n| 15 | Minimum for non-semantic elements that must stay visible |\n\nWith fluid type, check the smallest size in each `clamp()` range.\n\n## Primary sources\n\nCite specs and references, not blog summaries or recollection:\n\n- [WHATWG] for HTML, DOM, Fetch, and URL behavior\n- [MDN] for usage and examples\n- [Baseline] and [caniuse] for browser support\n- [WCAG 2.2] and [ARIA in HTML] for accessibility\n\n## Validating\n\nThese checks are optional. Run one when it's cheap and the change\ntouches markup, styles, or color. If a tool isn't available, say which\ncheck you skipped instead of installing something to get around it.\n\n| Check | Command | Needs |\n|-------|---------|-------|\n| HTML conformance | `vnu --errors-only page.html` | `vnu` (Homebrew) or `npx vnu-jar`, plus a JDK |\n| CSS conformance | `vnu --css --errors-only style.css` | Same as above |\n| Accessibility rules | `npx @axe-core\u002Fcli \u003Curl>` | Chrome |\n| Accessibility audit | `npx lighthouse \u003Curl> --only-categories=accessibility` | Chrome |\n| APCA contrast | The [APCA calculator], or `apca-w3` in a script | Nothing, or Node |\n\nAutomated checks catch only a fraction of accessibility problems; a\nclean axe run doesn't mean the page is accessible. For interactive\nchanges, also tab through the page and confirm focus stays visible and\nmoves in order.\n\n[Baseline]: https:\u002F\u002Fweb.dev\u002Fbaseline\n[caniuse]: https:\u002F\u002Fcaniuse.com\n[WCAG 2.2]: https:\u002F\u002Fwww.w3.org\u002FTR\u002FWCAG22\u002F\n[APCA]: https:\u002F\u002Fgit.apcacontrast.com\u002Fdocumentation\u002FAPCA_in_a_Nutshell\n[APCA calculator]: https:\u002F\u002Fapcacontrast.com\n[WHATWG]: https:\u002F\u002Fspec.whatwg.org\n[MDN]: https:\u002F\u002Fdeveloper.mozilla.org\n[ARIA in HTML]: https:\u002F\u002Fwww.w3.org\u002FTR\u002Fhtml-aria\u002F\n\n---\n\n*This is a self-improving skill. If you used it and it came up short — a missing command, flag, gotcha, or workflow — invoke the `self-improving-skills` skill and follow it before you finish.*\n","# Web standards\n\nBuild on what the platform already does, and check claims about it\nagainst a primary source rather than memory. Browser support moves\nfaster than training data, so a feature remembered as unsupported may\nhave shipped everywhere since.\n\nFor visual design, fluid type, and Alpine.js, use `web-design`. For alt\ntext and inclusive language, use `writing-for-accessibility`.\n\n## Semantic HTML\n\nLead with semantic HTML. Reach for meaningful elements — `main`,\n`article`, `nav`, `kbd`, `details`, `dl`\u002F`dt` — before wrapping content\nin generic `div`s. Semantic markup gives the CSS something to target and\ncarries accessibility along with it.\n\n## Native before JavaScript\n\nBefore adding a library or hand-rolling behavior, check whether the\nplatform has a built-in. The following replace common dependencies:\n\n| Need | Platform feature |\n|------|------------------|\n| Modals | `\u003Cdialog>` with `showModal()` |\n| Menus, tooltips, toasts | `popover` attribute |\n| Disclosure, accordions | `\u003Cdetails>` and `\u003Csummary>`, grouped with `name` |\n| Form validation | Constraint validation: `required`, `pattern`, `:user-invalid` |\n| Parent and state selectors | `:has()` |\n| Component-level responsiveness | Container queries |\n| Preprocessor nesting | Native CSS nesting |\n| Page and state transitions | View transitions |\n| Positioning relative to another element | Anchor positioning |\n| Date, number, and list formatting | `Intl.*` |\n| URL parsing and query strings | `URL`, `URLSearchParams` |\n| Cancellable requests | `fetch` with `AbortController` |\n| Deep copies | `structuredClone()` |\n\nSome of these are newer than others. Check support before relying on\none, as described in the next section.\n\n## Browser support\n\nDefault to [Baseline] \"widely available\": features that have worked in\nevery major browser for at least 30 months. Use \"newly available\"\nfeatures only as progressive enhancement, behind `@supports` or feature\ndetection, so the page still works without them.\n\nLook up the current status on [Baseline] or [caniuse] instead of\nrecalling it. MDN pages also show a Baseline badge near the top.\n\n## Progressive enhancement\n\nForms submit and links navigate without JavaScript. JavaScript layers\nbehavior on top of working HTML, not in place of it. Keep state worth\nsharing — filters, tabs, search terms — in the URL so it survives a\nreload and a copied link.\n\n## Accessibility\n\nTarget [WCAG 2.2] level AA. It's the current W3C Recommendation, and\nthe regulations that cite WCAG 2.1 AA are satisfied by 2.2 AA too.\nWCAG 3 is still a Working Draft; don't target it.\n\nFollow the first rule of ARIA: when a native element has the semantics\nand behavior you need, use it instead of adding `role` and `aria-*` to\na `div`. A `\u003Cbutton>` is focusable, activates on Enter and Space, and\nannounces itself as a button for free.\n\nKeep focus visible and in a logical order. When a `\u003Cdialog>` or popover\ncloses, focus returns to whatever opened it. Respect\n`prefers-reduced-motion` for animation and `prefers-color-scheme` for\ntheming.\n\n## Color contrast\n\nPass WCAG 2.2 AA (4.5:1 for body text, 3:1 for large text and UI\ncomponents), then check [APCA] as a perceptual floor. APCA handles dark\nmode and thin fonts better than the WCAG 2 ratio, which overstates\ncontrast for light text on dark backgrounds. APCA is a candidate for\nWCAG 3, not a standard, so it supplements WCAG 2.2 and doesn't replace\nit.\n\nAPCA reports a lightness contrast (Lc) value that's negative for light\ntext on dark backgrounds; compare its absolute value against the\nfollowing thresholds:\n\n| Lc | Use |\n|----|-----|\n| 90 | Preferred for body text |\n| 75 | Minimum for body text (18px\u002F400, 16px\u002F500, 14px\u002F700) |\n| 60 | Minimum for other content text (24px\u002F400, 16px\u002F700) |\n| 45 | Headlines (36px\u002F400, 24px\u002F700) |\n| 30 | Minimum for any other text, and non-text elements |\n| 15 | Minimum for non-semantic elements that must stay visible |\n\nWith fluid type, check the smallest size in each `clamp()` range.\n\n## Primary sources\n\nCite specs and references, not blog summaries or recollection:\n\n- [WHATWG] for HTML, DOM, Fetch, and URL behavior\n- [MDN] for usage and examples\n- [Baseline] and [caniuse] for browser support\n- [WCAG 2.2] and [ARIA in HTML] for accessibility\n\n## Validating\n\nThese checks are optional. Run one when it's cheap and the change\ntouches markup, styles, or color. If a tool isn't available, say which\ncheck you skipped instead of installing something to get around it.\n\n| Check | Command | Needs |\n|-------|---------|-------|\n| HTML conformance | `vnu --errors-only page.html` | `vnu` (Homebrew) or `npx vnu-jar`, plus a JDK |\n| CSS conformance | `vnu --css --errors-only style.css` | Same as above |\n| Accessibility rules | `npx @axe-core\u002Fcli \u003Curl>` | Chrome |\n| Accessibility audit | `npx lighthouse \u003Curl> --only-categories=accessibility` | Chrome |\n| APCA contrast | The [APCA calculator], or `apca-w3` in a script | Nothing, or Node |\n\nAutomated checks catch only a fraction of accessibility problems; a\nclean axe run doesn't mean the page is accessible. For interactive\nchanges, also tab through the page and confirm focus stays visible and\nmoves in order.\n\n[Baseline]: https:\u002F\u002Fweb.dev\u002Fbaseline\n[caniuse]: https:\u002F\u002Fcaniuse.com\n[WCAG 2.2]: https:\u002F\u002Fwww.w3.org\u002FTR\u002FWCAG22\u002F\n[APCA]: https:\u002F\u002Fgit.apcacontrast.com\u002Fdocumentation\u002FAPCA_in_a_Nutshell\n[APCA calculator]: https:\u002F\u002Fapcacontrast.com\n[WHATWG]: https:\u002F\u002Fspec.whatwg.org\n[MDN]: https:\u002F\u002Fdeveloper.mozilla.org\n[ARIA in HTML]: https:\u002F\u002Fwww.w3.org\u002FTR\u002Fhtml-aria\u002F\n\n---\n\n*This is a self-improving skill. If you used it and it came up short — a missing command, flag, gotcha, or workflow — invoke the `self-improving-skills` skill and follow it before you finish.*\n",{"name":5,"description":7},"main","54400d2fb3ebb925baf35311c647aaa31e7a5222","ai\u002Fskills\u002Fweb-standards",0,"https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fkejadlen","https:\u002F\u002Fkejadlen.dev","2026-11-14 03:39:37",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kejadlen\u002Fdotfiles --skill web-standards",{"tool":38,"command":39},"bunx","bunx skills add kejadlen\u002Fdotfiles --skill web-standards",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kejadlen\u002Fdotfiles --skill web-standards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fweb-standards\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7DEVM19CB8GSCZV56PHA594","zoekt","Use when searching code across repositories — prefer zoekt over grep\u002Fripgrep for indexed code search. Covers indexing repos, search syntax, and query patterns.","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fzoekt\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7DEVF10JKR56RSX30PZ8BNH","writing-for-accessibility","Use when writing documentation, alt text, diagrams, or any content that should be accessible to people with disabilities. Covers alt text, color contrast, inclusive language, and accessible visuals. Also use when reviewing documents for accessibility.","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fwriting-for-accessibility\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7DEVA0Q63VMQWG32VN18XYB","writing-error-messages","Use when writing, reviewing, or improving error messages in code, CLI tools, APIs, or UIs. Covers identifying the cause, explaining the fix, and setting the right tone. Also use when error messages are vague, unactionable, or confusing.","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fwriting-error-messages\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DEV6GGF2H3FW3YCPWXRRT6","working-in-the-open","Use when making design decisions during implementation — routes rationale to the right venue (commits, task comments, code comments, or documentation) based on how durable the context needs to be","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fworking-in-the-open\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DETYVQNPNGXC094DT0PTDF","web-design","Use when designing or building web UI, frontends, or styling — covers personal web design preferences, fluid layout, and Alpine.js","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fweb-design\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DETTRHEG9X12J3N7Q45XVE","warm-handoff","Use when the user asks to \"warm handoff\", \"\u002Fwarm-handoff\", \"hand off this thread\", or \"redirect this to\". Reads a Slack thread and proposes a warm handoff message for the target channel.","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fwarm-handoff\u002FSKILL.md",[],[]]