[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72BCFR3ZMC7N26VRACF66RE":3,"skill-same:01M72BCFR3ZMC7N26VRACF66RE":70},{"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":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M72BCFR3ZMC7N26VRACF66RE","swift-testing-pro",null,"Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.","guhans6\u002Fagent-workbench","guhans6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104162539?v=4","01M72B46KNSP1Y4W32NAP9HSCS","Guhan","01M72B46MCE81N1B04M3PWX3P7",0,"MIT","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswift-testing-pro\u002Fskills\u002Fswift-testing-pro\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: swift-testing-pro\ndescription: Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.\nlicense: MIT\nargument-hint: \"[focus area]\"\nmetadata:\n  author: Paul Hudson\n  version: \"1.0\"\n---\n\nWrite and review Swift Testing code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems - do not nitpick or invent issues.\n\nReview process:\n\n1. Ensure tests follow core Swift Testing conventions using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fcore-rules.md`.\n1. Validate test structure, assertions, dependency injection, and other best practices using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fwriting-better-tests.md`.\n1. Check async tests, confirmations, time limits, actor isolation, and networking mocks using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fasync-tests.md`.\n1. Ensure new features like raw identifiers, test scopes, exit tests, and attachments are used correctly using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fnew-features.md`.\n1. If migrating from XCTest, follow the conversion guidance in `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fmigrating-from-xctest.md`.\n\nIf doing partial work, load only the relevant reference files.\n\n\n## Core Instructions\n\n- Target Swift 6.2 or later, using modern Swift concurrency.\n- As a Swift Testing developer, the user wants all new unit and integration tests to be written using Swift Testing, and they may ask for help migrating existing XCTest code to Swift Testing.\n- Swift Testing does *not* support UI tests – XCTest must be used there.\n- Use a consistent project structure, with folder layout determined by app features.\n\nSwift Testing evolves with each Swift release, so expect three to four releases each year, each introducing new features. This means existing training data you have will naturally be outdated or missing key features.\n\nThis skill specifically draws upon the very latest Swift and Swift Testing code, which means it will suggest things you are not aware of. Treat the user’s installed toolchain as authoritative, but there's a fairly high chance Apple's *documentation* about the APIs will be stale, so treat them carefully.\n\n\n## Output Format\n\nIf the user asks for a review, organize findings by file. For each issue:\n\n1. State the file and relevant line(s).\n2. Name the rule being violated.\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\nIf the user asks you to write or improve tests, follow the same rules above but make the changes directly instead of returning a findings report.\n\nExample output:\n\n### UserTests.swift\n\n**Line 5: Use struct, not class, for test suites.**\n\n```swift\n\u002F\u002F Before\nclass UserTests: XCTestCase {\n\n\u002F\u002F After\nstruct UserTests {\n```\n\n**Line 12: Use `#expect` instead of `XCTAssertEqual`.**\n\n```swift\n\u002F\u002F Before\nXCTAssertEqual(user.name, \"Taylor\")\n\n\u002F\u002F After\n#expect(user.name == \"Taylor\")\n```\n\n**Line 30: Use `#require` for preconditions, not `#expect`.**\n\n```swift\n\u002F\u002F Before\n#expect(users.isEmpty == false)\nlet first = users.first!\n\n\u002F\u002F After\nlet first = try #require(users.first)\n```\n\n### Summary\n\n1. **Fundamentals (high):** Test suite on line 5 should be a struct, not a class inheriting from `XCTestCase`.\n2. **Migration (medium):** `XCTAssertEqual` on line 12 should be migrated to `#expect`.\n3. **Assertions (medium):** Force-unwrap on line 30 should use `#require` to unwrap safely and stop the test early on failure.\n\nEnd of example.\n\n\n## References\n\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fcore-rules.md` - core Swift Testing rules: structs over classes, `init`\u002F`deinit` over setUp\u002FtearDown, parallel execution, parameterized tests, `withKnownIssue`, and tags.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fwriting-better-tests.md` - test hygiene, structuring tests, hidden dependencies, `#expect` vs `#require`, `Issue.record()`, `#expect(throws:)`, and verification methods.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fasync-tests.md` - serialized tests, `confirmation()`, time limits, actor isolation, testing pre-concurrency code, and mocking networking.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fnew-features.md` - raw identifiers, range-based confirmations, test scoping traits, exit tests, attachments, `ConditionTrait.evaluate()`, and the updated `#expect(throws:)` return value.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fmigrating-from-xctest.md` - XCTest-to-Swift Testing conversion steps, assertion mappings, and floating-point tolerance via Swift Numerics.\n","Write and review Swift Testing code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems - do not nitpick or invent issues.\n\nReview process:\n\n1. Ensure tests follow core Swift Testing conventions using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fcore-rules.md`.\n1. Validate test structure, assertions, dependency injection, and other best practices using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fwriting-better-tests.md`.\n1. Check async tests, confirmations, time limits, actor isolation, and networking mocks using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fasync-tests.md`.\n1. Ensure new features like raw identifiers, test scopes, exit tests, and attachments are used correctly using `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fnew-features.md`.\n1. If migrating from XCTest, follow the conversion guidance in `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fmigrating-from-xctest.md`.\n\nIf doing partial work, load only the relevant reference files.\n\n\n## Core Instructions\n\n- Target Swift 6.2 or later, using modern Swift concurrency.\n- As a Swift Testing developer, the user wants all new unit and integration tests to be written using Swift Testing, and they may ask for help migrating existing XCTest code to Swift Testing.\n- Swift Testing does *not* support UI tests – XCTest must be used there.\n- Use a consistent project structure, with folder layout determined by app features.\n\nSwift Testing evolves with each Swift release, so expect three to four releases each year, each introducing new features. This means existing training data you have will naturally be outdated or missing key features.\n\nThis skill specifically draws upon the very latest Swift and Swift Testing code, which means it will suggest things you are not aware of. Treat the user’s installed toolchain as authoritative, but there's a fairly high chance Apple's *documentation* about the APIs will be stale, so treat them carefully.\n\n\n## Output Format\n\nIf the user asks for a review, organize findings by file. For each issue:\n\n1. State the file and relevant line(s).\n2. Name the rule being violated.\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\nIf the user asks you to write or improve tests, follow the same rules above but make the changes directly instead of returning a findings report.\n\nExample output:\n\n### UserTests.swift\n\n**Line 5: Use struct, not class, for test suites.**\n\n```swift\n\u002F\u002F Before\nclass UserTests: XCTestCase {\n\n\u002F\u002F After\nstruct UserTests {\n```\n\n**Line 12: Use `#expect` instead of `XCTAssertEqual`.**\n\n```swift\n\u002F\u002F Before\nXCTAssertEqual(user.name, \"Taylor\")\n\n\u002F\u002F After\n#expect(user.name == \"Taylor\")\n```\n\n**Line 30: Use `#require` for preconditions, not `#expect`.**\n\n```swift\n\u002F\u002F Before\n#expect(users.isEmpty == false)\nlet first = users.first!\n\n\u002F\u002F After\nlet first = try #require(users.first)\n```\n\n### Summary\n\n1. **Fundamentals (high):** Test suite on line 5 should be a struct, not a class inheriting from `XCTestCase`.\n2. **Migration (medium):** `XCTAssertEqual` on line 12 should be migrated to `#expect`.\n3. **Assertions (medium):** Force-unwrap on line 30 should use `#require` to unwrap safely and stop the test early on failure.\n\nEnd of example.\n\n\n## References\n\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fcore-rules.md` - core Swift Testing rules: structs over classes, `init`\u002F`deinit` over setUp\u002FtearDown, parallel execution, parameterized tests, `withKnownIssue`, and tags.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fwriting-better-tests.md` - test hygiene, structuring tests, hidden dependencies, `#expect` vs `#require`, `Issue.record()`, `#expect(throws:)`, and verification methods.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fasync-tests.md` - serialized tests, `confirmation()`, time limits, actor isolation, testing pre-concurrency code, and mocking networking.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fnew-features.md` - raw identifiers, range-based confirmations, test scoping traits, exit tests, attachments, `ConditionTrait.evaluate()`, and the updated `#expect(throws:)` return value.\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fmigrating-from-xctest.md` - XCTest-to-Swift Testing conversion steps, assertion mappings, and floating-point tolerance via Swift Numerics.\n",{"name":5,"license":15,"metadata":24,"description":7,"argument-hint":27},{"author":25,"version":26},"Paul Hudson","1.0","[focus area]","main","46b2e9493d75c07ea357cf5ac24ec104afb55500","shared\u002Fskills\u002Fswift-testing-pro\u002Fskills\u002Fswift-testing-pro","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench","https:\u002F\u002Fgithub.com\u002Fguhans6","2026-10-11 17:12:57",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add guhans6\u002Fagent-workbench --skill swift-testing-pro",{"tool":40,"command":41},"bunx","bunx skills add guhans6\u002Fagent-workbench --skill swift-testing-pro",{"tool":43,"command":44},"pnpm","pnpm dlx skills add guhans6\u002Fagent-workbench --skill swift-testing-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswift-testing-pro\u002Fskills\u002Fswift-testing-pro\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fasync-tests.md","REFERENCE","参考文档",8535,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswift-testing-pro\u002Fskills\u002Fswift-testing-pro\u002Freferences\u002Fasync-tests.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcore-rules.md",4032,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswift-testing-pro\u002Fskills\u002Fswift-testing-pro\u002Freferences\u002Fcore-rules.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fmigrating-from-xctest.md",2072,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswift-testing-pro\u002Fskills\u002Fswift-testing-pro\u002Freferences\u002Fmigrating-from-xctest.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fnew-features.md",10202,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswift-testing-pro\u002Fskills\u002Fswift-testing-pro\u002Freferences\u002Fnew-features.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fwriting-better-tests.md",11008,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswift-testing-pro\u002Fskills\u002Fswift-testing-pro\u002Freferences\u002Fwriting-better-tests.md",[71,80,88,96,104,111],{"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":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M72BDFZ4DSFCX7RHGN6NTMMB","winui-app","Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M72BD9EFCTBR28FEBJQQRVS8","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M72BD5GWQYR251PE9T29GXFR","transcribe","Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio\u002Fvideo, extract text from recordings, or label speakers in interviews or meetings.","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Ftranscribe\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Ftranscribe\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M72BD2GFD6AS2J1J24940AN4","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fto-tickets\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M72BCN5R8AD3FQKFXRXKETJC","swiftui-pro","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\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswiftui-pro\u002Fskills\u002Fswiftui-pro\u002FSKILL.md",[],[],{"skillNo":112,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M72BCJXF6ZWD25F8FGASNSAK","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswiftui-pro\u002FSKILL.md",[],[]]