rivetkit-client-swiftui
rivetkit client swiftui
What it does
- Prefer fail-fast behavior by default.
- Avoid broad do/catch unless absolutely needed.
- If a catch block is used, handle the error explicitly, at minimum by logging it.
- name (required)
- key as String or [String] (required)
- params (optional connection parameters)
- createWithInput (optional creation input)
Requirements & configuration
- params: ConnParams(authToken: "jwt-token"),
- config: try! ClientConfig(endpoint: "https://api.rivet.dev", token: "pk...")
- RIVETTOKEN - Authentication token (can also be in endpoint URL)
- https://namespace:token@api.rivet.dev
- Need More Than the Client?
Configuration: RIVET_NAMESPACERIVET_TOKENRIVET_RUNNER
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
rivetkit-client-swiftui FAQ
What does the rivetkit-client-swiftui skill do?
RivetKit SwiftUI client guidance. Use for SwiftUI apps that connect to Rivet Actors with RivetKitSwiftUI, @Actor, rivetKit view modifiers, and SwiftUI bindings. Prefer fail-fast behavior by default. Avoid broad do/catch unless absolutely needed.
What does rivetkit-client-swiftui require?
params: ConnParams(authToken: "jwt-token"), config: try! ClientConfig(endpoint: "https://api.rivet.dev", token: "pk...") RIVETTOKEN - Authentication token (can also be in endpoint URL) https://namespace:token@api.rivet.dev Need More Than the Client? Configuration keys: RIVET_NAMESPACE, RIVET_TOKEN, RIVET_RUNNER.
How do I install rivetkit-client-swiftui?
Run: npx -y skills add https://github.com/rivet-dev/skills --skill rivetkit-client-swiftui --agent claude-code — the source lives at github.com/rivet-dev/skills.
Maintain rivetkit-client-swiftui?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/rivet-dev-skills-rivetkit-client-swiftui?ref=badge) npx agentictools info skills/rivet-dev-skills-rivetkit-client-swiftui The second line is the CLI lookup for this page — handy in READMEs and docs.
