[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C23CFWFBFRW35PXRY2WM9E":3,"skill-same:01M7C23CFWFBFRW35PXRY2WM9E":52},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7C23CFWFBFRW35PXRY2WM9E","swift-architecture-skill",null,"Swift iOS architecture guidance and playbooks for MVVM, MVI, TCA, Clean Architecture, VIPER, MVP, Coordinator, and Reactive patterns. Use when designing, implementing, refactoring, or reviewing the architecture of a SwiftUI or UIKit feature, module, or codebase.","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\u002Fefremidze-swift-architecture-skill\u002Fswift-architecture-skill\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: swift-architecture-skill\ndescription: Swift iOS architecture guidance and playbooks for MVVM, MVI, TCA, Clean Architecture, VIPER, MVP, Coordinator, and Reactive patterns. Use when designing, implementing, refactoring, or reviewing the architecture of a SwiftUI or UIKit feature, module, or codebase.\nlicense: MIT\n---\n\n# Swift Architecture Skill\n\n## Overview\n\nUse this skill to pick the best Swift architecture playbook for SwiftUI\u002FUIKit codebases and apply it to the user’s task.\n\nFor quick navigation across playbooks, use `references\u002F_index.md`.\n\n## Fast Path\n\nBefore selecting an architecture, always capture:\n- task type (new feature, refactor, PR review, debugging)\n- UI stack (SwiftUI, UIKit, or mixed)\n- scope (single screen, multi-screen, app-wide)\n- state and effect complexity\n- team familiarity and dependency tolerance\n- existing conventions to preserve\n\nThen:\n- if the user explicitly names an architecture, treat it as the initial candidate and run a fit check first\n- if no architecture is named, load `references\u002Fselection-guide.md` and infer the best fit from the stated constraints\n- if the best fit combines patterns, name one **primary** playbook for the feature boundary and one **secondary** playbook for the supporting concern\n- choose **Quick Recommendation Mode** for single-feature guidance with clear constraints\n- choose **Deep Refactor Mode** for migrations, mixed architectures, or module boundary changes\n\n## Quick Recommendation Mode\n\nUse this mode when:\n- the scope is one feature or screen\n- constraints are clear enough to recommend one primary pattern\n- the user mainly needs a recommendation, scaffold, or review checklist\n\nDeliver:\n- fit result (`fit` or `mismatch`)\n- 1-2 reasons grounded in the request\n- the selected reference file\n- concrete structure, state, dependency, async, and testing guidance scoped to the feature\n\n## Deep Refactor Mode\n\nUse this mode when:\n- the request spans multiple modules or screens\n- the codebase already mixes architectures\n- the user is migrating from one pattern to another\n\nDeliver:\n- current-state assessment\n- target architecture recommendation with fit or mismatch result\n- incremental migration path with boundary changes called out\n- risks, trade-offs, and verification points for the transition\n\n## Architecture Router\n\nIf the user explicitly names an architecture, treat it as the initial candidate and run a fit check before committing:\n- validate against UI stack fit (SwiftUI\u002FUIKit\u002Fmixed), state complexity, effect orchestration needs, team familiarity, and existing codebase conventions\n- if it fits, proceed with the requested architecture\n- if it mismatches key constraints, explicitly explain the mismatch and recommend the closest-fit alternative from `references\u002Fselection-guide.md`\n- if the user still insists on a mismatched architecture, proceed with a risk-mitigated plan and state the risks up front\n\nArchitecture reference mapping:\n- MVVM → `references\u002Fmvvm.md`\n- MVI → `references\u002Fmvi.md`\n- TCA → `references\u002Ftca.md`\n- Clean Architecture → `references\u002Fclean-architecture.md`\n- VIPER → `references\u002Fviper.md`\n- Reactive → `references\u002Freactive.md`\n- MVP → `references\u002Fmvp.md`\n- Coordinator → `references\u002Fcoordinator.md`\n\nCombination routing:\n- Coordinator is usually secondary unless the user's main problem is flow ownership, deep linking, or reusable navigation.\n- Reactive is usually secondary when streams live inside MVVM, MVP, VIPER, MVI, or TCA presentation boundaries.\n- Clean Architecture is usually primary for app\u002Fmodule layering, with MVVM, MVP, or TCA as the presentation pattern.\n- When combining, read both references and state which pattern owns each boundary before giving file structure or code.\n\n## Analyze Existing Codebase (When Applicable)\n\nWhen code already exists:\n- detect current architecture and DI style\n- note concurrency model (async\u002Fawait, Combine, GCD, mixed)\n- align recommendations to local conventions\n\n## Guardrails\n\n- Do not force an architecture switch for a small feature when the current local pattern is still a reasonable fit.\n- Preserve existing conventions unless the mismatch is severe enough to justify change.\n- Do not introduce new framework dependencies such as TCA unless the user explicitly accepts that trade-off or the codebase already uses them.\n- Prefer the smallest architecture change that solves the request cleanly.\n- Keep guidance architecture-specific; do not blend playbooks unless the boundary between patterns is explicit.\n- For combined patterns, avoid merging responsibilities: identify the primary boundary first, then apply the secondary playbook only to its concern.\n\n## Produce Concrete Deliverables\n\nRead the selected architecture reference and convert its guidance into deliverables tailored to the user's request:\n\n- **File and module structure**: directory layout with file names specific to the feature\n- **State and dependency boundaries**: concrete types, protocols, and injection points\n- **Async strategy**: cancellation, actor isolation, and error paths\n- **Testing strategy**: what to test, how to stub dependencies, and example test structure\n- **Migration path** (for refactors): incremental steps to move from current to target architecture\n- **UI stack adaptation**: where SwiftUI and UIKit guidance should differ for the chosen architecture\n\n## Output Requirements\n\n- Keep recommendations scoped to the requested feature or review task.\n- Prefer protocol-based dependency injection and explicit state modeling.\n- Flag anti-patterns found in existing code and provide direct fixes.\n- Include cancellation and error handling in all async flows.\n- For explicit architecture requests, include a short fit result (`fit` or `mismatch`) with 1-2 reasons.\n- For mismatch cases, include one closest-fit alternative and why it better matches the stated constraints.\n- When writing code, include only the patterns relevant to the task — do not dump entire playbooks.\n- Treat reference snippets as illustrative by default; add full compile scaffolding only if the user asks for runnable code.\n- Ask only minimum blocking questions; otherwise proceed with explicit assumptions stated up front.\n- When reviewing PRs, use the architecture-specific checklist and call out specific violations with line-level fixes.\n\n## Verification Checklist\n\nBefore finalizing:\n\n1. confirm the selected pattern matches the user’s constraints and stack\n2. confirm dependency injection, state ownership, effects, and testing strategy are covered\n3. call out migration risk explicitly when recommending an architecture change\n4. end with the selected architecture’s PR review checklist adapted to the user’s feature\n","# Swift Architecture Skill\n\n## Overview\n\nUse this skill to pick the best Swift architecture playbook for SwiftUI\u002FUIKit codebases and apply it to the user’s task.\n\nFor quick navigation across playbooks, use `references\u002F_index.md`.\n\n## Fast Path\n\nBefore selecting an architecture, always capture:\n- task type (new feature, refactor, PR review, debugging)\n- UI stack (SwiftUI, UIKit, or mixed)\n- scope (single screen, multi-screen, app-wide)\n- state and effect complexity\n- team familiarity and dependency tolerance\n- existing conventions to preserve\n\nThen:\n- if the user explicitly names an architecture, treat it as the initial candidate and run a fit check first\n- if no architecture is named, load `references\u002Fselection-guide.md` and infer the best fit from the stated constraints\n- if the best fit combines patterns, name one **primary** playbook for the feature boundary and one **secondary** playbook for the supporting concern\n- choose **Quick Recommendation Mode** for single-feature guidance with clear constraints\n- choose **Deep Refactor Mode** for migrations, mixed architectures, or module boundary changes\n\n## Quick Recommendation Mode\n\nUse this mode when:\n- the scope is one feature or screen\n- constraints are clear enough to recommend one primary pattern\n- the user mainly needs a recommendation, scaffold, or review checklist\n\nDeliver:\n- fit result (`fit` or `mismatch`)\n- 1-2 reasons grounded in the request\n- the selected reference file\n- concrete structure, state, dependency, async, and testing guidance scoped to the feature\n\n## Deep Refactor Mode\n\nUse this mode when:\n- the request spans multiple modules or screens\n- the codebase already mixes architectures\n- the user is migrating from one pattern to another\n\nDeliver:\n- current-state assessment\n- target architecture recommendation with fit or mismatch result\n- incremental migration path with boundary changes called out\n- risks, trade-offs, and verification points for the transition\n\n## Architecture Router\n\nIf the user explicitly names an architecture, treat it as the initial candidate and run a fit check before committing:\n- validate against UI stack fit (SwiftUI\u002FUIKit\u002Fmixed), state complexity, effect orchestration needs, team familiarity, and existing codebase conventions\n- if it fits, proceed with the requested architecture\n- if it mismatches key constraints, explicitly explain the mismatch and recommend the closest-fit alternative from `references\u002Fselection-guide.md`\n- if the user still insists on a mismatched architecture, proceed with a risk-mitigated plan and state the risks up front\n\nArchitecture reference mapping:\n- MVVM → `references\u002Fmvvm.md`\n- MVI → `references\u002Fmvi.md`\n- TCA → `references\u002Ftca.md`\n- Clean Architecture → `references\u002Fclean-architecture.md`\n- VIPER → `references\u002Fviper.md`\n- Reactive → `references\u002Freactive.md`\n- MVP → `references\u002Fmvp.md`\n- Coordinator → `references\u002Fcoordinator.md`\n\nCombination routing:\n- Coordinator is usually secondary unless the user's main problem is flow ownership, deep linking, or reusable navigation.\n- Reactive is usually secondary when streams live inside MVVM, MVP, VIPER, MVI, or TCA presentation boundaries.\n- Clean Architecture is usually primary for app\u002Fmodule layering, with MVVM, MVP, or TCA as the presentation pattern.\n- When combining, read both references and state which pattern owns each boundary before giving file structure or code.\n\n## Analyze Existing Codebase (When Applicable)\n\nWhen code already exists:\n- detect current architecture and DI style\n- note concurrency model (async\u002Fawait, Combine, GCD, mixed)\n- align recommendations to local conventions\n\n## Guardrails\n\n- Do not force an architecture switch for a small feature when the current local pattern is still a reasonable fit.\n- Preserve existing conventions unless the mismatch is severe enough to justify change.\n- Do not introduce new framework dependencies such as TCA unless the user explicitly accepts that trade-off or the codebase already uses them.\n- Prefer the smallest architecture change that solves the request cleanly.\n- Keep guidance architecture-specific; do not blend playbooks unless the boundary between patterns is explicit.\n- For combined patterns, avoid merging responsibilities: identify the primary boundary first, then apply the secondary playbook only to its concern.\n\n## Produce Concrete Deliverables\n\nRead the selected architecture reference and convert its guidance into deliverables tailored to the user's request:\n\n- **File and module structure**: directory layout with file names specific to the feature\n- **State and dependency boundaries**: concrete types, protocols, and injection points\n- **Async strategy**: cancellation, actor isolation, and error paths\n- **Testing strategy**: what to test, how to stub dependencies, and example test structure\n- **Migration path** (for refactors): incremental steps to move from current to target architecture\n- **UI stack adaptation**: where SwiftUI and UIKit guidance should differ for the chosen architecture\n\n## Output Requirements\n\n- Keep recommendations scoped to the requested feature or review task.\n- Prefer protocol-based dependency injection and explicit state modeling.\n- Flag anti-patterns found in existing code and provide direct fixes.\n- Include cancellation and error handling in all async flows.\n- For explicit architecture requests, include a short fit result (`fit` or `mismatch`) with 1-2 reasons.\n- For mismatch cases, include one closest-fit alternative and why it better matches the stated constraints.\n- When writing code, include only the patterns relevant to the task — do not dump entire playbooks.\n- Treat reference snippets as illustrative by default; add full compile scaffolding only if the user asks for runnable code.\n- Ask only minimum blocking questions; otherwise proceed with explicit assumptions stated up front.\n- When reviewing PRs, use the architecture-specific checklist and call out specific violations with line-level fixes.\n\n## Verification Checklist\n\nBefore finalizing:\n\n1. confirm the selected pattern matches the user’s constraints and stack\n2. confirm dependency injection, state ownership, effects, and testing strategy are covered\n3. call out migration risk explicitly when recommending an architecture change\n4. end with the selected architecture’s PR review checklist adapted to the user’s feature\n",{"name":5,"license":15,"description":7},"main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fefremidze-swift-architecture-skill\u002Fswift-architecture-skill",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill swift-architecture-skill",{"tool":38,"command":39},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill swift-architecture-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill swift-architecture-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fefremidze-swift-architecture-skill\u002Fswift-architecture-skill\u002FSkill.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"metadata.json","REFERENCE","参考文档",551,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fefremidze-swift-architecture-skill\u002Fswift-architecture-skill\u002Fmetadata.json",[53,60,65,72,77,84],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":79,"nameZh":6,"description":80,"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},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]