Use `fatalError` only for an unrecoverable programmer error or an invariant that should be unreachable, such as a required implementation that is intentionally absent. It is not appropriate for expected input, network, or user errors. ```swift func makeRequiredService() -> Service { fatalError("Service must be provided by dependency injection") } ``` Prefer typed `throws` for recoverable failures, and `precondition`, `assert`, or `assertionFailure` when expressing programmer assumptions. Keep...
Scanned 9/5/2026
Install to Claude Code
npx -y skills add HoangNguyen0403/agent-skills-standard --skill swift-error-handling --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Swift Error Handling?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-swift-error-handling-41e54104)More formats (shields.io, HTML) on the badges page.
Use `fatalError` only for an unrecoverable programmer error or an invariant that should be unreachable, such as a required implementation that is intentionally absent. It is not appropriate for expected input, network, or user errors.
```swift
func makeRequiredService() -> Service {
fatalError("Service must be provided by dependency injection")
}
```
Prefer typed `throws` for recoverable failures, and `precondition`, `assert`, or `assertionFailure` when expressing programmer assumptions. Keep `Never` for functions that cannot return, such as a deliberate fatal termination.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!