[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBJCHVP8J2S7Q00ZP9QR45":3,"skill-same:01M7CBJCHVP8J2S7Q00ZP9QR45":50},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CBJCHVP8J2S7Q00ZP9QR45","sf-vlocity-build-deploy",null,"Salesforce Industries DataPack deployment automation using Vlocity Build. TRIGGER when: user deploys or validates OmniStudio\u002FVlocity DataPacks with vlocity commands (packDeploy\u002FpackRetry\u002FpackExport\u002FpackGetDiffs), sets up DataPack CI\u002FCD pipelines, or troubleshoots DataPack migration errors. DO NOT TRIGGER when: deploying Salesforce metadata with sf project deploy (use sf-deploy), authoring OmniStudio artifacts (use sf-industry-commoncore-*), or writing Apex\u002FLWC business logic (use sf-apex\u002Fsf-lwc).","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\u002Fjaganpro-sf-skills\u002Fsf-vlocity-build-deploy\u002Fskills\u002Fsf-vlocity-build-deploy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-vlocity-build-deploy\ndescription: >\n  Salesforce Industries DataPack deployment automation using Vlocity Build.\n  TRIGGER when: user deploys or validates OmniStudio\u002FVlocity DataPacks with\n  vlocity commands (packDeploy\u002FpackRetry\u002FpackExport\u002FpackGetDiffs), sets up\n  DataPack CI\u002FCD pipelines, or troubleshoots DataPack migration errors.\n  DO NOT TRIGGER when: deploying Salesforce metadata with sf project deploy\n  (use sf-deploy), authoring OmniStudio artifacts (use sf-industry-commoncore-*),\n  or writing Apex\u002FLWC business logic (use sf-apex\u002Fsf-lwc).\nlicense: MIT\nmetadata:\n  version: \"1.0.0\"\n  author: \"Shreyas Dhond (ShreyasD)\"\n---\n\n# sf-vlocity-build-deploy: Vlocity Build DataPack Deployment\n\nUse this skill when the user needs **Vlocity DataPack deployment orchestration**: export\u002Fdeploy workflow, manifest-driven deploys, failure triage, and CI\u002FCD sequencing for OmniStudio\u002FIndustries DataPacks.\n\n---\n\n## When This Skill Owns the Task\n\nUse `sf-vlocity-build-deploy` when work involves:\n- `vlocity packDeploy`, `packRetry`, `packContinue`, `packExport`, `packGetDiffs`, `validateLocalData`\n- DataPack job-file design (`projectPath`, `expansionPath`, `manifest`, `queries`)\n- org-to-org DataPack migration and retry loops\n- troubleshooting DataPack dependency, matching-key, and GlobalKey issues\n\nDelegate elsewhere when the user is:\n- deploying standard metadata with `sf project deploy` -> [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md)\n- building OmniScripts, FlexCards, IPs, or Data Mappers -> `sf-industry-commoncore-*`\n- designing Product2 EPC bundles -> [sf-industry-cme-epc-model](..\u002Fsf-industry-cme-epc-model\u002FSKILL.md)\n- writing Apex\u002FLWC code -> [sf-apex](..\u002Fsf-apex\u002FSKILL.md), [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md)\n\n---\n\n## Critical Operating Rules\n\n- Use **Vlocity Build (`vlocity`)** commands for DataPacks, not `sf project deploy`.\n- Prefer Salesforce CLI auth integration (`-sfdx.username \u003Calias>`) over username\u002Fpassword files when available.\n- Always run a **pre-deploy quality gate** before full deploy:\n  1) `validateLocalData`\n  2) optional `packGetDiffs`\n  3) then `packDeploy`\n- Use `packRetry` repeatedly when error counts are dropping; stop when retries no longer improve results.\n- Keep matching-key strategy and GlobalKey integrity consistent across source and target orgs.\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- source org and target org aliases\n- job file path and DataPack project path\n- deployment scope (full project, manifest subset, or specific `-key`)\n- whether this is export, deploy, retry, continue, or diff-only\n- namespace model (`%vlocity_namespace%`, `vlocity_cmt`, or core)\n- known constraints (new sandbox bootstrap, trigger behavior, matching key customizations)\n\nPreflight checks:\n\n```bash\nvlocity help\nsf org list\nsf org display --target-org \u003Calias> --json\ntest -f \u003Cjob-file>.yaml\n```\n\n---\n\n## Recommended Workflow\n\n### 1. Ensure tool readiness\n```bash\nnpm install --global vlocity\nvlocity help\n```\n\n### 2. Validate project data locally\n```bash\nvlocity -sfdx.username \u003Csource-alias> -job \u003Cjob-file>.yaml validateLocalData\n```\n\nUse `--fixLocalGlobalKeys` only when explicitly requested and after explaining impact.\n\n### 3. Export from source (when needed)\n```bash\nvlocity -sfdx.username \u003Csource-alias> -job \u003Cjob-file>.yaml packExport\nvlocity -sfdx.username \u003Csource-alias> -job \u003Cjob-file>.yaml packRetry\n```\n\n### 4. Deploy to target\n```bash\nvlocity -sfdx.username \u003Ctarget-alias> -job \u003Cjob-file>.yaml packDeploy\nvlocity -sfdx.username \u003Ctarget-alias> -job \u003Cjob-file>.yaml packRetry\n```\n\n### 5. Continue interrupted jobs\n```bash\nvlocity -sfdx.username \u003Ctarget-alias> -job \u003Cjob-file>.yaml packContinue\n```\n\n### 6. Verify post-deploy parity\n```bash\nvlocity -sfdx.username \u003Ctarget-alias> -job \u003Cjob-file>.yaml packGetDiffs\n```\n\nJob-file starter: [references\u002Fjob-file-template.md](references\u002Fjob-file-template.md)\n\n---\n\n## High-Signal Failure Patterns\n\n| Error \u002F symptom | Likely cause | Default fix direction |\n|---|---|---|\n| `No match found for ...` | missing dependency in target org | include missing DataPack key and redeploy |\n| `Duplicate Results found for ... GlobalKey` | duplicate records in target | clean duplicates and re-run deploy |\n| `Multiple Imported Records ... same Salesforce Record` | source duplicate matching-key records | remove duplicates in source and re-export |\n| `No Configuration Found` | outdated DataPack settings | run `packUpdateSettings` or enable `autoUpdateSettings` |\n| `Some records were not processed` | settings mismatch \u002F partial dependency state | refresh settings both orgs, then retry |\n| SASS \u002F template compile failures | missing referenced UI template assets | export\u002Fdeploy referenced template dependencies first |\n\nDetailed matrix: [references\u002Ftroubleshooting-matrix.md](references\u002Ftroubleshooting-matrix.md)\n\n---\n\n## CI\u002FCD Guidance\n\nDefault pipeline shape:\n1. authenticate orgs (`sf org login ...`)\n2. validate local DataPack integrity (`validateLocalData`)\n3. export changed scope (`packExport` or manifest-driven export)\n4. deploy (`packDeploy`)\n5. retry loop (`packRetry`) until stable\n6. compare (`packGetDiffs`) and publish deployment report\n\nFor incremental deploy optimization, use job-file options such as:\n- `gitCheck: true`\n- `gitCheckKey: \u003Cfolder>`\n- `manifest` for deterministic scope control\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| metadata deploy outside DataPacks | [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) | Metadata API workflows |\n| OmniStudio component authoring | `sf-industry-commoncore-*` | build artifacts before deploy |\n| EPC product and offer payload authoring | [sf-industry-cme-epc-model](..\u002Fsf-industry-cme-epc-model\u002FSKILL.md) | Product2\u002FDataPack model quality |\n| Apex trigger\u002Flog error diagnosis | [sf-debug](..\u002Fsf-debug\u002FSKILL.md), [sf-apex](..\u002Fsf-apex\u002FSKILL.md) | automation-side root-cause fixes |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fjob-file-template.md](references\u002Fjob-file-template.md)\n- [references\u002Ftroubleshooting-matrix.md](references\u002Ftroubleshooting-matrix.md)\n- [examples\u002Fbusiness-internet-plus-bundle\u002FTRANSCRIPT.md](examples\u002Fbusiness-internet-plus-bundle\u002FTRANSCRIPT.md)\n- [examples\u002Fbusiness-internet-plus-bundle-deploy\u002FTRANSCRIPT.md](examples\u002Fbusiness-internet-plus-bundle-deploy\u002FTRANSCRIPT.md)\n\n### External reference\n- [Vlocity Build GitHub](https:\u002F\u002Fgithub.com\u002Fvlocityinc\u002Fvlocity_build)\n\n---\n\n## Completion Format\n\n```text\nDataPack goal: \u003Cexport \u002F deploy \u002F retry \u002F diff \u002F ci-cd>\nSource org: \u003Calias or N\u002FA>\nTarget org: \u003Calias or N\u002FA>\nScope: \u003Cjob file + manifest\u002Fkey\u002Ffull>\nResult: \u003Cpassed \u002F failed \u002F partial>\nKey findings: \u003Cerrors, dependencies, retries, diffs>\nNext step: \u003Csafe follow-up action>\n```\n","# sf-vlocity-build-deploy: Vlocity Build DataPack Deployment\n\nUse this skill when the user needs **Vlocity DataPack deployment orchestration**: export\u002Fdeploy workflow, manifest-driven deploys, failure triage, and CI\u002FCD sequencing for OmniStudio\u002FIndustries DataPacks.\n\n---\n\n## When This Skill Owns the Task\n\nUse `sf-vlocity-build-deploy` when work involves:\n- `vlocity packDeploy`, `packRetry`, `packContinue`, `packExport`, `packGetDiffs`, `validateLocalData`\n- DataPack job-file design (`projectPath`, `expansionPath`, `manifest`, `queries`)\n- org-to-org DataPack migration and retry loops\n- troubleshooting DataPack dependency, matching-key, and GlobalKey issues\n\nDelegate elsewhere when the user is:\n- deploying standard metadata with `sf project deploy` -> [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md)\n- building OmniScripts, FlexCards, IPs, or Data Mappers -> `sf-industry-commoncore-*`\n- designing Product2 EPC bundles -> [sf-industry-cme-epc-model](..\u002Fsf-industry-cme-epc-model\u002FSKILL.md)\n- writing Apex\u002FLWC code -> [sf-apex](..\u002Fsf-apex\u002FSKILL.md), [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md)\n\n---\n\n## Critical Operating Rules\n\n- Use **Vlocity Build (`vlocity`)** commands for DataPacks, not `sf project deploy`.\n- Prefer Salesforce CLI auth integration (`-sfdx.username \u003Calias>`) over username\u002Fpassword files when available.\n- Always run a **pre-deploy quality gate** before full deploy:\n  1) `validateLocalData`\n  2) optional `packGetDiffs`\n  3) then `packDeploy`\n- Use `packRetry` repeatedly when error counts are dropping; stop when retries no longer improve results.\n- Keep matching-key strategy and GlobalKey integrity consistent across source and target orgs.\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- source org and target org aliases\n- job file path and DataPack project path\n- deployment scope (full project, manifest subset, or specific `-key`)\n- whether this is export, deploy, retry, continue, or diff-only\n- namespace model (`%vlocity_namespace%`, `vlocity_cmt`, or core)\n- known constraints (new sandbox bootstrap, trigger behavior, matching key customizations)\n\nPreflight checks:\n\n```bash\nvlocity help\nsf org list\nsf org display --target-org \u003Calias> --json\ntest -f \u003Cjob-file>.yaml\n```\n\n---\n\n## Recommended Workflow\n\n### 1. Ensure tool readiness\n```bash\nnpm install --global vlocity\nvlocity help\n```\n\n### 2. Validate project data locally\n```bash\nvlocity -sfdx.username \u003Csource-alias> -job \u003Cjob-file>.yaml validateLocalData\n```\n\nUse `--fixLocalGlobalKeys` only when explicitly requested and after explaining impact.\n\n### 3. Export from source (when needed)\n```bash\nvlocity -sfdx.username \u003Csource-alias> -job \u003Cjob-file>.yaml packExport\nvlocity -sfdx.username \u003Csource-alias> -job \u003Cjob-file>.yaml packRetry\n```\n\n### 4. Deploy to target\n```bash\nvlocity -sfdx.username \u003Ctarget-alias> -job \u003Cjob-file>.yaml packDeploy\nvlocity -sfdx.username \u003Ctarget-alias> -job \u003Cjob-file>.yaml packRetry\n```\n\n### 5. Continue interrupted jobs\n```bash\nvlocity -sfdx.username \u003Ctarget-alias> -job \u003Cjob-file>.yaml packContinue\n```\n\n### 6. Verify post-deploy parity\n```bash\nvlocity -sfdx.username \u003Ctarget-alias> -job \u003Cjob-file>.yaml packGetDiffs\n```\n\nJob-file starter: [references\u002Fjob-file-template.md](references\u002Fjob-file-template.md)\n\n---\n\n## High-Signal Failure Patterns\n\n| Error \u002F symptom | Likely cause | Default fix direction |\n|---|---|---|\n| `No match found for ...` | missing dependency in target org | include missing DataPack key and redeploy |\n| `Duplicate Results found for ... GlobalKey` | duplicate records in target | clean duplicates and re-run deploy |\n| `Multiple Imported Records ... same Salesforce Record` | source duplicate matching-key records | remove duplicates in source and re-export |\n| `No Configuration Found` | outdated DataPack settings | run `packUpdateSettings` or enable `autoUpdateSettings` |\n| `Some records were not processed` | settings mismatch \u002F partial dependency state | refresh settings both orgs, then retry |\n| SASS \u002F template compile failures | missing referenced UI template assets | export\u002Fdeploy referenced template dependencies first |\n\nDetailed matrix: [references\u002Ftroubleshooting-matrix.md](references\u002Ftroubleshooting-matrix.md)\n\n---\n\n## CI\u002FCD Guidance\n\nDefault pipeline shape:\n1. authenticate orgs (`sf org login ...`)\n2. validate local DataPack integrity (`validateLocalData`)\n3. export changed scope (`packExport` or manifest-driven export)\n4. deploy (`packDeploy`)\n5. retry loop (`packRetry`) until stable\n6. compare (`packGetDiffs`) and publish deployment report\n\nFor incremental deploy optimization, use job-file options such as:\n- `gitCheck: true`\n- `gitCheckKey: \u003Cfolder>`\n- `manifest` for deterministic scope control\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| metadata deploy outside DataPacks | [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) | Metadata API workflows |\n| OmniStudio component authoring | `sf-industry-commoncore-*` | build artifacts before deploy |\n| EPC product and offer payload authoring | [sf-industry-cme-epc-model](..\u002Fsf-industry-cme-epc-model\u002FSKILL.md) | Product2\u002FDataPack model quality |\n| Apex trigger\u002Flog error diagnosis | [sf-debug](..\u002Fsf-debug\u002FSKILL.md), [sf-apex](..\u002Fsf-apex\u002FSKILL.md) | automation-side root-cause fixes |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fjob-file-template.md](references\u002Fjob-file-template.md)\n- [references\u002Ftroubleshooting-matrix.md](references\u002Ftroubleshooting-matrix.md)\n- [examples\u002Fbusiness-internet-plus-bundle\u002FTRANSCRIPT.md](examples\u002Fbusiness-internet-plus-bundle\u002FTRANSCRIPT.md)\n- [examples\u002Fbusiness-internet-plus-bundle-deploy\u002FTRANSCRIPT.md](examples\u002Fbusiness-internet-plus-bundle-deploy\u002FTRANSCRIPT.md)\n\n### External reference\n- [Vlocity Build GitHub](https:\u002F\u002Fgithub.com\u002Fvlocityinc\u002Fvlocity_build)\n\n---\n\n## Completion Format\n\n```text\nDataPack goal: \u003Cexport \u002F deploy \u002F retry \u002F diff \u002F ci-cd>\nSource org: \u003Calias or N\u002FA>\nTarget org: \u003Calias or N\u002FA>\nScope: \u003Cjob file + manifest\u002Fkey\u002Ffull>\nResult: \u003Cpassed \u002F failed \u002F partial>\nKey findings: \u003Cerrors, dependencies, retries, diffs>\nNext step: \u003Csafe follow-up action>\n```\n",{"name":5,"license":15,"metadata":24,"description":27},{"author":25,"version":26},"Shreyas Dhond (ShreyasD)","1.0.0","Salesforce Industries DataPack deployment automation using Vlocity Build. TRIGGER when: user deploys or validates OmniStudio\u002FVlocity DataPacks with vlocity commands (packDeploy\u002FpackRetry\u002FpackExport\u002FpackGetDiffs), sets up DataPack CI\u002FCD pipelines, or troubleshoots DataPack migration errors. DO NOT TRIGGER when: deploying Salesforce metadata with sf project deploy (use sf-deploy), authoring OmniStudio artifacts (use sf-industry-commoncore-*), or writing Apex\u002FLWC business logic (use sf-apex\u002Fsf-lwc).\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-vlocity-build-deploy\u002Fskills\u002Fsf-vlocity-build-deploy",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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-vlocity-build-deploy",{"tool":42,"command":43},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-vlocity-build-deploy",{"tool":45,"command":46},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-vlocity-build-deploy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-vlocity-build-deploy\u002Fskills\u002Fsf-vlocity-build-deploy\u002FSKILL.md",true,[],[51,58,63,70,75,82],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"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":59,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":65,"nameZh":6,"description":66,"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},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\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},"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":83,"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":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]