メニュー
Use when working with the Racket backend, adding or modifying RPC methods, or understanding the Racket-Swift communication layer. Covers define-rpc, Backend.swift codegen, and the Noise RPC framework.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Prepare a release by bumping the build number, collecting user-facing changes into a changelog, and committing the result.
Use after making changes to visually validate the app in the iOS Simulator. Builds, installs, launches the app, then uses screenshots and accessibility descriptions to verify the change looks and behaves correctly.
Use when building, testing, or linting the Ruckus iOS app, regenerating the Tuist project, running tests, or adding new Swift files. Covers xcodebuild, tuist, make, swiftlint, and test workflows.
| name | ruckus-core |
| description | Use when working with the Racket backend, adding or modifying RPC methods, or understanding the Racket-Swift communication layer. Covers define-rpc, Backend.swift codegen, and the Noise RPC framework. |
| user-invocable | false |
Racket handles business logic; Swift/SwiftUI provides the iOS UI layer. They communicate via the Noise RPC framework.
RPC methods are defined in ruckus-core/main.rkt using define-rpc.
The Makefile runs noise-serde-codegen to auto-generate
Ruckus/Backend.swift with corresponding async Swift methods. Do not
edit Backend.swift manually — it is regenerated from Racket source.
Flow: ruckus-core/*.rkt → make → Backend.swift
(auto-generated) + res/core.zo (bytecode)
(define-rpc (name : ReturnType) body) in ruckus-core/main.rktmake to regenerate Backend.swift and recompile bytecodeBackend.shared.name() from Swiftexample.rkt, not examples.rkt).ruckus-core/main.rkt — Racket backend: RPC definitions and server entry point