[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CB52AMH31E6K3P1446WD31":3,"skill-same:01M7CB52AMH31E6K3P1446WD31":51},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7CB52AMH31E6K3P1446WD31","sf-apex",null,"Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch\u002Fqueueable\u002Fschedulable jobs, or touches .cls\u002F.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.","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-apex\u002Fskills\u002Fsf-apex\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-apex\ndescription: >\n  Generates and reviews Salesforce Apex code with 150-point scoring.\n  TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes,\n  batch\u002Fqueueable\u002Fschedulable jobs, or touches .cls\u002F.trigger files.\n  DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow),\n  SOQL-only queries (use sf-soql), or non-Salesforce code.\nlicense: MIT\nmetadata:\n  version: \"1.1.0\"\n  author: \"Jag Valaiyapathy\"\n  scoring: \"150 points across 8 categories\"\n---\n\n# sf-apex: Salesforce Apex Code Generation and Review\n\nUse this skill when the user needs **production Apex**: new classes, triggers, selectors, services, async jobs, invocable methods, test classes, or evidence-based review of existing `.cls` \u002F `.trigger` code.\n\n## When This Skill Owns the Task\n\nUse `sf-apex` when the work involves:\n- Apex class generation or refactoring\n- trigger design and trigger-framework decisions\n- `@InvocableMethod`, Queueable, Batch, Schedulable, or test-class work\n- review of bulkification, sharing, security, testing, or maintainability\n\nDelegate elsewhere when the user is:\n- editing LWC JavaScript \u002F HTML \u002F CSS → [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md)\n- building Flow XML or Flow orchestration → [sf-flow](..\u002Fsf-flow\u002FSKILL.md)\n- writing SOQL only → [sf-soql](..\u002Fsf-soql\u002FSKILL.md)\n- deploying or validating metadata to orgs → [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- class type: trigger, service, selector, batch, queueable, schedulable, invocable, test\n- target object(s) and business goal\n- whether code is net-new, refactor, or fix\n- org \u002F API constraints if known\n- expected test coverage or deployment target\n\nBefore authoring, inspect the project shape:\n- existing classes \u002F triggers\n- current trigger framework or handler pattern\n- related tests, flows, and selectors\n- whether TAF is already in use\n\n---\n\n## Recommended Workflow\n\n### 1. Discover local architecture\nCheck for:\n- existing trigger handlers \u002F frameworks\n- service-selector-domain conventions\n- related tests and data factories\n- invocable or async patterns already used in the repo\n\n### 2. Choose the smallest correct pattern\n| Need | Preferred pattern |\n|---|---|\n| simple reusable logic | service class |\n| query-heavy data access | selector |\n| single object trigger behavior | one trigger + handler \u002F TAF action |\n| Flow needs complex logic | `@InvocableMethod` |\n| background processing | Queueable by default |\n| very large datasets | Batch Apex or `Database.Cursor` patterns |\n| repeatable verification | dedicated test class + test data factory |\n\n### 3. Author with guardrails\nGenerate code that is:\n- bulk-safe\n- sharing-aware\n- CRUD\u002FFLS-safe where applicable\n- testable in isolation\n- consistent with project naming and layering\n\n### 4. Validate and score\nEvaluate against the 150-point rubric before handoff.\n\n### 5. Hand off deploy\u002Ftest next steps\nWhen org validation is needed, hand off to:\n- [sf-testing](..\u002Fsf-testing\u002FSKILL.md) for test execution loops\n- [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) for deploy \u002F dry-run \u002F verification\n\n---\n\n## Generation Guardrails\n\nNever generate these without explicitly stopping and explaining the problem:\n\n| Anti-pattern | Why it blocks |\n|---|---|\n| SOQL in loops | governor-limit failure |\n| DML in loops | governor-limit failure |\n| missing sharing model | security \u002F data exposure risk |\n| hardcoded IDs | deployment and portability failure |\n| empty `catch` blocks | silent failure \u002F poor observability |\n| string-built SOQL with user input | injection risk |\n| tests without assertions | false-positive test suite |\n\nDefault fix direction:\n- query once, operate on collections\n- use `with sharing` unless justified otherwise\n- use bind variables and `WITH USER_MODE` where appropriate\n- create assertions for positive, negative, and bulk cases\n\nSee [references\u002Fanti-patterns.md](references\u002Fanti-patterns.md) and [references\u002Fsecurity-guide.md](references\u002Fsecurity-guide.md).\n\n---\n\n## High-Signal Build Rules\n\n### Trigger architecture\n- Prefer **one trigger per object**.\n- If TAF is already installed and used, extend it instead of inventing a second trigger pattern.\n- Triggers should delegate logic; avoid heavy business logic directly in trigger bodies.\n\n### Async choice\n| Scenario | Default |\n|---|---|\n| standard async work | Queueable |\n| very large record processing | Batch Apex |\n| recurring schedule | Scheduled Flow or Schedulable |\n| post-job cleanup | Finalizer |\n| long-running Lightning callouts | `Continuation` |\n\n### Testing minimums\nUse the **PNB** pattern for every feature:\n- **Positive** path\n- **Negative** \u002F error path\n- **Bulk** path (251+ records where relevant)\n\n### Modern Apex expectations\nPrefer current idioms when available:\n- safe navigation: `obj?.Field__c`\n- null coalescing: `value ?? fallback`\n- `Assert.*` over legacy assertion style\n- `WITH USER_MODE` and explicit security handling where relevant\n\n---\n\n## Output Format\n\nWhen finishing, report in this order:\n1. **What was created or reviewed**\n2. **Files changed**\n3. **Key design decisions**\n4. **Risk \u002F guardrail notes**\n5. **Test guidance**\n6. **Deployment guidance**\n\nSuggested shape:\n\n```text\nApex work: \u003Csummary>\nFiles: \u003Cpaths>\nDesign: \u003Cpattern \u002F framework choices>\nRisks: \u003Csecurity, bulkification, async, dependency notes>\nTests: \u003Cwhat to run \u002F add>\nDeploy: \u003Cdry-run or next step>\n```\n\n---\n\n## LSP Validation Note\n\nThis skill supports an LSP-assisted authoring loop for `.cls` and `.trigger` files:\n- syntax issues can be detected immediately after write\u002Fedit\n- the skill can auto-fix common syntax errors in a short loop\n- semantic quality still depends on the 150-point review rubric\n\nFull guide: [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md#lsp-based-validation-auto-fix-loop)\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| describe objects \u002F fields first | [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) | avoid coding against wrong schema |\n| seed bulk or edge-case data | [sf-data](..\u002Fsf-data\u002FSKILL.md) | create realistic test datasets |\n| run Apex tests \u002F fix failing tests | [sf-testing](..\u002Fsf-testing\u002FSKILL.md) | execute and iterate on failures |\n| deploy to org | [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) | validation and deployment orchestration |\n| build Flow that calls Apex | [sf-flow](..\u002Fsf-flow\u002FSKILL.md) | declarative orchestration |\n| build LWC that calls Apex | [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md) | UI\u002Fcontroller integration |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fpatterns-deep-dive.md](references\u002Fpatterns-deep-dive.md)\n- [references\u002Fsecurity-guide.md](references\u002Fsecurity-guide.md)\n- [references\u002Fbulkification-guide.md](references\u002Fbulkification-guide.md)\n- [references\u002Ftesting-patterns.md](references\u002Ftesting-patterns.md)\n\n### High-signal checklists\n- [references\u002Fcode-review-checklist.md](references\u002Fcode-review-checklist.md)\n- [references\u002Fanti-patterns.md](references\u002Fanti-patterns.md)\n- [references\u002Fnaming-conventions.md](references\u002Fnaming-conventions.md)\n\n### Specialized patterns\n- [references\u002Ftrigger-actions-framework.md](references\u002Ftrigger-actions-framework.md)\n- [references\u002Fautomation-density-guide.md](references\u002Fautomation-density-guide.md)\n- [references\u002Fflow-integration.md](references\u002Fflow-integration.md)\n- [references\u002Ftriangle-pattern.md](references\u002Ftriangle-pattern.md)\n- [references\u002Fdesign-patterns.md](references\u002Fdesign-patterns.md)\n- [references\u002Fsolid-principles.md](references\u002Fsolid-principles.md)\n\n### Troubleshooting \u002F validation\n- [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md)\n- [references\u002Fllm-anti-patterns.md](references\u002Fllm-anti-patterns.md)\n- [references\u002Ftesting-guide.md](references\u002Ftesting-guide.md)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 120+ | strong production-ready Apex |\n| 90–119 | good implementation, review before deploy |\n| 67–89 | acceptable but needs improvement |\n| \u003C 67 | block deployment |\n","# sf-apex: Salesforce Apex Code Generation and Review\n\nUse this skill when the user needs **production Apex**: new classes, triggers, selectors, services, async jobs, invocable methods, test classes, or evidence-based review of existing `.cls` \u002F `.trigger` code.\n\n## When This Skill Owns the Task\n\nUse `sf-apex` when the work involves:\n- Apex class generation or refactoring\n- trigger design and trigger-framework decisions\n- `@InvocableMethod`, Queueable, Batch, Schedulable, or test-class work\n- review of bulkification, sharing, security, testing, or maintainability\n\nDelegate elsewhere when the user is:\n- editing LWC JavaScript \u002F HTML \u002F CSS → [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md)\n- building Flow XML or Flow orchestration → [sf-flow](..\u002Fsf-flow\u002FSKILL.md)\n- writing SOQL only → [sf-soql](..\u002Fsf-soql\u002FSKILL.md)\n- deploying or validating metadata to orgs → [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- class type: trigger, service, selector, batch, queueable, schedulable, invocable, test\n- target object(s) and business goal\n- whether code is net-new, refactor, or fix\n- org \u002F API constraints if known\n- expected test coverage or deployment target\n\nBefore authoring, inspect the project shape:\n- existing classes \u002F triggers\n- current trigger framework or handler pattern\n- related tests, flows, and selectors\n- whether TAF is already in use\n\n---\n\n## Recommended Workflow\n\n### 1. Discover local architecture\nCheck for:\n- existing trigger handlers \u002F frameworks\n- service-selector-domain conventions\n- related tests and data factories\n- invocable or async patterns already used in the repo\n\n### 2. Choose the smallest correct pattern\n| Need | Preferred pattern |\n|---|---|\n| simple reusable logic | service class |\n| query-heavy data access | selector |\n| single object trigger behavior | one trigger + handler \u002F TAF action |\n| Flow needs complex logic | `@InvocableMethod` |\n| background processing | Queueable by default |\n| very large datasets | Batch Apex or `Database.Cursor` patterns |\n| repeatable verification | dedicated test class + test data factory |\n\n### 3. Author with guardrails\nGenerate code that is:\n- bulk-safe\n- sharing-aware\n- CRUD\u002FFLS-safe where applicable\n- testable in isolation\n- consistent with project naming and layering\n\n### 4. Validate and score\nEvaluate against the 150-point rubric before handoff.\n\n### 5. Hand off deploy\u002Ftest next steps\nWhen org validation is needed, hand off to:\n- [sf-testing](..\u002Fsf-testing\u002FSKILL.md) for test execution loops\n- [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) for deploy \u002F dry-run \u002F verification\n\n---\n\n## Generation Guardrails\n\nNever generate these without explicitly stopping and explaining the problem:\n\n| Anti-pattern | Why it blocks |\n|---|---|\n| SOQL in loops | governor-limit failure |\n| DML in loops | governor-limit failure |\n| missing sharing model | security \u002F data exposure risk |\n| hardcoded IDs | deployment and portability failure |\n| empty `catch` blocks | silent failure \u002F poor observability |\n| string-built SOQL with user input | injection risk |\n| tests without assertions | false-positive test suite |\n\nDefault fix direction:\n- query once, operate on collections\n- use `with sharing` unless justified otherwise\n- use bind variables and `WITH USER_MODE` where appropriate\n- create assertions for positive, negative, and bulk cases\n\nSee [references\u002Fanti-patterns.md](references\u002Fanti-patterns.md) and [references\u002Fsecurity-guide.md](references\u002Fsecurity-guide.md).\n\n---\n\n## High-Signal Build Rules\n\n### Trigger architecture\n- Prefer **one trigger per object**.\n- If TAF is already installed and used, extend it instead of inventing a second trigger pattern.\n- Triggers should delegate logic; avoid heavy business logic directly in trigger bodies.\n\n### Async choice\n| Scenario | Default |\n|---|---|\n| standard async work | Queueable |\n| very large record processing | Batch Apex |\n| recurring schedule | Scheduled Flow or Schedulable |\n| post-job cleanup | Finalizer |\n| long-running Lightning callouts | `Continuation` |\n\n### Testing minimums\nUse the **PNB** pattern for every feature:\n- **Positive** path\n- **Negative** \u002F error path\n- **Bulk** path (251+ records where relevant)\n\n### Modern Apex expectations\nPrefer current idioms when available:\n- safe navigation: `obj?.Field__c`\n- null coalescing: `value ?? fallback`\n- `Assert.*` over legacy assertion style\n- `WITH USER_MODE` and explicit security handling where relevant\n\n---\n\n## Output Format\n\nWhen finishing, report in this order:\n1. **What was created or reviewed**\n2. **Files changed**\n3. **Key design decisions**\n4. **Risk \u002F guardrail notes**\n5. **Test guidance**\n6. **Deployment guidance**\n\nSuggested shape:\n\n```text\nApex work: \u003Csummary>\nFiles: \u003Cpaths>\nDesign: \u003Cpattern \u002F framework choices>\nRisks: \u003Csecurity, bulkification, async, dependency notes>\nTests: \u003Cwhat to run \u002F add>\nDeploy: \u003Cdry-run or next step>\n```\n\n---\n\n## LSP Validation Note\n\nThis skill supports an LSP-assisted authoring loop for `.cls` and `.trigger` files:\n- syntax issues can be detected immediately after write\u002Fedit\n- the skill can auto-fix common syntax errors in a short loop\n- semantic quality still depends on the 150-point review rubric\n\nFull guide: [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md#lsp-based-validation-auto-fix-loop)\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| describe objects \u002F fields first | [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) | avoid coding against wrong schema |\n| seed bulk or edge-case data | [sf-data](..\u002Fsf-data\u002FSKILL.md) | create realistic test datasets |\n| run Apex tests \u002F fix failing tests | [sf-testing](..\u002Fsf-testing\u002FSKILL.md) | execute and iterate on failures |\n| deploy to org | [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) | validation and deployment orchestration |\n| build Flow that calls Apex | [sf-flow](..\u002Fsf-flow\u002FSKILL.md) | declarative orchestration |\n| build LWC that calls Apex | [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md) | UI\u002Fcontroller integration |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fpatterns-deep-dive.md](references\u002Fpatterns-deep-dive.md)\n- [references\u002Fsecurity-guide.md](references\u002Fsecurity-guide.md)\n- [references\u002Fbulkification-guide.md](references\u002Fbulkification-guide.md)\n- [references\u002Ftesting-patterns.md](references\u002Ftesting-patterns.md)\n\n### High-signal checklists\n- [references\u002Fcode-review-checklist.md](references\u002Fcode-review-checklist.md)\n- [references\u002Fanti-patterns.md](references\u002Fanti-patterns.md)\n- [references\u002Fnaming-conventions.md](references\u002Fnaming-conventions.md)\n\n### Specialized patterns\n- [references\u002Ftrigger-actions-framework.md](references\u002Ftrigger-actions-framework.md)\n- [references\u002Fautomation-density-guide.md](references\u002Fautomation-density-guide.md)\n- [references\u002Fflow-integration.md](references\u002Fflow-integration.md)\n- [references\u002Ftriangle-pattern.md](references\u002Ftriangle-pattern.md)\n- [references\u002Fdesign-patterns.md](references\u002Fdesign-patterns.md)\n- [references\u002Fsolid-principles.md](references\u002Fsolid-principles.md)\n\n### Troubleshooting \u002F validation\n- [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md)\n- [references\u002Fllm-anti-patterns.md](references\u002Fllm-anti-patterns.md)\n- [references\u002Ftesting-guide.md](references\u002Ftesting-guide.md)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 120+ | strong production-ready Apex |\n| 90–119 | good implementation, review before deploy |\n| 67–89 | acceptable but needs improvement |\n| \u003C 67 | block deployment |\n",{"name":5,"license":15,"metadata":24,"description":28},{"author":25,"scoring":26,"version":27},"Jag Valaiyapathy","150 points across 8 categories","1.1.0","Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch\u002Fqueueable\u002Fschedulable jobs, or touches .cls\u002F.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-apex\u002Fskills\u002Fsf-apex",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-apex",{"tool":43,"command":44},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-apex",{"tool":46,"command":47},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-apex","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-apex\u002Fskills\u002Fsf-apex\u002FSKILL.md",true,[],[52,59,64,71,76,83],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"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":60,"name":54,"nameZh":6,"description":55,"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},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"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":72,"name":66,"nameZh":6,"description":67,"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},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"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":84,"name":78,"nameZh":6,"description":79,"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},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]