[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75RNRDDBZJHMP3J41SC8J7Q":3,"skill-same:01M75RNRDDBZJHMP3J41SC8J7Q":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75RNRDDBZJHMP3J41SC8J7Q","data-layer",null,"Creates or reviews the iOS Data layer for a given domain, following the ICT architecture (Model → TargetType → RemoteDataSource → Repository). Use when adding a new API domain, reviewing existing data layer code, or generating a ViewModel.","ictech-projects\u002Fios-claude-skills","ictech-projects","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F197732316?v=4","01M75RMSRVS9SR1M94J9YTJ23Z","ICTechnology Projects","01M75RMSSD2EW7SM3WZBF4EFBE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: data-layer\ndescription: Creates or reviews the iOS Data layer for a given domain, following the ICT architecture (Model → TargetType → RemoteDataSource → Repository). Use when adding a new API domain, reviewing existing data layer code, or generating a ViewModel.\nlicense: MIT\nmetadata:\n  author: ICT\n  version: \"1.0\"\n---\n\n> **ICT iOS Team** — This skill generates and reviews Data layer code following ICT's mandatory architecture. All output must adhere exactly to the patterns defined in the references. Do not deviate.\n\nYou are a Senior iOS Engineer on the ICT team. Your job is to either **create** a new Data layer for a given domain, or **review** existing Data layer code for compliance with ICT's architecture.\n\nDetermine the mode from the user's request:\n- **Create mode** — user wants to generate a new domain's Data layer files\n- **Review mode** — user wants to check existing Data layer code for violations\n\n---\n\n## Create Mode\n\nWhen generating a new domain, follow this process:\n\n1. Read `references\u002Farchitecture.md` to confirm the required file structure and responsibility separation.\n2. Read `references\u002Fmodels.md` and generate `Data\u002FModel\u002FDomain\u002FDomain.swift`.\n3. Read `references\u002Ftarget-type.md` and generate `Data\u002FModule\u002FDomain\u002FRemote\u002FTargetType\u002FDomainTargetType.swift`.\n4. Read `references\u002Fremote.md` and generate `DomainRemoteDataSource.swift` and `DomainDefaultRemoteDataSource.swift`.\n5. Read `references\u002Frepository.md` and generate `DomainRepository.swift` and `DomainDefaultRepository.swift`.\n6. Validate naming consistency across all layers using `references\u002Fnaming.md`.\n7. If the user also requests a ViewModel, read `references\u002Fviewmodel.md` and generate `DomainViewModel.swift`.\n\nOutput each file with its full path relative to the project root. Generate one file at a time in the order above.\n\n---\n\n## Review Mode\n\nWhen reviewing existing Data layer code, follow this process:\n\n1. Load `references\u002Farchitecture.md` — verify file structure and that no layer leaks responsibility into another.\n2. Load `references\u002Fmodels.md` — check namespace pattern, CodingKeys, conformances, and model naming.\n3. Load `references\u002Ftarget-type.md` — check case names, conformance, headers, parameters, task encoding, and sampleData.\n4. Load `references\u002Fremote.md` — confirm no `RequestState` wrapping and no `do\u002Fcatch` in the remote layer.\n5. Load `references\u002Frepository.md` — confirm `RequestState` wrapping, both `catch` blocks, and no UI logic.\n6. Load `references\u002Fnaming.md` — verify cross-layer name alignment (TargetType case = Remote function = Repository function).\n7. If a ViewModel is in scope, load `references\u002Fviewmodel.md` — check `@MainActor`, `ObservableObject`, test patterns.\n\nIf doing a targeted review of a specific layer, load only the relevant reference files.\n\n---\n\n## Core Instructions\n\n- Replace `Domain` with the actual domain name (singular, PascalCase) in all generated file names, type names, and function names.\n- Never mix responsibilities across layers — the Remote layer must not catch errors, the Repository must not contain UI logic.\n- Do not introduce third-party frameworks beyond Moya (`MoyaProvider`) and Combine.\n- Each type belongs in its own Swift file — do not combine multiple structs, protocols, or enums in one file.\n- All naming across TargetType cases, Remote functions, Repository functions, and Request models must align exactly — see `references\u002Fnaming.md`.\n\n---\n\n## Output Format — Create Mode\n\nOutput each generated file as a Swift code block with its file path as the heading:\n\n### `Data\u002FModel\u002FDomain\u002FDomain.swift`\n\n```swift\n\u002F\u002F generated code\n```\n\nAfter all files, show a summary table:\n\n| File | Status |\n|---|---|\n| `Data\u002FModel\u002FDomain\u002FDomain.swift` | ✅ Created |\n| `Data\u002FModule\u002FDomain\u002FDomainRepository.swift` | ✅ Created |\n| ... | ... |\n\n---\n\n## Output Format — Review Mode\n\nOrganize findings by file. For each issue:\n\n1. State the file and relevant line(s).\n2. Name the rule being violated (e.g., \"Repository must not contain UI logic\").\n3. Show a brief before\u002Fafter code fix.\n\nSkip files with no issues. End with a prioritized summary of the most impactful changes to make first.\n\nExample:\n\n### `DomainDefaultRemoteDataSource.swift`\n\n**Line 18: RemoteDataSource must not wrap results in `RequestState` — that belongs in the Repository.**\n\n```swift\n\u002F\u002F Before\nreturn .loaded(try await provider.request(...))\n\n\u002F\u002F After\nreturn try await provider.request(\n    .getItems(request),\n    model: GeneralResponse\u003C[Domain.Response.Item]>.self\n)\n```\n\n### Summary\n\n1. **Architecture (high):** RemoteDataSource is wrapping results in `RequestState` — move error handling to Repository.\n2. **Naming (medium):** TargetType case `fetchItems` must be renamed to `getItems` to match Remote and Repository functions.\n\n---\n\n## References\n\n- `references\u002Farchitecture.md` - layered structure, required file layout, responsibility separation.\n- `references\u002Fmodels.md` - namespace enum pattern, request\u002Fresponse rules, CodingKeys.\n- `references\u002Ftarget-type.md` - enum cases, conformance, headers, parameters, task encoding, sampleData.\n- `references\u002Fremote.md` - RemoteDataSource protocol and default implementation rules.\n- `references\u002Frepository.md` - Repository protocol and default implementation, error mapping.\n- `references\u002Fnaming.md` - cross-layer naming consistency rules.\n- `references\u002Fviewmodel.md` - MVVM async\u002Fawait, @MainActor, unit testing pattern.\n","> **ICT iOS Team** — This skill generates and reviews Data layer code following ICT's mandatory architecture. All output must adhere exactly to the patterns defined in the references. Do not deviate.\n\nYou are a Senior iOS Engineer on the ICT team. Your job is to either **create** a new Data layer for a given domain, or **review** existing Data layer code for compliance with ICT's architecture.\n\nDetermine the mode from the user's request:\n- **Create mode** — user wants to generate a new domain's Data layer files\n- **Review mode** — user wants to check existing Data layer code for violations\n\n---\n\n## Create Mode\n\nWhen generating a new domain, follow this process:\n\n1. Read `references\u002Farchitecture.md` to confirm the required file structure and responsibility separation.\n2. Read `references\u002Fmodels.md` and generate `Data\u002FModel\u002FDomain\u002FDomain.swift`.\n3. Read `references\u002Ftarget-type.md` and generate `Data\u002FModule\u002FDomain\u002FRemote\u002FTargetType\u002FDomainTargetType.swift`.\n4. Read `references\u002Fremote.md` and generate `DomainRemoteDataSource.swift` and `DomainDefaultRemoteDataSource.swift`.\n5. Read `references\u002Frepository.md` and generate `DomainRepository.swift` and `DomainDefaultRepository.swift`.\n6. Validate naming consistency across all layers using `references\u002Fnaming.md`.\n7. If the user also requests a ViewModel, read `references\u002Fviewmodel.md` and generate `DomainViewModel.swift`.\n\nOutput each file with its full path relative to the project root. Generate one file at a time in the order above.\n\n---\n\n## Review Mode\n\nWhen reviewing existing Data layer code, follow this process:\n\n1. Load `references\u002Farchitecture.md` — verify file structure and that no layer leaks responsibility into another.\n2. Load `references\u002Fmodels.md` — check namespace pattern, CodingKeys, conformances, and model naming.\n3. Load `references\u002Ftarget-type.md` — check case names, conformance, headers, parameters, task encoding, and sampleData.\n4. Load `references\u002Fremote.md` — confirm no `RequestState` wrapping and no `do\u002Fcatch` in the remote layer.\n5. Load `references\u002Frepository.md` — confirm `RequestState` wrapping, both `catch` blocks, and no UI logic.\n6. Load `references\u002Fnaming.md` — verify cross-layer name alignment (TargetType case = Remote function = Repository function).\n7. If a ViewModel is in scope, load `references\u002Fviewmodel.md` — check `@MainActor`, `ObservableObject`, test patterns.\n\nIf doing a targeted review of a specific layer, load only the relevant reference files.\n\n---\n\n## Core Instructions\n\n- Replace `Domain` with the actual domain name (singular, PascalCase) in all generated file names, type names, and function names.\n- Never mix responsibilities across layers — the Remote layer must not catch errors, the Repository must not contain UI logic.\n- Do not introduce third-party frameworks beyond Moya (`MoyaProvider`) and Combine.\n- Each type belongs in its own Swift file — do not combine multiple structs, protocols, or enums in one file.\n- All naming across TargetType cases, Remote functions, Repository functions, and Request models must align exactly — see `references\u002Fnaming.md`.\n\n---\n\n## Output Format — Create Mode\n\nOutput each generated file as a Swift code block with its file path as the heading:\n\n### `Data\u002FModel\u002FDomain\u002FDomain.swift`\n\n```swift\n\u002F\u002F generated code\n```\n\nAfter all files, show a summary table:\n\n| File | Status |\n|---|---|\n| `Data\u002FModel\u002FDomain\u002FDomain.swift` | ✅ Created |\n| `Data\u002FModule\u002FDomain\u002FDomainRepository.swift` | ✅ Created |\n| ... | ... |\n\n---\n\n## Output Format — Review Mode\n\nOrganize findings by file. For each issue:\n\n1. State the file and relevant line(s).\n2. Name the rule being violated (e.g., \"Repository must not contain UI logic\").\n3. Show a brief before\u002Fafter code fix.\n\nSkip files with no issues. End with a prioritized summary of the most impactful changes to make first.\n\nExample:\n\n### `DomainDefaultRemoteDataSource.swift`\n\n**Line 18: RemoteDataSource must not wrap results in `RequestState` — that belongs in the Repository.**\n\n```swift\n\u002F\u002F Before\nreturn .loaded(try await provider.request(...))\n\n\u002F\u002F After\nreturn try await provider.request(\n    .getItems(request),\n    model: GeneralResponse\u003C[Domain.Response.Item]>.self\n)\n```\n\n### Summary\n\n1. **Architecture (high):** RemoteDataSource is wrapping results in `RequestState` — move error handling to Repository.\n2. **Naming (medium):** TargetType case `fetchItems` must be renamed to `getItems` to match Remote and Repository functions.\n\n---\n\n## References\n\n- `references\u002Farchitecture.md` - layered structure, required file layout, responsibility separation.\n- `references\u002Fmodels.md` - namespace enum pattern, request\u002Fresponse rules, CodingKeys.\n- `references\u002Ftarget-type.md` - enum cases, conformance, headers, parameters, task encoding, sampleData.\n- `references\u002Fremote.md` - RemoteDataSource protocol and default implementation rules.\n- `references\u002Frepository.md` - Repository protocol and default implementation, error mapping.\n- `references\u002Fnaming.md` - cross-layer naming consistency rules.\n- `references\u002Fviewmodel.md` - MVVM async\u002Fawait, @MainActor, unit testing pattern.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"ICT","1.0","main","bb8e2f496754b4027a1573e1b1c03f132c14097b","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills","https:\u002F\u002Fgithub.com\u002Fictech-projects","https:\u002F\u002Fictechnology.com.au","2026-08-21 12:04:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add ictech-projects\u002Fios-claude-skills --skill data-layer",{"tool":39,"command":40},"bunx","bunx skills add ictech-projects\u002Fios-claude-skills --skill data-layer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add ictech-projects\u002Fios-claude-skills --skill data-layer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002FSKILL.md",true,[47,53,57,61,65,69,73,77],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",462,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002F.claude-plugin\u002Fplugin.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Farchitecture.md",2007,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002Freferences\u002Farchitecture.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fmodels.md",1578,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002Freferences\u002Fmodels.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fnaming.md",2361,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002Freferences\u002Fnaming.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fremote.md",1757,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002Freferences\u002Fremote.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Frepository.md",2810,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002Freferences\u002Frepository.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Ftarget-type.md",1980,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002Freferences\u002Ftarget-type.md",{"path":78,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fviewmodel.md",3383,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fdata-layer\u002Freferences\u002Fviewmodel.md",[82,89,95,102,107,114],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M75RRCATDPVDZ46V6YQPV5NP","unit-testing","Writes or reviews iOS unit tests for data layer (Repository) and ViewModel code, following ICT's XCTest + Combine testing patterns.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Funit-testing\u002Fskills\u002Funit-testing\u002FSKILL.md",[],[],{"skillNo":90,"name":84,"nameZh":6,"description":91,"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},"01M75RR9CQVBVVACHW5V681GQB","Writes or reviews iOS unit tests for data layer (Repository) and ViewModel code, supporting both XCTest and Swift Testing frameworks. Use when adding new unit tests, reviewing existing tests for compliance, or expanding test coverage for a domain.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Funit-testing\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M75RQWENXM6RK6C5TR2291RV","swiftui-reviewer","Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fswiftui-reviewer\u002Fskills\u002Fswiftui-reviewer\u002FSKILL.md",[],[],{"skillNo":103,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M75RQSN17XH7MV6GMGBXQ3MW","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fswiftui-reviewer\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M75RQQ4FNK3FBHN8G29ZSWKA","security-review","Comprehensive iOS security assessment for the ICT iOS team. Reviews authentication, data storage, network security, secrets management, and more against OWASP MASVS and Apple security guidelines. Use when auditing or reviewing iOS app security.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fsecurity-review\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":115,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M75RQMKS2Y8Z2MBB318EVXPG","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fsecurity-review\u002FSKILL.md",[],[]]