[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CTFY9YQJ3X3KNJEX1PC6P6":3,"skill-same:01M7CTFY9YQJ3X3KNJEX1PC6P6":54},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CTFY9YQJ3X3KNJEX1PC6P6","upgrade-react-native",null,"Use when upgrading react-native to a newer version. Handles version bumps, native project changes (Android\u002FiOS), dependency updates, and breaking change migration. Invoke with `\u002Fupgrade-react-native \u003Cversion>`.","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\u002Freact-native-community-skills\u002Fupgrade-react-native\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: upgrade-react-native\ndescription: >\n  Use when upgrading react-native to a newer version. Handles version bumps,\n  native project changes (Android\u002FiOS), dependency updates, and breaking change\n  migration. Invoke with `\u002Fupgrade-react-native \u003Cversion>`.\nversion: 0.1.0\nlicense: MIT\n---\n\n# Upgrade React Native\n\nUpgrade a React Native Community CLI project to a target version by fetching\nand applying the diff from the\n[React Native Upgrade Helper](https:\u002F\u002Freact-native-community.github.io\u002Fupgrade-helper\u002F).\n\n\u003C!-- LLM_EXCLUDE: Human-only context below -->\n> [!Note]\n> **Expo users:** For Expo projects or more complex upgrade scenarios, try:\n> - [expo\u002Fskills\u002Fupgrading-expo](https:\u002F\u002Fskills.sh\u002Fexpo\u002Fskills\u002Fupgrading-expo)\n> - [callstackincubator\u002Fagent-skills\u002Fupgrading-react-native](https:\u002F\u002Fskills.sh\u002Fcallstackincubator\u002Fagent-skills\u002Fupgrading-react-native)\n\u003C!-- \u002FLLM_EXCLUDE -->\n\n## Invocation\n\n```\n\u002Fupgrade-react-native \u003CtargetVersion>\n```\n\n- `\u003CtargetVersion>` — the React Native version to upgrade to (e.g. `0.79.0`).\n\n## Step-by-step procedure\n\nFollow every step below **in order**. Do not skip steps.\n\n### 1. Detect the current React Native version\n\nRead the project's root `package.json` and extract the `react-native` version\nfrom `dependencies` (or `devDependencies`). Strip any semver range prefix\n(`^`, `~`, `>=`, etc.) to get the exact current version string.\n\nIf the current version cannot be determined, stop and ask the user.\n\n### 2. Validate the target version\n\n- The target version must be a valid semver string (e.g. `0.79.0`).\n- It must be **greater than** the current version.\n- Verify the target version exists by checking:\n  ```\n  https:\u002F\u002Fraw.githubusercontent.com\u002Freact-native-community\u002Frn-diff-purge\u002Fmaster\u002FRELEASES\n  ```\n  Fetch this file and confirm the target version is listed. If not, report the\n  closest available versions and ask the user to choose.\n\n### 3. Fetch the upgrade diff\n\nFetch the unified diff between the two versions:\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Freact-native-community\u002Frn-diff-purge\u002Fdiffs\u002Fdiffs\u002F\u003CcurrentVersion>..\u003CtargetVersion>.diff\n```\n\nFor example, to upgrade from `0.73.0` to `0.74.0`:\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Freact-native-community\u002Frn-diff-purge\u002Fdiffs\u002Fdiffs\u002F0.73.0..0.74.0.diff\n```\n\nIf the diff cannot be fetched (404), it may be because exact patch versions are\nnot available. Try the nearest minor versions (e.g. `0.73.0` instead of\n`0.73.2`). Report what you tried and ask the user if needed.\n\n### 4. Parse the diff and map file paths\n\nThe diff uses the template project name `RnDiffApp`. Map every path in the diff\nto the actual project:\n\n| Diff path prefix | Actual project path |\n|------------------|---------------------|\n| `RnDiffApp\u002F` | Project root (`.\u002F`) |\n\nAdditionally, replace occurrences of the template identifiers with the project's\nactual names:\n\n| Template value | Replace with |\n|----------------|--------------|\n| `RnDiffApp` | The project's app name (from `app.json` → `name`, or the `name` field in `package.json`) |\n| `rndiffapp` | Lowercase version of the project's app name |\n| `com.rndiffapp` | The project's Android package name (from `android\u002Fapp\u002Fbuild.gradle` or `android\u002Fapp\u002Fsrc\u002Fmain\u002FAndroidManifest.xml`) |\n\n### 5. Review the diff and plan changes\n\nBefore making any edits, review the entire diff and categorize changes:\n\n1. **Direct applies** — files that exist in the project and whose original\n   content matches the diff's `-` lines. These can be applied as-is.\n2. **Conflicts** — files where the project's content has diverged from the\n   template (custom modifications). These need manual merging.\n3. **New files** — files in the diff that don't exist in the project yet. Create\n   them.\n4. **Deleted files** — files the diff removes. Delete them only if the project\n   hasn't added custom content to them.\n\nPresent this plan to the user before proceeding. Group changes by area:\n\n- **Root config files** (`package.json`, `metro.config.js`, `.eslintrc.js`, etc.)\n- **iOS native files** (`ios\u002F` directory)\n- **Android native files** (`android\u002F` directory)\n- **JavaScript\u002FTypeScript source** (if any template source files changed)\n- **Third-party native dependencies** (from step 7 — include any version bumps\n  identified there)\n\n### 6. Apply changes\n\nApply the changes following the plan from step 5:\n\n- For **direct applies**: edit the file to match the diff's `+` lines.\n- For **conflicts**: apply the upgrade changes while preserving the project's\n  customizations. Use your judgement to merge. If uncertain, show both versions\n  and ask the user.\n- For **new files**: create them at the mapped path.\n- For **deleted files**: remove them.\n\n**Important considerations:**\n\n- When updating `package.json`, update the `react-native` version and any\n  related dependencies mentioned in the diff (e.g. `react`, `@react-native\u002F*`\n  packages, Gradle versions, CocoaPods versions).\n- Do NOT run `npm install` \u002F `yarn install` \u002F `pod install` automatically.\n  Inform the user these steps are needed after the upgrade.\n- Refer to the [references](#references) section for version-specific guidance\n  on breaking changes and migration notes.\n\n### 7. Update third-party native dependencies\n\nScan the project's `dependencies` and `devDependencies` in `package.json` for\nthird-party React Native libraries that contain **native code** (i.e. they have\nan `ios\u002F` or `android\u002F` directory, or are known native modules). Common examples\ninclude `react-native-screens`, `react-native-reanimated`,\n`react-native-gesture-handler`, `@react-native-async-storage\u002Fasync-storage`,\n`react-native-svg`, `react-native-safe-area-context`, etc.\n\nFor each candidate dependency:\n\n1. **Fetch the library's README** from its GitHub repository or npm page.\n2. **Look for a React Native version compatibility table or section** — many\n   native libraries document which versions of their package support which React\n   Native versions (e.g. a \"Compatibility\" or \"Version Support\" table).\n3. **If the README contains a compatibility table** that maps the target React\n   Native version to a specific library version, include that library version\n   bump in the upgrade plan.\n4. **If the README does not mention version compatibility with React Native\n   versions**, skip the library — do not guess or assume an upgrade is needed.\n\nPresent all proposed dependency bumps alongside the diff-based changes in step 5\n(grouped under a **Third-party native dependencies** section). For each:\n\n- State the current version, the proposed version, and link to the compatibility\n  info you found.\n- If multiple major versions are compatible, prefer the latest stable version\n  that supports the target React Native version.\n\nApply these version bumps to `package.json` as part of step 6.\n\n### 8. Post-upgrade checklist\n\nAfter applying all changes, present the user with a checklist:\n\n- [ ] Run `npm install` or `yarn install` to update JS dependencies\n- [ ] Run `cd ios && bundle exec pod install` (or `npx pod-install`) to update\n      native iOS dependencies\n- [ ] Run a clean build for Android: `cd android && .\u002Fgradlew clean`\n- [ ] Run a clean build for iOS: `cd ios && xcodebuild clean`\n- [ ] Run the app on both platforms to verify it launches\n- [ ] Run the project's test suite\n- [ ] Review any conflict resolutions for correctness\n- [ ] Check the [React Native changelog](https:\u002F\u002Fgithub.com\u002Ffacebook\u002Freact-native\u002Fblob\u002Fmain\u002FCHANGELOG.md) for additional breaking changes\n- [ ] Check the [Upgrade Helper web UI](https:\u002F\u002Freact-native-community.github.io\u002Fupgrade-helper\u002F?from=\u003CcurrentVersion>&to=\u003CtargetVersion>) for any supplementary notes\n\n## References\n\nConsult these for version-specific migration guidance:\n\n- [references\u002Fupgrade-helper-api.md](.\u002Freferences\u002Fupgrade-helper-api.md) — How\n  to fetch diffs and version lists programmatically\n","# Upgrade React Native\n\nUpgrade a React Native Community CLI project to a target version by fetching\nand applying the diff from the\n[React Native Upgrade Helper](https:\u002F\u002Freact-native-community.github.io\u002Fupgrade-helper\u002F).\n\n\u003C!-- LLM_EXCLUDE: Human-only context below -->\n> [!Note]\n> **Expo users:** For Expo projects or more complex upgrade scenarios, try:\n> - [expo\u002Fskills\u002Fupgrading-expo](https:\u002F\u002Fskills.sh\u002Fexpo\u002Fskills\u002Fupgrading-expo)\n> - [callstackincubator\u002Fagent-skills\u002Fupgrading-react-native](https:\u002F\u002Fskills.sh\u002Fcallstackincubator\u002Fagent-skills\u002Fupgrading-react-native)\n\u003C!-- \u002FLLM_EXCLUDE -->\n\n## Invocation\n\n```\n\u002Fupgrade-react-native \u003CtargetVersion>\n```\n\n- `\u003CtargetVersion>` — the React Native version to upgrade to (e.g. `0.79.0`).\n\n## Step-by-step procedure\n\nFollow every step below **in order**. Do not skip steps.\n\n### 1. Detect the current React Native version\n\nRead the project's root `package.json` and extract the `react-native` version\nfrom `dependencies` (or `devDependencies`). Strip any semver range prefix\n(`^`, `~`, `>=`, etc.) to get the exact current version string.\n\nIf the current version cannot be determined, stop and ask the user.\n\n### 2. Validate the target version\n\n- The target version must be a valid semver string (e.g. `0.79.0`).\n- It must be **greater than** the current version.\n- Verify the target version exists by checking:\n  ```\n  https:\u002F\u002Fraw.githubusercontent.com\u002Freact-native-community\u002Frn-diff-purge\u002Fmaster\u002FRELEASES\n  ```\n  Fetch this file and confirm the target version is listed. If not, report the\n  closest available versions and ask the user to choose.\n\n### 3. Fetch the upgrade diff\n\nFetch the unified diff between the two versions:\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Freact-native-community\u002Frn-diff-purge\u002Fdiffs\u002Fdiffs\u002F\u003CcurrentVersion>..\u003CtargetVersion>.diff\n```\n\nFor example, to upgrade from `0.73.0` to `0.74.0`:\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Freact-native-community\u002Frn-diff-purge\u002Fdiffs\u002Fdiffs\u002F0.73.0..0.74.0.diff\n```\n\nIf the diff cannot be fetched (404), it may be because exact patch versions are\nnot available. Try the nearest minor versions (e.g. `0.73.0` instead of\n`0.73.2`). Report what you tried and ask the user if needed.\n\n### 4. Parse the diff and map file paths\n\nThe diff uses the template project name `RnDiffApp`. Map every path in the diff\nto the actual project:\n\n| Diff path prefix | Actual project path |\n|------------------|---------------------|\n| `RnDiffApp\u002F` | Project root (`.\u002F`) |\n\nAdditionally, replace occurrences of the template identifiers with the project's\nactual names:\n\n| Template value | Replace with |\n|----------------|--------------|\n| `RnDiffApp` | The project's app name (from `app.json` → `name`, or the `name` field in `package.json`) |\n| `rndiffapp` | Lowercase version of the project's app name |\n| `com.rndiffapp` | The project's Android package name (from `android\u002Fapp\u002Fbuild.gradle` or `android\u002Fapp\u002Fsrc\u002Fmain\u002FAndroidManifest.xml`) |\n\n### 5. Review the diff and plan changes\n\nBefore making any edits, review the entire diff and categorize changes:\n\n1. **Direct applies** — files that exist in the project and whose original\n   content matches the diff's `-` lines. These can be applied as-is.\n2. **Conflicts** — files where the project's content has diverged from the\n   template (custom modifications). These need manual merging.\n3. **New files** — files in the diff that don't exist in the project yet. Create\n   them.\n4. **Deleted files** — files the diff removes. Delete them only if the project\n   hasn't added custom content to them.\n\nPresent this plan to the user before proceeding. Group changes by area:\n\n- **Root config files** (`package.json`, `metro.config.js`, `.eslintrc.js`, etc.)\n- **iOS native files** (`ios\u002F` directory)\n- **Android native files** (`android\u002F` directory)\n- **JavaScript\u002FTypeScript source** (if any template source files changed)\n- **Third-party native dependencies** (from step 7 — include any version bumps\n  identified there)\n\n### 6. Apply changes\n\nApply the changes following the plan from step 5:\n\n- For **direct applies**: edit the file to match the diff's `+` lines.\n- For **conflicts**: apply the upgrade changes while preserving the project's\n  customizations. Use your judgement to merge. If uncertain, show both versions\n  and ask the user.\n- For **new files**: create them at the mapped path.\n- For **deleted files**: remove them.\n\n**Important considerations:**\n\n- When updating `package.json`, update the `react-native` version and any\n  related dependencies mentioned in the diff (e.g. `react`, `@react-native\u002F*`\n  packages, Gradle versions, CocoaPods versions).\n- Do NOT run `npm install` \u002F `yarn install` \u002F `pod install` automatically.\n  Inform the user these steps are needed after the upgrade.\n- Refer to the [references](#references) section for version-specific guidance\n  on breaking changes and migration notes.\n\n### 7. Update third-party native dependencies\n\nScan the project's `dependencies` and `devDependencies` in `package.json` for\nthird-party React Native libraries that contain **native code** (i.e. they have\nan `ios\u002F` or `android\u002F` directory, or are known native modules). Common examples\ninclude `react-native-screens`, `react-native-reanimated`,\n`react-native-gesture-handler`, `@react-native-async-storage\u002Fasync-storage`,\n`react-native-svg`, `react-native-safe-area-context`, etc.\n\nFor each candidate dependency:\n\n1. **Fetch the library's README** from its GitHub repository or npm page.\n2. **Look for a React Native version compatibility table or section** — many\n   native libraries document which versions of their package support which React\n   Native versions (e.g. a \"Compatibility\" or \"Version Support\" table).\n3. **If the README contains a compatibility table** that maps the target React\n   Native version to a specific library version, include that library version\n   bump in the upgrade plan.\n4. **If the README does not mention version compatibility with React Native\n   versions**, skip the library — do not guess or assume an upgrade is needed.\n\nPresent all proposed dependency bumps alongside the diff-based changes in step 5\n(grouped under a **Third-party native dependencies** section). For each:\n\n- State the current version, the proposed version, and link to the compatibility\n  info you found.\n- If multiple major versions are compatible, prefer the latest stable version\n  that supports the target React Native version.\n\nApply these version bumps to `package.json` as part of step 6.\n\n### 8. Post-upgrade checklist\n\nAfter applying all changes, present the user with a checklist:\n\n- [ ] Run `npm install` or `yarn install` to update JS dependencies\n- [ ] Run `cd ios && bundle exec pod install` (or `npx pod-install`) to update\n      native iOS dependencies\n- [ ] Run a clean build for Android: `cd android && .\u002Fgradlew clean`\n- [ ] Run a clean build for iOS: `cd ios && xcodebuild clean`\n- [ ] Run the app on both platforms to verify it launches\n- [ ] Run the project's test suite\n- [ ] Review any conflict resolutions for correctness\n- [ ] Check the [React Native changelog](https:\u002F\u002Fgithub.com\u002Ffacebook\u002Freact-native\u002Fblob\u002Fmain\u002FCHANGELOG.md) for additional breaking changes\n- [ ] Check the [Upgrade Helper web UI](https:\u002F\u002Freact-native-community.github.io\u002Fupgrade-helper\u002F?from=\u003CcurrentVersion>&to=\u003CtargetVersion>) for any supplementary notes\n\n## References\n\nConsult these for version-specific migration guidance:\n\n- [references\u002Fupgrade-helper-api.md](.\u002Freferences\u002Fupgrade-helper-api.md) — How\n  to fetch diffs and version lists programmatically\n",{"name":5,"license":15,"version":24,"description":25},"0.1.0","Use when upgrading react-native to a newer version. Handles version bumps, native project changes (Android\u002FiOS), dependency updates, and breaking change migration. Invoke with `\u002Fupgrade-react-native \u003Cversion>`.\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Freact-native-community-skills\u002Fupgrade-react-native",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill upgrade-react-native",{"tool":40,"command":41},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill upgrade-react-native",{"tool":43,"command":44},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill upgrade-react-native","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Freact-native-community-skills\u002Fupgrade-react-native\u002FSkill.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"metadata.json","REFERENCE","参考文档",509,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Freact-native-community-skills\u002Fupgrade-react-native\u002Fmetadata.json",[55,62,67,74,79,86],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]