[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CB7FH3S7GT8BEQ49AHTJHM":3,"skill-same:01M7CB7FH3S7GT8BEQ49AHTJHM":58},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7CB7FH3S7GT8BEQ49AHTJHM","sf-datacloud-prepare",null,"Salesforce Data Cloud Prepare phase. TRIGGER when: user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations, or asks about ingestion into Data Cloud. DO NOT TRIGGER when: the task is connection setup only (use sf-datacloud-connect), DMOs and identity resolution (use sf-datacloud-harmonize), or query\u002Fsearch work (use sf-datacloud-retrieve).","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-datacloud-prepare\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-datacloud-prepare\ndescription: >\n  Salesforce Data Cloud Prepare phase.\n  TRIGGER when: user creates or manages Data Cloud data streams, DLOs, transforms,\n  or Document AI configurations, or asks about ingestion into Data Cloud.\n  DO NOT TRIGGER when: the task is connection setup only (use sf-datacloud-connect),\n  DMOs and identity resolution (use sf-datacloud-harmonize), or query\u002Fsearch work (use sf-datacloud-retrieve).\nlicense: MIT\ncompatibility: \"Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org\"\nmetadata:\n  version: \"1.0.0\"\n  author: \"Gnanasekaran Thoppae\"\n  phase: \"Prepare\"\n---\n\n# sf-datacloud-prepare: Data Cloud Prepare Phase\n\nUse this skill when the user needs **ingestion and lake preparation work**: data streams, Data Lake Objects (DLOs), transforms, Document AI, unstructured ingestion, or the handoff from connector setup into a live stream.\n\n## When This Skill Owns the Task\n\nUse `sf-datacloud-prepare` when the work involves:\n- `sf data360 data-stream *`\n- `sf data360 dlo *`\n- `sf data360 transform *`\n- `sf data360 docai *`\n- choosing how data should enter Data Cloud\n- rerunning or rescanning ingestion after a source update\n- preparing Ingestion API-backed streams after connector setup is complete\n\nDelegate elsewhere when the user is:\n- still creating\u002Ftesting source connections → [sf-datacloud-connect](..\u002Fsf-datacloud-connect\u002FSKILL.md)\n- mapping to DMOs or designing IR\u002Fdata graphs → [sf-datacloud-harmonize](..\u002Fsf-datacloud-harmonize\u002FSKILL.md)\n- querying ingested data → [sf-datacloud-retrieve](..\u002Fsf-datacloud-retrieve\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias\n- source connection name\n- source object \u002F dataset \u002F document source\n- desired stream type\n- DLO naming expectations\n- whether the user is creating, updating, running, or deleting a stream\n- whether the source is CRM, a database connector, an unstructured file source, or an Ingestion API feed\n\n---\n\n## Core Operating Rules\n\n- Verify the external plugin runtime before running Data Cloud commands.\n- Run the shared readiness classifier before mutating ingestion assets: `node ~\u002F.claude\u002Fskills\u002Fsf-datacloud\u002Fscripts\u002Fdiagnose-org.mjs -o \u003Corg> --phase prepare --json`.\n- Prefer inspecting existing streams and DLOs before creating new ingestion assets.\n- Suppress linked-plugin warning noise with `2>\u002Fdev\u002Fnull` for normal usage.\n- Treat DLO naming and field naming as Data Cloud-specific, not CRM-native.\n- Confirm whether each dataset should be treated as `Profile`, `Engagement`, or `Other` before creating the stream.\n- Distinguish stream-level refresh from connection-level reruns when working with unstructured sources.\n- Use UI setup intentionally when initial stream or unstructured asset creation is platform-gated.\n- Hand off to Harmonize only after ingestion assets are clearly healthy.\n\n---\n\n## Recommended Workflow\n\n### 1. Classify readiness for prepare work\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fsf-datacloud\u002Fscripts\u002Fdiagnose-org.mjs -o \u003Corg> --phase prepare --json\n```\n\n### 2. Inspect existing ingestion assets\n```bash\nsf data360 data-stream list -o \u003Corg> 2>\u002Fdev\u002Fnull\nsf data360 dlo list -o \u003Corg> 2>\u002Fdev\u002Fnull\n```\n\n### 3. Confirm the stream category before creation\nUse these rules when suggesting categories:\n\n| Category | Use for | Typical requirement |\n|---|---|---|\n| `Profile` | person\u002Fentity records | primary key |\n| `Engagement` | time-based events or interactions | primary key + event time field |\n| `Other` | reference\u002Fconfiguration\u002Fsupporting datasets | primary key |\n\nWhen the source is ambiguous, ask the user explicitly whether the dataset should be treated as `Profile`, `Engagement`, or `Other`.\n\n### 4. Create or inspect streams intentionally\n```bash\nsf data360 data-stream get -o \u003Corg> --name \u003Cstream> 2>\u002Fdev\u002Fnull\nsf data360 data-stream create-from-object -o \u003Corg> --object Contact --connection SalesforceDotCom_Home 2>\u002Fdev\u002Fnull\nsf data360 data-stream create -o \u003Corg> -f stream.json 2>\u002Fdev\u002Fnull\nsf data360 data-stream run -o \u003Corg> --name \u003Cstream> 2>\u002Fdev\u002Fnull\n```\n\n### 5. Check DLO shape\n```bash\nsf data360 dlo get -o \u003Corg> --name Contact_Home__dll 2>\u002Fdev\u002Fnull\n```\n\n### 6. Choose the right refresh mechanism\nUse the smaller refresh scope that matches the user goal:\n\n```bash\nsf data360 data-stream run -o \u003Corg> --name \u003Cstream> 2>\u002Fdev\u002Fnull\nsf data360 connection run-existing -o \u003Corg> --name \u003Cconnection-id> 2>\u002Fdev\u002Fnull\n```\n\n- `data-stream run` is the closest match to a stream-level refresh or re-scan.\n- `connection run-existing` runs at the connection level and can be useful for some connector workflows, but it is not a reliable replacement for stream refresh on unstructured sources.\n- For unstructured document connectors, prefer `data-stream run` when the goal is to re-scan newly added or changed files.\n\n### 7. Handle unstructured sources deliberately\nFor SharePoint-style document ingestion, a minimal unstructured DLO payload can look like:\n\n```json\n{\n  \"name\": \"my_udlo\",\n  \"label\": \"My UDLO\",\n  \"category\": \"Directory_Table\",\n  \"dataSource\": {\n    \"sourceType\": \"SF_DRIVE\",\n    \"directoryAndFilesDetails\": [\n      {\n        \"dirName\": \"SPUnstructuredDocument\u002F\u003CCONNECTION_ID>\u002F\u003CSITE_ID>\",\n        \"fileName\": \"*\"\n      }\n    ],\n    \"sourceConfig\": {\n      \"reservedPrefix\": \"$dcf_content$\"\n    }\n  }\n}\n```\n\nUse the UI for the first-time unstructured setup when the user needs the richer end-to-end pipeline. The UI path can seed additional document metadata fields and downstream assets that a bare CLI DLO create flow may not provision automatically.\n\n### 8. Use the local Ingestion API example for send-data workflows\nFor external systems pushing records into Data Cloud:\n\n1. create the connector in [sf-datacloud-connect](..\u002Fsf-datacloud-connect\u002FSKILL.md)\n2. upload the schema with `sf data360 connection schema-upsert`\n3. create the stream in the UI when required\n4. send records with the local example in `examples\u002Fingestion-api\u002F`\n\n```bash\ncd examples\u002Fingestion-api\ncp .env.example .env\npython3 send-data.py\n```\n\nKey details:\n- auth is a staged flow: JWT → Salesforce token → Data Cloud token\n- the ingestion endpoint uses the tenant URL, not the Salesforce instance URL\n- `202` means the payload was accepted for processing, not that records are queryable immediately\n- validation failures often surface in the Problem Records DLO family\n\n### 9. Only then move into harmonization\nOnce the stream and DLO are healthy, hand off to [sf-datacloud-harmonize](..\u002Fsf-datacloud-harmonize\u002FSKILL.md).\n\n---\n\n## High-Signal Gotchas\n\n- CRM-backed stream behavior is not the same as fully custom connector-framework ingestion.\n- `sf data360 data-stream run` and `sf data360 connection run-existing` are not interchangeable; prefer stream-level refresh for unstructured rescans.\n- `SFDC` streams sync on a platform-managed schedule; `data-stream run` is not the general control path for CRM connector refresh.\n- Some external database connectors can be created via API while stream creation still requires UI flow or org-specific browser automation. Do not promise a pure CLI stream-creation path for every connector type.\n- Initial SharePoint-style unstructured setup can be richer in the UI than in a minimal CLI DLO create flow.\n- Stream deletion can also delete the associated DLO unless the delete mode says otherwise.\n- DLO field naming differs from CRM field naming, including `__c` → `_c` transformations.\n- Query DLO record counts with Data Cloud SQL instead of assuming list output is sufficient.\n- `CdpDataStreams` means the stream module is gated for the current org\u002Fuser; guide the user to provisioning\u002Fpermissions review instead of retrying blindly.\n\n---\n\n## Output Format\n\n```text\nPrepare task: \u003Cstream \u002F dlo \u002F transform \u002F docai>\nSource: \u003Cconnection + object>\nTarget org: \u003Calias>\nArtifacts: \u003Cstream names \u002F dlo names \u002F json definitions>\nVerification: \u003Cpassed \u002F partial \u002F blocked>\nNext step: \u003Charmonize or retrieve>\n```\n\n---\n\n## References\n\n- [README.md](README.md)\n- [examples\u002Fingestion-api\u002FREADME.md](examples\u002Fingestion-api\u002FREADME.md)\n- [..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fdata-stream.template.json](..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fdata-stream.template.json)\n- [..\u002Fsf-datacloud\u002Freferences\u002Fplugin-setup.md](..\u002Fsf-datacloud\u002Freferences\u002Fplugin-setup.md)\n- [..\u002Fsf-datacloud\u002Freferences\u002Ffeature-readiness.md](..\u002Fsf-datacloud\u002Freferences\u002Ffeature-readiness.md)\n","# sf-datacloud-prepare: Data Cloud Prepare Phase\n\nUse this skill when the user needs **ingestion and lake preparation work**: data streams, Data Lake Objects (DLOs), transforms, Document AI, unstructured ingestion, or the handoff from connector setup into a live stream.\n\n## When This Skill Owns the Task\n\nUse `sf-datacloud-prepare` when the work involves:\n- `sf data360 data-stream *`\n- `sf data360 dlo *`\n- `sf data360 transform *`\n- `sf data360 docai *`\n- choosing how data should enter Data Cloud\n- rerunning or rescanning ingestion after a source update\n- preparing Ingestion API-backed streams after connector setup is complete\n\nDelegate elsewhere when the user is:\n- still creating\u002Ftesting source connections → [sf-datacloud-connect](..\u002Fsf-datacloud-connect\u002FSKILL.md)\n- mapping to DMOs or designing IR\u002Fdata graphs → [sf-datacloud-harmonize](..\u002Fsf-datacloud-harmonize\u002FSKILL.md)\n- querying ingested data → [sf-datacloud-retrieve](..\u002Fsf-datacloud-retrieve\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias\n- source connection name\n- source object \u002F dataset \u002F document source\n- desired stream type\n- DLO naming expectations\n- whether the user is creating, updating, running, or deleting a stream\n- whether the source is CRM, a database connector, an unstructured file source, or an Ingestion API feed\n\n---\n\n## Core Operating Rules\n\n- Verify the external plugin runtime before running Data Cloud commands.\n- Run the shared readiness classifier before mutating ingestion assets: `node ~\u002F.claude\u002Fskills\u002Fsf-datacloud\u002Fscripts\u002Fdiagnose-org.mjs -o \u003Corg> --phase prepare --json`.\n- Prefer inspecting existing streams and DLOs before creating new ingestion assets.\n- Suppress linked-plugin warning noise with `2>\u002Fdev\u002Fnull` for normal usage.\n- Treat DLO naming and field naming as Data Cloud-specific, not CRM-native.\n- Confirm whether each dataset should be treated as `Profile`, `Engagement`, or `Other` before creating the stream.\n- Distinguish stream-level refresh from connection-level reruns when working with unstructured sources.\n- Use UI setup intentionally when initial stream or unstructured asset creation is platform-gated.\n- Hand off to Harmonize only after ingestion assets are clearly healthy.\n\n---\n\n## Recommended Workflow\n\n### 1. Classify readiness for prepare work\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fsf-datacloud\u002Fscripts\u002Fdiagnose-org.mjs -o \u003Corg> --phase prepare --json\n```\n\n### 2. Inspect existing ingestion assets\n```bash\nsf data360 data-stream list -o \u003Corg> 2>\u002Fdev\u002Fnull\nsf data360 dlo list -o \u003Corg> 2>\u002Fdev\u002Fnull\n```\n\n### 3. Confirm the stream category before creation\nUse these rules when suggesting categories:\n\n| Category | Use for | Typical requirement |\n|---|---|---|\n| `Profile` | person\u002Fentity records | primary key |\n| `Engagement` | time-based events or interactions | primary key + event time field |\n| `Other` | reference\u002Fconfiguration\u002Fsupporting datasets | primary key |\n\nWhen the source is ambiguous, ask the user explicitly whether the dataset should be treated as `Profile`, `Engagement`, or `Other`.\n\n### 4. Create or inspect streams intentionally\n```bash\nsf data360 data-stream get -o \u003Corg> --name \u003Cstream> 2>\u002Fdev\u002Fnull\nsf data360 data-stream create-from-object -o \u003Corg> --object Contact --connection SalesforceDotCom_Home 2>\u002Fdev\u002Fnull\nsf data360 data-stream create -o \u003Corg> -f stream.json 2>\u002Fdev\u002Fnull\nsf data360 data-stream run -o \u003Corg> --name \u003Cstream> 2>\u002Fdev\u002Fnull\n```\n\n### 5. Check DLO shape\n```bash\nsf data360 dlo get -o \u003Corg> --name Contact_Home__dll 2>\u002Fdev\u002Fnull\n```\n\n### 6. Choose the right refresh mechanism\nUse the smaller refresh scope that matches the user goal:\n\n```bash\nsf data360 data-stream run -o \u003Corg> --name \u003Cstream> 2>\u002Fdev\u002Fnull\nsf data360 connection run-existing -o \u003Corg> --name \u003Cconnection-id> 2>\u002Fdev\u002Fnull\n```\n\n- `data-stream run` is the closest match to a stream-level refresh or re-scan.\n- `connection run-existing` runs at the connection level and can be useful for some connector workflows, but it is not a reliable replacement for stream refresh on unstructured sources.\n- For unstructured document connectors, prefer `data-stream run` when the goal is to re-scan newly added or changed files.\n\n### 7. Handle unstructured sources deliberately\nFor SharePoint-style document ingestion, a minimal unstructured DLO payload can look like:\n\n```json\n{\n  \"name\": \"my_udlo\",\n  \"label\": \"My UDLO\",\n  \"category\": \"Directory_Table\",\n  \"dataSource\": {\n    \"sourceType\": \"SF_DRIVE\",\n    \"directoryAndFilesDetails\": [\n      {\n        \"dirName\": \"SPUnstructuredDocument\u002F\u003CCONNECTION_ID>\u002F\u003CSITE_ID>\",\n        \"fileName\": \"*\"\n      }\n    ],\n    \"sourceConfig\": {\n      \"reservedPrefix\": \"$dcf_content$\"\n    }\n  }\n}\n```\n\nUse the UI for the first-time unstructured setup when the user needs the richer end-to-end pipeline. The UI path can seed additional document metadata fields and downstream assets that a bare CLI DLO create flow may not provision automatically.\n\n### 8. Use the local Ingestion API example for send-data workflows\nFor external systems pushing records into Data Cloud:\n\n1. create the connector in [sf-datacloud-connect](..\u002Fsf-datacloud-connect\u002FSKILL.md)\n2. upload the schema with `sf data360 connection schema-upsert`\n3. create the stream in the UI when required\n4. send records with the local example in `examples\u002Fingestion-api\u002F`\n\n```bash\ncd examples\u002Fingestion-api\ncp .env.example .env\npython3 send-data.py\n```\n\nKey details:\n- auth is a staged flow: JWT → Salesforce token → Data Cloud token\n- the ingestion endpoint uses the tenant URL, not the Salesforce instance URL\n- `202` means the payload was accepted for processing, not that records are queryable immediately\n- validation failures often surface in the Problem Records DLO family\n\n### 9. Only then move into harmonization\nOnce the stream and DLO are healthy, hand off to [sf-datacloud-harmonize](..\u002Fsf-datacloud-harmonize\u002FSKILL.md).\n\n---\n\n## High-Signal Gotchas\n\n- CRM-backed stream behavior is not the same as fully custom connector-framework ingestion.\n- `sf data360 data-stream run` and `sf data360 connection run-existing` are not interchangeable; prefer stream-level refresh for unstructured rescans.\n- `SFDC` streams sync on a platform-managed schedule; `data-stream run` is not the general control path for CRM connector refresh.\n- Some external database connectors can be created via API while stream creation still requires UI flow or org-specific browser automation. Do not promise a pure CLI stream-creation path for every connector type.\n- Initial SharePoint-style unstructured setup can be richer in the UI than in a minimal CLI DLO create flow.\n- Stream deletion can also delete the associated DLO unless the delete mode says otherwise.\n- DLO field naming differs from CRM field naming, including `__c` → `_c` transformations.\n- Query DLO record counts with Data Cloud SQL instead of assuming list output is sufficient.\n- `CdpDataStreams` means the stream module is gated for the current org\u002Fuser; guide the user to provisioning\u002Fpermissions review instead of retrying blindly.\n\n---\n\n## Output Format\n\n```text\nPrepare task: \u003Cstream \u002F dlo \u002F transform \u002F docai>\nSource: \u003Cconnection + object>\nTarget org: \u003Calias>\nArtifacts: \u003Cstream names \u002F dlo names \u002F json definitions>\nVerification: \u003Cpassed \u002F partial \u002F blocked>\nNext step: \u003Charmonize or retrieve>\n```\n\n---\n\n## References\n\n- [README.md](README.md)\n- [examples\u002Fingestion-api\u002FREADME.md](examples\u002Fingestion-api\u002FREADME.md)\n- [..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fdata-stream.template.json](..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fdata-stream.template.json)\n- [..\u002Fsf-datacloud\u002Freferences\u002Fplugin-setup.md](..\u002Fsf-datacloud\u002Freferences\u002Fplugin-setup.md)\n- [..\u002Fsf-datacloud\u002Freferences\u002Ffeature-readiness.md](..\u002Fsf-datacloud\u002Freferences\u002Ffeature-readiness.md)\n",{"name":5,"license":15,"metadata":24,"description":28,"compatibility":29},{"phase":25,"author":26,"version":27},"Prepare","Gnanasekaran Thoppae","1.0.0","Salesforce Data Cloud Prepare phase. TRIGGER when: user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations, or asks about ingestion into Data Cloud. DO NOT TRIGGER when: the task is connection setup only (use sf-datacloud-connect), DMOs and identity resolution (use sf-datacloud-harmonize), or query\u002Fsearch work (use sf-datacloud-retrieve).\n","Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-datacloud-prepare",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":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-datacloud-prepare",{"tool":44,"command":45},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-datacloud-prepare",{"tool":47,"command":48},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-datacloud-prepare","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-datacloud-prepare\u002FSkill.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"metadata.json","REFERENCE","参考文档",454,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-datacloud-prepare\u002Fmetadata.json",[59,66,71,78,83,90],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":61,"nameZh":6,"description":62,"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},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":73,"nameZh":6,"description":74,"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},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]