

Also from Kynth Studios


Also from Kynth Studios
Use this agent when working with Swift code in any context—whether building iOS/macOS/watchOS/tvOS apps, server-side Swift projects, or Swift libraries.…
Works
40% of the score94/100
Maintained
25% of the score94/100
Adopted
20% of the score4/100
Documented
15% of the score81/100
| Finding | What it means |
|---|---|
| Long description | The description runs past the practical length ceiling and may be truncated. |
| No license | The repository ships no license file, so the reuse terms are unclear. |
Use this agent when working with Swift code in any context—whether building iOS/macOS/watchOS/tvOS apps, server-side Swift projects, or Swift libraries. Invoke this agent for:\n\n- **Implementation work** - New features, refactoring, bug fixes in Swift codebases\n- **Quality assurance** - Code review, testing (Swift Testing or XCTest), SwiftLint/SwiftFormat compliance, dependency security audits\n- **Architecture decisions** - Choosing between value/reference types, protocol-oriented design, composition strategies, async/await patterns\n- **Documentation sync** - Ensuring DocC catalogs and markdown docs reflect current implementation\n- **Testing strategy** - Writing behaviour-focused tests, creating test doubles, async test patterns\n- **Build and dependency management** - Working with SwiftPM, Package.swift, modularization, dependency updates\n- **Final review** - Before committing, ensuring all quality gates pass (tests, linting, formatting, security)\n\n**Examples of when to use:**\n\n<example>\nContext: User is building a new feature for their iOS app and has just written the business logic.\nuser: "I've implemented the order processing logic in OrderProcessor.swift. Here's the code..."\nassistant: "Let me use the swift-craftsperson agent to review this implementation for Swift idioms, test coverage, and adherence to functional core principles."\n<commentary>\nSince the user has completed implementation work in Swift, delegate to swift-craftsperson to ensure the code follows value type patterns, is properly tested with Swift Testing, and separates pure logic from I/O.\n</commentary>\n</example>\n\n<example>\nContext: User wants to add a new dependency to their Swift package.\nuser: "I need to add Alamofire for networking in my SwiftPM package"\nassistant: "I'm going to use the swift-craftsperson agent to help you add this dependency correctly and review security implications."\n<commentary>\nSwiftPM dependency management requires expertise in Package.swift structure and understanding security implications. The swift-craftsperson will ensure the dependency is added correctly, suggest protocol-based abstractions for the networking layer, and run appropriate security checks.\n</commentary>\n</example>\n\n<example>\nContext: Agent should proactively review Swift code quality during development.\nuser: "Please implement a function to validate email addresses"\nassistant: "Here's an email validation function using Swift's regex capabilities..."\n<function implementation omitted>\nassistant: "Now let me use the swift-craftsperson agent to review this implementation for Swift best practices and add comprehensive tests."\n<commentary>\nEven though the user didn't explicitly request review, the swift-craftsperson should proactively ensure the code follows Simple Design Heuristics, has Swift Testing coverage, and uses idiomatic Swift patterns.\n</commentary>\n</example>\n\n<example>\nContext: User is refactoring existing code to improve testability.\nuser: "This view model has too many dependencies and is hard to test"\nassistant: "Let me use the swift-craftsperson agent to refactor this following functional core/imperative shell principles."\n<commentary>\nRefactoring for testability requires deep understanding of Swift composition patterns, protocol-oriented design, and separation of pure logic from side effects. The swift-craftsperson will guide this architectural improvement.\n</commentary>\n</example>
| Artifact | Score | What the check found | Type | Reach | Last commit |
|---|---|---|---|---|---|
| presentation-image-generatorsvetzal/guidelines | 78 | No license | Skill | 1 stars | 2 days ago |
| slidev-presentationsvetzal/guidelines | 78 | No license | Skill | 1 stars | 2 days ago |
| cli-uxsvetzal/guidelines | 77 | No license | Skill | 1 stars | yesterday |
| typescript-craftspersonsvetzal/guidelines | 76 | No license | Subagent | 1 stars | 2 days ago |
| uvsvetzal/guidelines | 75 | No license | Skill | 1 stars | 2 days ago |
| elixir-phoenix-craftspersonsvetzal/guidelines | 74 | Long description | Subagent | 1 stars | yesterday |
| Artifact | Score | What the check found | Category | Reach | Last commit |
|---|---|---|---|---|---|
| kotlin-revieweraffaan-m/ECC | 92 | clean | Mobile | 242k stars | today |
| swift-build-resolveraffaan-m/ECC | 92 | clean | Mobile | 242k stars | today |
| kotlin-build-resolveraffaan-m/ECC | 91 | clean | Mobile | 242k stars | today |
| swift-revieweraffaan-m/ECC | 91 | clean | Mobile | 242k stars | today |
| gem-designer-mobilegithub/awesome-copilot | 89 | clean | Mobile | 38k stars | today |
| gem-implementer-mobilegithub/awesome-copilot | 89 | clean | Mobile | 38k stars | today |
A badge carrying how many listings this index holds from the repository and how many pass every static structural check. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.
[](https://skillworks.kynth.studio/?q=svetzal%2Fguidelines)Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:
Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.


Also from Kynth Studios