[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CB9N7MYYWETBS4ZBCSEVHT":3,"skill-same:01M7CB9N7MYYWETBS4ZBCSEVHT":56},{"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},"01M7CB9N7MYYWETBS4ZBCSEVHT","sf-deploy",null,"Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates\u002Fmanages scratch orgs or sandboxes, sets up CI\u002FCD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex\u002FLWC code (use sf-apex\u002Fsf-lwc), creating metadata XML (use sf-metadata), or querying org data (use sf-data).","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-deploy\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-deploy\ndescription: >\n  Salesforce DevOps automation using sf CLI v2.\n  TRIGGER when: user deploys metadata, creates\u002Fmanages scratch orgs or sandboxes,\n  sets up CI\u002FCD pipelines, or troubleshoots deployment errors with sf project deploy.\n  DO NOT TRIGGER when: writing Apex\u002FLWC code (use sf-apex\u002Fsf-lwc), creating metadata\n  XML (use sf-metadata), or querying org data (use sf-data).\nlicense: MIT\nmetadata:\n  version: \"2.3.0\"\n  author: \"Jag Valaiyapathy\"\n---\n\n# sf-deploy: Comprehensive Salesforce DevOps Automation\n\nUse this skill when the user needs **deployment orchestration**: dry-run validation, targeted or manifest-based deploys, CI\u002FCD workflow advice, scratch-org management, failure triage, or safe rollout sequencing for Salesforce metadata.\n\n## When This Skill Owns the Task\n\nUse `sf-deploy` when the work involves:\n- `sf project deploy start`, `quick`, `report`, or retrieval workflows\n- release sequencing across objects, permission sets, Apex, and Flows\n- CI\u002FCD gates, test-level selection, or deployment reports\n- troubleshooting deployment failures and dependency ordering\n\nDelegate elsewhere when the user is:\n- authoring Apex or LWC code → [sf-apex](..\u002Fsf-apex\u002FSKILL.md), [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md)\n- creating metadata definitions → [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md)\n- building Flows → [sf-flow](..\u002Fsf-flow\u002FSKILL.md)\n- doing org data operations → [sf-data](..\u002Fsf-data\u002FSKILL.md)\n- authoring Agent Script logic → [sf-ai-agentscript](..\u002Fsf-ai-agentscript\u002FSKILL.md)\n\n---\n\n## Critical Operating Rules\n\n- Use **`sf` CLI v2 only**.\n- On non-source-tracking orgs, deploy\u002Fretrieve commands require an explicit scope such as `--source-dir`, `--metadata`, or `--manifest`.\n- Prefer **`--dry-run` first** before real deploys.\n- For Flows, deploy safely and activate only after validation.\n- Keep test-data creation guidance delegated to **`sf-data`** after metadata is validated or deployed.\n\n### Default deployment order\n| Phase | Metadata |\n|---|---|\n| 1 | Custom objects \u002F fields |\n| 2 | Permission sets |\n| 3 | Apex |\n| 4 | Flows as Draft |\n| 5 | Flow activation \u002F post-verify |\n\nThis ordering prevents many dependency and FLS failures.\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias and environment type\n- deployment scope: source-dir, metadata list, or manifest\n- whether this is validate-only, deploy, quick deploy, retrieve, or CI\u002FCD guidance\n- required test level and rollback expectations\n- whether special metadata types are involved (Flow, permission sets, agents, packages)\n\nPreflight checks:\n```bash\nsf --version\nsf org list\nsf org display --target-org \u003Calias> --json\ntest -f sfdx-project.json\n```\n\n---\n\n## Recommended Workflow\n\n### 1. Preflight\nConfirm auth, repo shape, package directories, and target scope.\n\n### 2. Validate first\n```bash\nsf project deploy start --dry-run --source-dir force-app --target-org \u003Calias> --wait 30 --json\n```\nUse manifest- or metadata-scoped validation when the change set is targeted.\n\n### 3. If validation succeeds, offer the next safe workflow\nAfter a successful validation, guide the user to the correct next action:\n1. deploy now\n2. assign permission sets\n3. create test data via [sf-data](..\u002Fsf-data\u002FSKILL.md)\n4. run tests \u002F smoke checks\n5. orchestrate multiple post-deploy steps in order\n\n### 4. Deploy the smallest correct scope\n```bash\n# source-dir deploy\nsf project deploy start --source-dir force-app --target-org \u003Calias> --wait 30 --json\n\n# manifest deploy\nsf project deploy start --manifest manifest\u002Fpackage.xml --target-org \u003Calias> --test-level RunLocalTests --wait 30 --json\n\n# manifest deploy with Spring '26 relevant-test selection\nsf project deploy start --manifest manifest\u002Fpackage.xml --target-org \u003Calias> --test-level RunRelevantTests --wait 30 --json\n\n# quick deploy after successful validation\nsf project deploy quick --job-id \u003Cvalidation-job-id> --target-org \u003Calias> --json\n```\n\n### 5. Verify\n```bash\nsf project deploy report --job-id \u003Cjob-id> --target-org \u003Calias> --json\n```\nThen verify tests, Flow state, permission assignments, and smoke-test behavior.\n\n### 6. Report clearly\nSummarize what deployed, what failed, what was skipped, and what the next safe action is.\n\nOutput template: [references\u002Fdeployment-report-template.md](references\u002Fdeployment-report-template.md)\n\n---\n\n## High-Signal Failure Patterns\n\n| Error \u002F symptom | Likely cause | Default fix direction |\n|---|---|---|\n| `FIELD_CUSTOM_VALIDATION_EXCEPTION` | validation rule or bad test data | adjust data or rule timing |\n| `INVALID_CROSS_REFERENCE_KEY` | missing dependency | include referenced metadata first |\n| `CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY` | trigger \u002F Flow \u002F validation side effect | inspect automation stack and failing logic |\n| tests fail during deploy | broken code or fragile tests | run targeted tests, fix root cause, revalidate |\n| field\u002Fobject not found in permset | wrong order | deploy objects\u002Ffields before permission sets |\n| Flow invalid \u002F version conflict | dependency or activation problem | deploy as Draft, verify, then activate |\n\nFull workflows: [references\u002Forchestration.md](references\u002Forchestration.md), [references\u002Ftrigger-deployment-safety.md](references\u002Ftrigger-deployment-safety.md)\n\n---\n\n## CI\u002FCD Guidance\n\nDefault pipeline shape:\n1. authenticate\n2. validate repo \u002F org state\n3. static analysis\n4. dry-run deploy\n5. tests + coverage gates\n6. deploy\n7. verify + notify\n\n- When org policy and release risk allow it, consider `--test-level RunRelevantTests` for Apex-heavy deployments.\n- Pair this with modern Apex test annotations such as `@IsTest(testFor=...)` and `@IsTest(isCritical=true)` as documented in `sf-apex`.\n\nStatic analysis now uses **Code Analyzer v5** (`sf code-analyzer`), not retired `sf scanner`.\n\nDeep reference: [references\u002Fdeployment-workflows.md](references\u002Fdeployment-workflows.md)\n\n---\n\n## Agentforce Deployment Note\n\nUse this skill to orchestrate **deployment\u002Fpublish sequencing** around agents, but use the agent-specific skills for authoring decisions:\n- [sf-ai-agentscript](..\u002Fsf-ai-agentscript\u002FSKILL.md) for `.agent` authoring and validation\n- [sf-ai-agentforce](..\u002Fsf-ai-agentforce\u002FSKILL.md) for Agent Builder \u002F Prompt Builder \u002F metadata config\n\nFor full agent DevOps details, including `Agent:` pseudo metadata, publish\u002Factivate, and sync-between-orgs, see:\n- [references\u002Fagent-deployment-guide.md](references\u002Fagent-deployment-guide.md)\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| custom object \u002F field creation | [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) | define metadata before deploy |\n| Apex compile \u002F review \u002F fixes | [sf-apex](..\u002Fsf-apex\u002FSKILL.md) | code authoring and repair |\n| Flow creation \u002F repair | [sf-flow](..\u002Fsf-flow\u002FSKILL.md) | Flow authoring and activation guidance |\n| test data or seed records | [sf-data](..\u002Fsf-data\u002FSKILL.md) | describe-first data setup and cleanup |\n| Agent Script build\u002Fpublish readiness | [sf-ai-agentscript](..\u002Fsf-ai-agentscript\u002FSKILL.md) | agent-specific correctness |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Forchestration.md](references\u002Forchestration.md)\n- [references\u002Fdeployment-workflows.md](references\u002Fdeployment-workflows.md)\n- [references\u002Fdeployment-report-template.md](references\u002Fdeployment-report-template.md)\n\n### Specialized deployment safety\n- [references\u002Ftrigger-deployment-safety.md](references\u002Ftrigger-deployment-safety.md)\n- [references\u002Fagent-deployment-guide.md](references\u002Fagent-deployment-guide.md)\n- [references\u002Fdeploy.sh](references\u002Fdeploy.sh)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 90+ | strong deployment plan and execution guidance |\n| 75–89 | good deploy guidance with minor review items |\n| 60–74 | partial coverage of deployment risk |\n| \u003C 60 | insufficient confidence; tighten plan before rollout |\n\n---\n\n## Completion Format\n\n```text\nDeployment goal: \u003Cvalidate \u002F deploy \u002F retrieve \u002F pipeline>\nTarget org: \u003Calias>\nScope: \u003Csource-dir \u002F metadata \u002F manifest>\nResult: \u003Cpassed \u002F failed \u002F partial>\nKey findings: \u003Cerrors, ordering, tests, skipped items>\nNext step: \u003Csafe follow-up action>\n```\n","# sf-deploy: Comprehensive Salesforce DevOps Automation\n\nUse this skill when the user needs **deployment orchestration**: dry-run validation, targeted or manifest-based deploys, CI\u002FCD workflow advice, scratch-org management, failure triage, or safe rollout sequencing for Salesforce metadata.\n\n## When This Skill Owns the Task\n\nUse `sf-deploy` when the work involves:\n- `sf project deploy start`, `quick`, `report`, or retrieval workflows\n- release sequencing across objects, permission sets, Apex, and Flows\n- CI\u002FCD gates, test-level selection, or deployment reports\n- troubleshooting deployment failures and dependency ordering\n\nDelegate elsewhere when the user is:\n- authoring Apex or LWC code → [sf-apex](..\u002Fsf-apex\u002FSKILL.md), [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md)\n- creating metadata definitions → [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md)\n- building Flows → [sf-flow](..\u002Fsf-flow\u002FSKILL.md)\n- doing org data operations → [sf-data](..\u002Fsf-data\u002FSKILL.md)\n- authoring Agent Script logic → [sf-ai-agentscript](..\u002Fsf-ai-agentscript\u002FSKILL.md)\n\n---\n\n## Critical Operating Rules\n\n- Use **`sf` CLI v2 only**.\n- On non-source-tracking orgs, deploy\u002Fretrieve commands require an explicit scope such as `--source-dir`, `--metadata`, or `--manifest`.\n- Prefer **`--dry-run` first** before real deploys.\n- For Flows, deploy safely and activate only after validation.\n- Keep test-data creation guidance delegated to **`sf-data`** after metadata is validated or deployed.\n\n### Default deployment order\n| Phase | Metadata |\n|---|---|\n| 1 | Custom objects \u002F fields |\n| 2 | Permission sets |\n| 3 | Apex |\n| 4 | Flows as Draft |\n| 5 | Flow activation \u002F post-verify |\n\nThis ordering prevents many dependency and FLS failures.\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias and environment type\n- deployment scope: source-dir, metadata list, or manifest\n- whether this is validate-only, deploy, quick deploy, retrieve, or CI\u002FCD guidance\n- required test level and rollback expectations\n- whether special metadata types are involved (Flow, permission sets, agents, packages)\n\nPreflight checks:\n```bash\nsf --version\nsf org list\nsf org display --target-org \u003Calias> --json\ntest -f sfdx-project.json\n```\n\n---\n\n## Recommended Workflow\n\n### 1. Preflight\nConfirm auth, repo shape, package directories, and target scope.\n\n### 2. Validate first\n```bash\nsf project deploy start --dry-run --source-dir force-app --target-org \u003Calias> --wait 30 --json\n```\nUse manifest- or metadata-scoped validation when the change set is targeted.\n\n### 3. If validation succeeds, offer the next safe workflow\nAfter a successful validation, guide the user to the correct next action:\n1. deploy now\n2. assign permission sets\n3. create test data via [sf-data](..\u002Fsf-data\u002FSKILL.md)\n4. run tests \u002F smoke checks\n5. orchestrate multiple post-deploy steps in order\n\n### 4. Deploy the smallest correct scope\n```bash\n# source-dir deploy\nsf project deploy start --source-dir force-app --target-org \u003Calias> --wait 30 --json\n\n# manifest deploy\nsf project deploy start --manifest manifest\u002Fpackage.xml --target-org \u003Calias> --test-level RunLocalTests --wait 30 --json\n\n# manifest deploy with Spring '26 relevant-test selection\nsf project deploy start --manifest manifest\u002Fpackage.xml --target-org \u003Calias> --test-level RunRelevantTests --wait 30 --json\n\n# quick deploy after successful validation\nsf project deploy quick --job-id \u003Cvalidation-job-id> --target-org \u003Calias> --json\n```\n\n### 5. Verify\n```bash\nsf project deploy report --job-id \u003Cjob-id> --target-org \u003Calias> --json\n```\nThen verify tests, Flow state, permission assignments, and smoke-test behavior.\n\n### 6. Report clearly\nSummarize what deployed, what failed, what was skipped, and what the next safe action is.\n\nOutput template: [references\u002Fdeployment-report-template.md](references\u002Fdeployment-report-template.md)\n\n---\n\n## High-Signal Failure Patterns\n\n| Error \u002F symptom | Likely cause | Default fix direction |\n|---|---|---|\n| `FIELD_CUSTOM_VALIDATION_EXCEPTION` | validation rule or bad test data | adjust data or rule timing |\n| `INVALID_CROSS_REFERENCE_KEY` | missing dependency | include referenced metadata first |\n| `CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY` | trigger \u002F Flow \u002F validation side effect | inspect automation stack and failing logic |\n| tests fail during deploy | broken code or fragile tests | run targeted tests, fix root cause, revalidate |\n| field\u002Fobject not found in permset | wrong order | deploy objects\u002Ffields before permission sets |\n| Flow invalid \u002F version conflict | dependency or activation problem | deploy as Draft, verify, then activate |\n\nFull workflows: [references\u002Forchestration.md](references\u002Forchestration.md), [references\u002Ftrigger-deployment-safety.md](references\u002Ftrigger-deployment-safety.md)\n\n---\n\n## CI\u002FCD Guidance\n\nDefault pipeline shape:\n1. authenticate\n2. validate repo \u002F org state\n3. static analysis\n4. dry-run deploy\n5. tests + coverage gates\n6. deploy\n7. verify + notify\n\n- When org policy and release risk allow it, consider `--test-level RunRelevantTests` for Apex-heavy deployments.\n- Pair this with modern Apex test annotations such as `@IsTest(testFor=...)` and `@IsTest(isCritical=true)` as documented in `sf-apex`.\n\nStatic analysis now uses **Code Analyzer v5** (`sf code-analyzer`), not retired `sf scanner`.\n\nDeep reference: [references\u002Fdeployment-workflows.md](references\u002Fdeployment-workflows.md)\n\n---\n\n## Agentforce Deployment Note\n\nUse this skill to orchestrate **deployment\u002Fpublish sequencing** around agents, but use the agent-specific skills for authoring decisions:\n- [sf-ai-agentscript](..\u002Fsf-ai-agentscript\u002FSKILL.md) for `.agent` authoring and validation\n- [sf-ai-agentforce](..\u002Fsf-ai-agentforce\u002FSKILL.md) for Agent Builder \u002F Prompt Builder \u002F metadata config\n\nFor full agent DevOps details, including `Agent:` pseudo metadata, publish\u002Factivate, and sync-between-orgs, see:\n- [references\u002Fagent-deployment-guide.md](references\u002Fagent-deployment-guide.md)\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| custom object \u002F field creation | [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) | define metadata before deploy |\n| Apex compile \u002F review \u002F fixes | [sf-apex](..\u002Fsf-apex\u002FSKILL.md) | code authoring and repair |\n| Flow creation \u002F repair | [sf-flow](..\u002Fsf-flow\u002FSKILL.md) | Flow authoring and activation guidance |\n| test data or seed records | [sf-data](..\u002Fsf-data\u002FSKILL.md) | describe-first data setup and cleanup |\n| Agent Script build\u002Fpublish readiness | [sf-ai-agentscript](..\u002Fsf-ai-agentscript\u002FSKILL.md) | agent-specific correctness |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Forchestration.md](references\u002Forchestration.md)\n- [references\u002Fdeployment-workflows.md](references\u002Fdeployment-workflows.md)\n- [references\u002Fdeployment-report-template.md](references\u002Fdeployment-report-template.md)\n\n### Specialized deployment safety\n- [references\u002Ftrigger-deployment-safety.md](references\u002Ftrigger-deployment-safety.md)\n- [references\u002Fagent-deployment-guide.md](references\u002Fagent-deployment-guide.md)\n- [references\u002Fdeploy.sh](references\u002Fdeploy.sh)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 90+ | strong deployment plan and execution guidance |\n| 75–89 | good deploy guidance with minor review items |\n| 60–74 | partial coverage of deployment risk |\n| \u003C 60 | insufficient confidence; tighten plan before rollout |\n\n---\n\n## Completion Format\n\n```text\nDeployment goal: \u003Cvalidate \u002F deploy \u002F retrieve \u002F pipeline>\nTarget org: \u003Calias>\nScope: \u003Csource-dir \u002F metadata \u002F manifest>\nResult: \u003Cpassed \u002F failed \u002F partial>\nKey findings: \u003Cerrors, ordering, tests, skipped items>\nNext step: \u003Csafe follow-up action>\n```\n",{"name":5,"license":15,"metadata":24,"description":27},{"author":25,"version":26},"Jag Valaiyapathy","2.3.0","Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates\u002Fmanages scratch orgs or sandboxes, sets up CI\u002FCD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex\u002FLWC code (use sf-apex\u002Fsf-lwc), creating metadata XML (use sf-metadata), or querying org data (use sf-data).\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-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-deploy",{"tool":42,"command":43},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-deploy",{"tool":45,"command":46},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-deploy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-deploy\u002FSkill.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"metadata.json","REFERENCE","参考文档",411,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-deploy\u002Fmetadata.json",[57,64,69,76,81,88],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"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.","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":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"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":15,"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":15,"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":15,"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":15,"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",[],[]]