[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSMXFMD4DMS1D7Q4QBVX17":3,"skill-same:01M7CSMXFMD4DMS1D7Q4QBVX17":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":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CSMXFMD4DMS1D7Q4QBVX17","pixijs-accessibility",null,"Use this skill when adding screen reader and keyboard navigation to PixiJS v8 apps. Covers AccessibilitySystem options (enabledByDefault, debug, activateOnTab, deactivateOnMouseMove), per-container accessibility properties, shadow DOM overlay, mobile touch-hook activation. Triggers on: accessibility, a11y, screen reader, ARIA, keyboard navigation, tab order, AccessibilitySystem, accessibleTitle, accessibleHint, tabIndex, accessibleChildren.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fpixijs-pixijs-skills\u002Fpixijs-accessibility\u002Fskills\u002Fpixijs-accessibility\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pixijs-accessibility\ndescription: \"Use this skill when adding screen reader and keyboard navigation to PixiJS v8 apps. Covers AccessibilitySystem options (enabledByDefault, debug, activateOnTab, deactivateOnMouseMove), per-container accessibility properties, shadow DOM overlay, mobile touch-hook activation. Triggers on: accessibility, a11y, screen reader, ARIA, keyboard navigation, tab order, AccessibilitySystem, accessibleTitle, accessibleHint, tabIndex, accessibleChildren.\"\nlicense: MIT\n---\n\nEnable screen reader and keyboard navigation via PixiJS's AccessibilitySystem. The system creates an invisible shadow DOM overlay positioned over accessible containers so assistive technology can discover and activate them.\n\n## Quick Start\n\n```ts\nconst button = new Sprite(await Assets.load(\"button.png\"));\nbutton.accessible = true;\nbutton.accessibleTitle = \"Play game\";\nbutton.accessibleHint = \"Starts a new game session\";\nbutton.eventMode = \"static\";\nbutton.tabIndex = 0;\napp.stage.addChild(button);\n\napp.renderer.accessibility.setAccessibilityEnabled(true);\n\nbutton.on(\"pointertap\", () => startGame());\n```\n\n**Related skills:** `pixijs-events` (pointer\u002Ftap handlers), `pixijs-scene-dom-container` (HTML elements on canvas), `pixijs-application` (init options).\n\n**Key points:**\n\n- By default the system activates only after the user presses Tab. Set `enabledByDefault: true` in Application init for immediate activation.\n- On mobile, the system creates a hidden touch hook; screen-reader focus activates accessibility for the whole session.\n- The AccessibilitySystem requires the main thread; it is not available in a Web Worker.\n\n## Core Patterns\n\n### Container accessible properties\n\n```ts\nimport { Container, Sprite } from \"pixi.js\";\n\nconst container = new Container();\ncontainer.accessible = true;\ncontainer.accessibleTitle = \"Navigation menu\";\ncontainer.accessibleHint = \"Contains links to other pages\";\ncontainer.eventMode = \"static\"; \u002F\u002F required for custom tabIndex to apply\ncontainer.tabIndex = 0;\ncontainer.accessibleType = \"div\"; \u002F\u002F defaults to 'button'\n\nconst sprite = new Sprite();\nsprite.accessible = true;\nsprite.accessibleTitle = \"Close dialog\";\nsprite.accessibleText = \"X\"; \u002F\u002F text content of the shadow div\nsprite.eventMode = \"static\";\nsprite.tabIndex = 1;\n```\n\nAvailable properties on any Container:\n\n- `accessible` (boolean) - enables the accessible overlay div\n- `accessibleTitle` (string) - sets the `title` attribute on the shadow div\n- `accessibleHint` (string) - sets the `aria-label` attribute\n- `accessibleText` (string) - sets inner text content of the shadow div\n- `accessibleType` (string) - HTML tag for the shadow element, defaults to `'button'`\n- `tabIndex` (number) - tab order for keyboard navigation (only applied when `interactive` is true \u002F `eventMode` is `'static'` or `'dynamic'`)\n- `accessibleChildren` (boolean, default `true`) - when `false`, prevents child containers from being accessible\n- `accessiblePointerEvents` (string) - CSS `pointer-events` value on the shadow div\n\n### Custom tab order\n\nGive each accessible container a `tabIndex` to control the order assistive tech walks through them. Higher numbers come later; equal numbers fall back to scene-graph order.\n\n```ts\nmenuButton.accessible = true;\nmenuButton.eventMode = \"static\";\nmenuButton.tabIndex = 1;\n\nplayButton.accessible = true;\nplayButton.eventMode = \"static\";\nplayButton.tabIndex = 2;\n\nsettingsButton.accessible = true;\nsettingsButton.eventMode = \"static\";\nsettingsButton.tabIndex = 3;\n```\n\n`tabIndex` is only forwarded to the shadow div when the container is `interactive` (`eventMode` is `'static'` or `'dynamic'`). Without that, the system clamps the div's tabIndex back to `0`, and the order you set is ignored.\n\n### Programmatic control\n\n```ts\nimport { Application } from \"pixi.js\";\n\nconst app = new Application();\nawait app.init({ width: 800, height: 600 });\n\n\u002F\u002F Enable accessibility at runtime\napp.renderer.accessibility.setAccessibilityEnabled(true);\n\n\u002F\u002F Check current state\nconsole.log(app.renderer.accessibility.isActive);\nconsole.log(app.renderer.accessibility.isMobileAccessibility);\n\n\u002F\u002F Full init options:\nawait app.init({\n  accessibilityOptions: {\n    enabledByDefault: true, \u002F\u002F activate immediately (default: false)\n    debug: true, \u002F\u002F makes overlay divs visible (default: false)\n    activateOnTab: true, \u002F\u002F Tab key activates system (default: true)\n    deactivateOnMouseMove: false, \u002F\u002F stay active when mouse moves (default: true)\n  },\n});\n```\n\nThe system can also be configured via static defaults before creating the Application:\n\n```ts\nimport { AccessibilitySystem, Application } from \"pixi.js\";\n\nAccessibilitySystem.defaultOptions.enabledByDefault = true;\nAccessibilitySystem.defaultOptions.deactivateOnMouseMove = false;\n\nconst app = new Application();\nawait app.init();\n```\n\n### Handling accessible interactions\n\n```ts\nimport { Sprite } from \"pixi.js\";\n\nconst button = new Sprite();\nbutton.eventMode = \"static\";\nbutton.accessible = true;\nbutton.accessibleTitle = \"Submit form\";\nbutton.tabIndex = 0;\n\n\u002F\u002F Screen readers trigger click\u002Ftap events through the shadow DOM element\nbutton.on(\"pointertap\", () => {\n  submitForm();\n});\n```\n\nWhen accessibility is active and a user activates a shadow div (via Enter\u002FSpace key or screen reader action), the system dispatches `click`, `pointertap`, and `tap` FederatedEvents to the corresponding container. Focus on the shadow div dispatches `mouseover`, and focus-out dispatches `mouseout`. Both `eventMode` and `accessible` should be set for full keyboard + pointer support.\n\n## Common Mistakes\n\n### [MEDIUM] Expecting accessibility to be active without Tab key press\n\nThe AccessibilitySystem does not create its DOM overlay until the user presses Tab (or, on mobile, focuses the touch hook). If your application needs accessibility immediately:\n\n```ts\nconst app = new Application();\nawait app.init({\n  accessibilityOptions: {\n    enabledByDefault: true,\n  },\n});\n```\n\nOr at runtime:\n\n```ts\napp.renderer.accessibility.setAccessibilityEnabled(true);\n```\n\nWithout one of these, automated accessibility testing tools will not find the overlay elements.\n\n\n### [MEDIUM] Setting accessible without accessibleTitle\n\nWrong:\n\n```ts\nconst sprite = new Sprite();\nsprite.accessible = true;\n\u002F\u002F no title or hint set\n```\n\nCorrect:\n\n```ts\nconst sprite = new Sprite();\nsprite.accessible = true;\nsprite.accessibleTitle = \"Play button\";\nsprite.accessibleHint = \"Click to start the game\";\n```\n\nA container with `accessible = true` but no `accessibleTitle` or `accessibleHint` gets a fallback title of `\"container {tabIndex}\"`. Screen readers will announce this generic label with no useful context. Always provide at least `accessibleTitle`.\n\n\n### [MEDIUM] Accessibility deactivates when moving mouse\n\nBy default, `deactivateOnMouseMove` is `true`. Any mouse movement after Tab-activation will deactivate the overlay. This is by design (assumes keyboard-only users don't use a mouse), but it makes testing with a mouse frustrating.\n\n```ts\nawait app.init({\n  accessibilityOptions: {\n    deactivateOnMouseMove: false,\n  },\n});\n```\n\n\n### [MEDIUM] Not importing accessibility extension in custom builds\n\nWhen using `skipExtensionImports: true` for a custom build, the accessibility extension is not automatically registered. You must import it explicitly:\n\n```ts\nimport \"pixi.js\u002Faccessibility\";\nimport { Application } from \"pixi.js\";\n\nconst app = new Application();\nawait app.init({ skipExtensionImports: true });\n```\n\nWithout this import, `app.renderer.accessibility` will be undefined and no shadow DOM layer will be created.\n\n\n## API Reference\n\n- [AccessibilitySystem](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.AccessibilitySystem.html.md)\n- [AccessibilitySystemOptions](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.AccessibilitySystemOptions.html.md)\n- [AccessibilityOptions](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.AccessibilityOptions.html.md)\n- [AccessibleOptions](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.AccessibleOptions.html.md)\n- [PointerEvents](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.PointerEvents.html.md)\n","Enable screen reader and keyboard navigation via PixiJS's AccessibilitySystem. The system creates an invisible shadow DOM overlay positioned over accessible containers so assistive technology can discover and activate them.\n\n## Quick Start\n\n```ts\nconst button = new Sprite(await Assets.load(\"button.png\"));\nbutton.accessible = true;\nbutton.accessibleTitle = \"Play game\";\nbutton.accessibleHint = \"Starts a new game session\";\nbutton.eventMode = \"static\";\nbutton.tabIndex = 0;\napp.stage.addChild(button);\n\napp.renderer.accessibility.setAccessibilityEnabled(true);\n\nbutton.on(\"pointertap\", () => startGame());\n```\n\n**Related skills:** `pixijs-events` (pointer\u002Ftap handlers), `pixijs-scene-dom-container` (HTML elements on canvas), `pixijs-application` (init options).\n\n**Key points:**\n\n- By default the system activates only after the user presses Tab. Set `enabledByDefault: true` in Application init for immediate activation.\n- On mobile, the system creates a hidden touch hook; screen-reader focus activates accessibility for the whole session.\n- The AccessibilitySystem requires the main thread; it is not available in a Web Worker.\n\n## Core Patterns\n\n### Container accessible properties\n\n```ts\nimport { Container, Sprite } from \"pixi.js\";\n\nconst container = new Container();\ncontainer.accessible = true;\ncontainer.accessibleTitle = \"Navigation menu\";\ncontainer.accessibleHint = \"Contains links to other pages\";\ncontainer.eventMode = \"static\"; \u002F\u002F required for custom tabIndex to apply\ncontainer.tabIndex = 0;\ncontainer.accessibleType = \"div\"; \u002F\u002F defaults to 'button'\n\nconst sprite = new Sprite();\nsprite.accessible = true;\nsprite.accessibleTitle = \"Close dialog\";\nsprite.accessibleText = \"X\"; \u002F\u002F text content of the shadow div\nsprite.eventMode = \"static\";\nsprite.tabIndex = 1;\n```\n\nAvailable properties on any Container:\n\n- `accessible` (boolean) - enables the accessible overlay div\n- `accessibleTitle` (string) - sets the `title` attribute on the shadow div\n- `accessibleHint` (string) - sets the `aria-label` attribute\n- `accessibleText` (string) - sets inner text content of the shadow div\n- `accessibleType` (string) - HTML tag for the shadow element, defaults to `'button'`\n- `tabIndex` (number) - tab order for keyboard navigation (only applied when `interactive` is true \u002F `eventMode` is `'static'` or `'dynamic'`)\n- `accessibleChildren` (boolean, default `true`) - when `false`, prevents child containers from being accessible\n- `accessiblePointerEvents` (string) - CSS `pointer-events` value on the shadow div\n\n### Custom tab order\n\nGive each accessible container a `tabIndex` to control the order assistive tech walks through them. Higher numbers come later; equal numbers fall back to scene-graph order.\n\n```ts\nmenuButton.accessible = true;\nmenuButton.eventMode = \"static\";\nmenuButton.tabIndex = 1;\n\nplayButton.accessible = true;\nplayButton.eventMode = \"static\";\nplayButton.tabIndex = 2;\n\nsettingsButton.accessible = true;\nsettingsButton.eventMode = \"static\";\nsettingsButton.tabIndex = 3;\n```\n\n`tabIndex` is only forwarded to the shadow div when the container is `interactive` (`eventMode` is `'static'` or `'dynamic'`). Without that, the system clamps the div's tabIndex back to `0`, and the order you set is ignored.\n\n### Programmatic control\n\n```ts\nimport { Application } from \"pixi.js\";\n\nconst app = new Application();\nawait app.init({ width: 800, height: 600 });\n\n\u002F\u002F Enable accessibility at runtime\napp.renderer.accessibility.setAccessibilityEnabled(true);\n\n\u002F\u002F Check current state\nconsole.log(app.renderer.accessibility.isActive);\nconsole.log(app.renderer.accessibility.isMobileAccessibility);\n\n\u002F\u002F Full init options:\nawait app.init({\n  accessibilityOptions: {\n    enabledByDefault: true, \u002F\u002F activate immediately (default: false)\n    debug: true, \u002F\u002F makes overlay divs visible (default: false)\n    activateOnTab: true, \u002F\u002F Tab key activates system (default: true)\n    deactivateOnMouseMove: false, \u002F\u002F stay active when mouse moves (default: true)\n  },\n});\n```\n\nThe system can also be configured via static defaults before creating the Application:\n\n```ts\nimport { AccessibilitySystem, Application } from \"pixi.js\";\n\nAccessibilitySystem.defaultOptions.enabledByDefault = true;\nAccessibilitySystem.defaultOptions.deactivateOnMouseMove = false;\n\nconst app = new Application();\nawait app.init();\n```\n\n### Handling accessible interactions\n\n```ts\nimport { Sprite } from \"pixi.js\";\n\nconst button = new Sprite();\nbutton.eventMode = \"static\";\nbutton.accessible = true;\nbutton.accessibleTitle = \"Submit form\";\nbutton.tabIndex = 0;\n\n\u002F\u002F Screen readers trigger click\u002Ftap events through the shadow DOM element\nbutton.on(\"pointertap\", () => {\n  submitForm();\n});\n```\n\nWhen accessibility is active and a user activates a shadow div (via Enter\u002FSpace key or screen reader action), the system dispatches `click`, `pointertap`, and `tap` FederatedEvents to the corresponding container. Focus on the shadow div dispatches `mouseover`, and focus-out dispatches `mouseout`. Both `eventMode` and `accessible` should be set for full keyboard + pointer support.\n\n## Common Mistakes\n\n### [MEDIUM] Expecting accessibility to be active without Tab key press\n\nThe AccessibilitySystem does not create its DOM overlay until the user presses Tab (or, on mobile, focuses the touch hook). If your application needs accessibility immediately:\n\n```ts\nconst app = new Application();\nawait app.init({\n  accessibilityOptions: {\n    enabledByDefault: true,\n  },\n});\n```\n\nOr at runtime:\n\n```ts\napp.renderer.accessibility.setAccessibilityEnabled(true);\n```\n\nWithout one of these, automated accessibility testing tools will not find the overlay elements.\n\n\n### [MEDIUM] Setting accessible without accessibleTitle\n\nWrong:\n\n```ts\nconst sprite = new Sprite();\nsprite.accessible = true;\n\u002F\u002F no title or hint set\n```\n\nCorrect:\n\n```ts\nconst sprite = new Sprite();\nsprite.accessible = true;\nsprite.accessibleTitle = \"Play button\";\nsprite.accessibleHint = \"Click to start the game\";\n```\n\nA container with `accessible = true` but no `accessibleTitle` or `accessibleHint` gets a fallback title of `\"container {tabIndex}\"`. Screen readers will announce this generic label with no useful context. Always provide at least `accessibleTitle`.\n\n\n### [MEDIUM] Accessibility deactivates when moving mouse\n\nBy default, `deactivateOnMouseMove` is `true`. Any mouse movement after Tab-activation will deactivate the overlay. This is by design (assumes keyboard-only users don't use a mouse), but it makes testing with a mouse frustrating.\n\n```ts\nawait app.init({\n  accessibilityOptions: {\n    deactivateOnMouseMove: false,\n  },\n});\n```\n\n\n### [MEDIUM] Not importing accessibility extension in custom builds\n\nWhen using `skipExtensionImports: true` for a custom build, the accessibility extension is not automatically registered. You must import it explicitly:\n\n```ts\nimport \"pixi.js\u002Faccessibility\";\nimport { Application } from \"pixi.js\";\n\nconst app = new Application();\nawait app.init({ skipExtensionImports: true });\n```\n\nWithout this import, `app.renderer.accessibility` will be undefined and no shadow DOM layer will be created.\n\n\n## API Reference\n\n- [AccessibilitySystem](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.AccessibilitySystem.html.md)\n- [AccessibilitySystemOptions](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.AccessibilitySystemOptions.html.md)\n- [AccessibilityOptions](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.AccessibilityOptions.html.md)\n- [AccessibleOptions](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.AccessibleOptions.html.md)\n- [PointerEvents](https:\u002F\u002Fpixijs.download\u002Frelease\u002Fdocs\u002Faccessibility.PointerEvents.html.md)\n",{"name":5,"license":15,"description":7},"main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fpixijs-pixijs-skills\u002Fpixijs-accessibility\u002Fskills\u002Fpixijs-accessibility",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill pixijs-accessibility",{"tool":38,"command":39},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill pixijs-accessibility",{"tool":41,"command":42},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill pixijs-accessibility","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fpixijs-pixijs-skills\u002Fpixijs-accessibility\u002Fskills\u002Fpixijs-accessibility\u002FSKILL.md",true,[],[47,54,59,66,71,78],{"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},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":55,"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":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":67,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":79,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]