[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPQKAJWHYZGQQ052QNPSCP":3,"skill-same:01M7CPQKAJWHYZGQQ052QNPSCP":55},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CPQKAJWHYZGQQ052QNPSCP","mcore-testing",null,"Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fmcore-testing\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mcore-testing\ndescription: Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.\nlicense: Apache-2.0\nwhen_to_use: Adding or running a unit or functional test; understanding the test layout; writing a recipe YAML; downloading or updating golden values; reproducing a test failure locally; 'how do I add a test', 'run unit tests', 'pytest fails', 'test layout', 'golden values', 'recipe YAML', 'marker filter'.\nmetadata:\n  author: Philip Petrakian \u003Cppetrakian@nvidia.com>\n---\n\n# Testing Guide\n\n---\n\n## Answer-First Testing Facts\n\nFor questions about disabling tests without deleting them:\n\n- Functional recipe entries stay in YAML; disable by suffixing scope with\n  `-broken`, for example `scope: [mr-github]` -> `scope: [mr-github-broken]`.\n- Unit-test skips use pytest markers instead: `@pytest.mark.flaky_in_dev` skips\n  in the default dev environment, and `@pytest.mark.flaky` skips in LTS.\n- Do not delete the test case or recipe entry when the goal is discoverability\n  and easy re-enable.\n\n---\n\n## Test Layout\n\n```text\ntests\u002F\n├── unit_tests\u002F          # pytest, 1 node × 8 GPUs, torch.distributed runner\n├── functional_tests\u002F    # end-to-end shell + training scripts\n│   └── test_cases\u002F\n│       └── {model}\u002F{test_case}\u002F\n│           ├── model_config.yaml          # training args\n│           └── golden_values_{env}_{platform}.json\n└── test_utils\u002F\n    ├── recipes\u002F\n    │   ├── h100\u002F        # YAML recipes for H100 jobs\n    │   └── gb200\u002F       # YAML recipes for GB200 jobs\n    └── python_scripts\u002F  # helpers (recipe_parser, golden-value download, …)\n```\n\n---\n\n## How Tests Execute\n\nThe GitHub Actions runner invokes `launch_nemo_run_workload.py`, which uses\n**nemo-run** to launch a `DockerExecutor` container. The repo is bind-mounted\nat `\u002Fopt\u002Fmegatron-lm`; training data is mounted at `\u002Fmnt\u002Fartifacts`.\n\n**Unit tests** are dispatched through `torch.distributed.run`:\n\n- Ranks 0 and 3 are tee-d to stdout; all other ranks write only to log files.\n- Per-rank log files land at `{assets_dir}\u002Flogs\u002F1\u002F` and are uploaded as a\n  GitHub artifact after the run.\n\n**Functional tests** are driven by\n`tests\u002Ffunctional_tests\u002Fshell_test_utils\u002Frun_ci_test.sh`. Only rank 0 runs the\npytest validation step; training output from all ranks is uploaded as an artifact.\n\n**Flaky-failure auto-retry**: `launch_nemo_run_workload.py` retries up to\n**3 times** for known transient patterns (NCCL timeout, ECC error, segfault,\nHuggingFace connectivity, …) before declaring a genuine failure.\n\n---\n\n## Recipe YAML Structure\n\nRecipes live in `tests\u002Ftest_utils\u002Frecipes\u002F` and are parsed by\n`tests\u002Ftest_utils\u002Fpython_scripts\u002Frecipe_parser.py`. Each file expands a\ncartesian `products` block into individual workload specs:\n\n```yaml\ntype: basic\nformat_version: 1\nmaintainers: [mcore]\nloggers: [stdout]\nspec:\n  name: \"{test_case}_{environment}_{platforms}\"\n  model: gpt              # maps to tests\u002Ffunctional_tests\u002Ftest_cases\u002F{model}\u002F\n  build: mcore-pyt-{environment}\n  nodes: 1\n  gpus: 8\n  n_repeat: 5\n  platforms: dgx_h100\n  time_limit: 1800\n  script_setup: |\n    ...\n  script: |-\n    bash tests\u002Ffunctional_tests\u002Fshell_test_utils\u002Frun_ci_test.sh ...\nproducts:\n  - test_case: [my_test]\n    products:\n      - environment: [dev, lts]\n        scope: [mr-github]\n        platforms: [dgx_h100]\n```\n\nKey runtime placeholders: `{assets_dir}`, `{artifacts_dir}`, `{test_case}`,\n`{environment}`, `{platforms}`, `{n_repeat}`.\n\n### Disabling a Test Without Deleting It\n\nTo temporarily disable a test case in a recipe YAML, suffix its `scope` value\nwith `-broken` — **do not delete the entry**:\n\n```yaml\n# before (test runs in CI)\nscope: [mr-github]\n\n# after (test is skipped; entry preserved for easy re-enable)\nscope: [mr-github-broken]\n```\n\n---\n\n## Running Unit Tests Locally\n\nAll unit tests initialize a `torch.distributed` group, so every invocation\nrequires GPU access and must go through `torch.distributed.run`:\n\n```bash\n# Full suite\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\n\n# Single file\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\u002Fmodels\u002Ftest_gpt_model.py\n\n# Single test\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\u002Fmodels\u002Ftest_gpt_model.py::TestGPTModel::test_constructor\n\n# Filter by name substring\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests -k optimizer\n```\n\n### Marker filters\n\n```bash\n# Exclude flaky tests during development\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests -m \"not flaky and not flaky_in_dev\"\n\n# Include experimental tests\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests --experimental\n```\n\n### CI parity\n\nUse `tests\u002Funit_tests\u002Frun_ci_test.sh` to reproduce a CI bucket failure exactly.\nFor ad-hoc runs, prefer the direct `torch.distributed.run` invocations above.\n\n### Gotchas\n\n- `pyproject.toml` sets `addopts = --durations=15 -s -rA` — stdout is not\n  captured (`-s`), so ranks interleave during multi-rank runs. Override with\n  `--capture=fd` when debugging a specific rank.\n- `tests\u002Funit_tests\u002Fconftest.py` looks for test data under `\u002Fopt\u002Fdata` and\n  attempts a download if missing. Supply it manually or skip data-dependent\n  tests when running outside the canonical container.\n\n---\n\n## Adding a Unit Test\n\n1. Create `tests\u002Funit_tests\u002F\u003Ccategory>\u002Ftest_\u003Cname>.py`.\n2. Use fixtures from `tests\u002Funit_tests\u002Fconftest.py`.\n3. Apply markers as needed:\n   - `@pytest.mark.internal` — skipped on `legacy` tag\n   - `@pytest.mark.flaky_in_dev` — skipped in `dev` environment (CI default; use this to disable a flaky test without blocking the standard pipeline)\n   - `@pytest.mark.flaky` — skipped in `lts` environment\n   - `@pytest.mark.experimental` — `latest` tag only\n4. Verify locally (see Running Unit Tests Locally above).\n5. If the test needs a dedicated CI bucket, add an entry to\n   `tests\u002Ftest_utils\u002Frecipes\u002Fh100\u002Funit-tests.yaml`.\n\n---\n\n## Adding a Functional \u002F Integration Test\n\n1. Create `tests\u002Ffunctional_tests\u002Ftest_cases\u002F\u003Cmodel>\u002F\u003Ctest_name>\u002F`.\n2. Write `model_config.yaml` with `MODEL_ARGS`, `ENV_VARS`, and `TEST_TYPE`.\n3. Add a YAML recipe under `tests\u002Ftest_utils\u002Frecipes\u002Fh100\u002F` (and `gb200\u002F` if\n   needed). Required fields: `scope`, `environment`, `platform`, `n_repeat`,\n   `time_limit`.\n4. Push the PR, add the label **\"Run functional tests\"** to trigger a full run.\n5. After a successful run, download golden values:\n\n   ```bash\n   python tests\u002Ftest_utils\u002Fpython_scripts\u002Fdownload_golden_values.py \\\n     --source github --pipeline-id \u003Crun-id>\n   ```\n\n6. Commit the downloaded golden values.\n\n---\n\n## Common Pitfalls\n\n| Problem | Cause | Fix |\n|---------|-------|-----|\n| Test passes locally but fails in CI | Different environment or data path | Check `DATA_PATH`, `DATA_CACHE_PATH`, and the `environment` tag (`dev` vs `lts`) |\n| Golden value mismatch after a code change | Numerical regression | Download new golden values via `download_golden_values.py` after a clean run |\n| `cicd-integration-tests-gb200` not triggered | GB200 jobs require maintainer status | Ask a maintainer to trigger, or add the `Run functional tests` label |\n","# Testing Guide\n\n---\n\n## Answer-First Testing Facts\n\nFor questions about disabling tests without deleting them:\n\n- Functional recipe entries stay in YAML; disable by suffixing scope with\n  `-broken`, for example `scope: [mr-github]` -> `scope: [mr-github-broken]`.\n- Unit-test skips use pytest markers instead: `@pytest.mark.flaky_in_dev` skips\n  in the default dev environment, and `@pytest.mark.flaky` skips in LTS.\n- Do not delete the test case or recipe entry when the goal is discoverability\n  and easy re-enable.\n\n---\n\n## Test Layout\n\n```text\ntests\u002F\n├── unit_tests\u002F          # pytest, 1 node × 8 GPUs, torch.distributed runner\n├── functional_tests\u002F    # end-to-end shell + training scripts\n│   └── test_cases\u002F\n│       └── {model}\u002F{test_case}\u002F\n│           ├── model_config.yaml          # training args\n│           └── golden_values_{env}_{platform}.json\n└── test_utils\u002F\n    ├── recipes\u002F\n    │   ├── h100\u002F        # YAML recipes for H100 jobs\n    │   └── gb200\u002F       # YAML recipes for GB200 jobs\n    └── python_scripts\u002F  # helpers (recipe_parser, golden-value download, …)\n```\n\n---\n\n## How Tests Execute\n\nThe GitHub Actions runner invokes `launch_nemo_run_workload.py`, which uses\n**nemo-run** to launch a `DockerExecutor` container. The repo is bind-mounted\nat `\u002Fopt\u002Fmegatron-lm`; training data is mounted at `\u002Fmnt\u002Fartifacts`.\n\n**Unit tests** are dispatched through `torch.distributed.run`:\n\n- Ranks 0 and 3 are tee-d to stdout; all other ranks write only to log files.\n- Per-rank log files land at `{assets_dir}\u002Flogs\u002F1\u002F` and are uploaded as a\n  GitHub artifact after the run.\n\n**Functional tests** are driven by\n`tests\u002Ffunctional_tests\u002Fshell_test_utils\u002Frun_ci_test.sh`. Only rank 0 runs the\npytest validation step; training output from all ranks is uploaded as an artifact.\n\n**Flaky-failure auto-retry**: `launch_nemo_run_workload.py` retries up to\n**3 times** for known transient patterns (NCCL timeout, ECC error, segfault,\nHuggingFace connectivity, …) before declaring a genuine failure.\n\n---\n\n## Recipe YAML Structure\n\nRecipes live in `tests\u002Ftest_utils\u002Frecipes\u002F` and are parsed by\n`tests\u002Ftest_utils\u002Fpython_scripts\u002Frecipe_parser.py`. Each file expands a\ncartesian `products` block into individual workload specs:\n\n```yaml\ntype: basic\nformat_version: 1\nmaintainers: [mcore]\nloggers: [stdout]\nspec:\n  name: \"{test_case}_{environment}_{platforms}\"\n  model: gpt              # maps to tests\u002Ffunctional_tests\u002Ftest_cases\u002F{model}\u002F\n  build: mcore-pyt-{environment}\n  nodes: 1\n  gpus: 8\n  n_repeat: 5\n  platforms: dgx_h100\n  time_limit: 1800\n  script_setup: |\n    ...\n  script: |-\n    bash tests\u002Ffunctional_tests\u002Fshell_test_utils\u002Frun_ci_test.sh ...\nproducts:\n  - test_case: [my_test]\n    products:\n      - environment: [dev, lts]\n        scope: [mr-github]\n        platforms: [dgx_h100]\n```\n\nKey runtime placeholders: `{assets_dir}`, `{artifacts_dir}`, `{test_case}`,\n`{environment}`, `{platforms}`, `{n_repeat}`.\n\n### Disabling a Test Without Deleting It\n\nTo temporarily disable a test case in a recipe YAML, suffix its `scope` value\nwith `-broken` — **do not delete the entry**:\n\n```yaml\n# before (test runs in CI)\nscope: [mr-github]\n\n# after (test is skipped; entry preserved for easy re-enable)\nscope: [mr-github-broken]\n```\n\n---\n\n## Running Unit Tests Locally\n\nAll unit tests initialize a `torch.distributed` group, so every invocation\nrequires GPU access and must go through `torch.distributed.run`:\n\n```bash\n# Full suite\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\n\n# Single file\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\u002Fmodels\u002Ftest_gpt_model.py\n\n# Single test\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\u002Fmodels\u002Ftest_gpt_model.py::TestGPTModel::test_constructor\n\n# Filter by name substring\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests -k optimizer\n```\n\n### Marker filters\n\n```bash\n# Exclude flaky tests during development\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests -m \"not flaky and not flaky_in_dev\"\n\n# Include experimental tests\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests --experimental\n```\n\n### CI parity\n\nUse `tests\u002Funit_tests\u002Frun_ci_test.sh` to reproduce a CI bucket failure exactly.\nFor ad-hoc runs, prefer the direct `torch.distributed.run` invocations above.\n\n### Gotchas\n\n- `pyproject.toml` sets `addopts = --durations=15 -s -rA` — stdout is not\n  captured (`-s`), so ranks interleave during multi-rank runs. Override with\n  `--capture=fd` when debugging a specific rank.\n- `tests\u002Funit_tests\u002Fconftest.py` looks for test data under `\u002Fopt\u002Fdata` and\n  attempts a download if missing. Supply it manually or skip data-dependent\n  tests when running outside the canonical container.\n\n---\n\n## Adding a Unit Test\n\n1. Create `tests\u002Funit_tests\u002F\u003Ccategory>\u002Ftest_\u003Cname>.py`.\n2. Use fixtures from `tests\u002Funit_tests\u002Fconftest.py`.\n3. Apply markers as needed:\n   - `@pytest.mark.internal` — skipped on `legacy` tag\n   - `@pytest.mark.flaky_in_dev` — skipped in `dev` environment (CI default; use this to disable a flaky test without blocking the standard pipeline)\n   - `@pytest.mark.flaky` — skipped in `lts` environment\n   - `@pytest.mark.experimental` — `latest` tag only\n4. Verify locally (see Running Unit Tests Locally above).\n5. If the test needs a dedicated CI bucket, add an entry to\n   `tests\u002Ftest_utils\u002Frecipes\u002Fh100\u002Funit-tests.yaml`.\n\n---\n\n## Adding a Functional \u002F Integration Test\n\n1. Create `tests\u002Ffunctional_tests\u002Ftest_cases\u002F\u003Cmodel>\u002F\u003Ctest_name>\u002F`.\n2. Write `model_config.yaml` with `MODEL_ARGS`, `ENV_VARS`, and `TEST_TYPE`.\n3. Add a YAML recipe under `tests\u002Ftest_utils\u002Frecipes\u002Fh100\u002F` (and `gb200\u002F` if\n   needed). Required fields: `scope`, `environment`, `platform`, `n_repeat`,\n   `time_limit`.\n4. Push the PR, add the label **\"Run functional tests\"** to trigger a full run.\n5. After a successful run, download golden values:\n\n   ```bash\n   python tests\u002Ftest_utils\u002Fpython_scripts\u002Fdownload_golden_values.py \\\n     --source github --pipeline-id \u003Crun-id>\n   ```\n\n6. Commit the downloaded golden values.\n\n---\n\n## Common Pitfalls\n\n| Problem | Cause | Fix |\n|---------|-------|-----|\n| Test passes locally but fails in CI | Different environment or data path | Check `DATA_PATH`, `DATA_CACHE_PATH`, and the `environment` tag (`dev` vs `lts`) |\n| Golden value mismatch after a code change | Numerical regression | Download new golden values via `download_golden_values.py` after a clean run |\n| `cicd-integration-tests-gb200` not triggered | GB200 jobs require maintainer status | Ask a maintainer to trigger, or add the `Run functional tests` label |\n",{"name":5,"license":15,"metadata":24,"description":7,"when_to_use":26},{"author":25},"Philip Petrakian \u003Cppetrakian@nvidia.com>","Adding or running a unit or functional test; understanding the test layout; writing a recipe YAML; downloading or updating golden values; reproducing a test failure locally; 'how do I add a test', 'run unit tests', 'pytest fails', 'test layout', 'golden values', 'recipe YAML', 'marker filter'.","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fnvidia-skills\u002Fmcore-testing",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill mcore-testing",{"tool":41,"command":42},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill mcore-testing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill mcore-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fmcore-testing\u002FSkill.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"metadata.json","REFERENCE","参考文档",402,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fmcore-testing\u002Fmetadata.json",[56,64,69,76,81,88],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":65,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]