菜单
iOS build, test, and debugging workflows for the Llamenos project. Covers SSH to Mac M4, xcodebuild commands, simulator selection, XCFramework rebuilds, and UniFFI binding sync. Use when building iOS, running XCUITests, debugging crypto FFI issues, or troubleshooting Xcode/SPM problems.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when adding encryption for a new data type, implementing envelope encryption, working with HPKE key wrapping, managing crypto labels, or handling multi-recipient decryption. Also use when the user mentions "encrypt", "E2EE", "envelope", "HPKE", "forward secrecy", "crypto label", "admin envelope", "content key", or needs to understand how data is encrypted at rest.
Guide JSON Schema and protocol changes through the multi-platform codegen pipeline in the Llamenos monorepo. Use this skill when modifying files in packages/protocol/schemas/, changing crypto-labels.json, updating wire formats, adding new message types, or when the user mentions "schema change", "protocol update", "codegen", "wire format", "new message type", "crypto label", "domain separation", "add a field", "new field", "envelope format", or "shared types". Also use when the user describes adding or modifying data structures that need to work across all platforms (desktop, iOS, Android, worker) — this implies a protocol change. If a change touches encrypted payload formats or cross-platform type definitions, this skill applies. Schema changes have blast radius across every platform — this skill ensures nothing is missed.
Process security audit findings into dependency-ordered implementation epics for the Llamenos monorepo. Use this skill when conducting a security audit, reviewing security findings, processing vulnerability reports, creating security fix epics, or when the user mentions "security audit", "vulnerability", "findings", "security review", "pen test results", "audit round", "security issue", "security bug", "exploit", "insecure", "hardening", or "timing-unsafe". Also use when the user describes specific security problems inline — like missing auth checks, unsafe crypto operations, or data exposure — even without using the word "audit" or "vulnerability". If the user pastes or describes 2+ security issues that need triage and remediation, this skill applies. Covers all platforms: Worker backend, desktop (Tauri), iOS (SwiftUI), Android (Kotlin/Compose), crypto (Rust), CI/CD, and infrastructure.
Guide BDD test writing for the Llamenos monorepo. Use this skill when writing Gherkin feature files, creating backend or desktop step definitions, debugging test failures, or when the user mentions "BDD", "feature file", "Gherkin", "step definition", "backend BDD", "test:backend:bdd", "behavioral test", "write tests first", "add test coverage", "tests broke", "fix tests", or "E2E testing". This skill supplements superpowers brainstorming and plan execution — it does not replace them. Use it for BDD-specific implementation detail, not as a workflow entry point.
Guide porting features across Desktop (Tauri/React), iOS (SwiftUI), and Android (Kotlin/Compose) in the Llamenos monorepo. Use this skill when implementing a feature that exists on one platform and needs to work on another, when the user mentions "port to iOS", "Android version", "feature parity", "cross-platform", "implement on all platforms", "build the iOS/Android/mobile version", "same thing on Swift/Kotlin/native side", or describes a feature that "doesn't exist on [platform] yet". Also use when the user says "the desktop version works, now build it for mobile", asks to "replicate" or "mirror" a feature across platforms, or when creating epics for mobile feature parity. If a user describes building a screen or feature and mentions a specific target platform while referencing an existing implementation on another platform, this skill applies. It ensures consistent architecture, shared types, proper crypto integration, and correct i18n string handling on each platform.
Use when deploying the application, bumping versions, cutting releases, configuring CI/CD, managing Docker/Helm/Ansible deployments, or troubleshooting deployment issues. Also use when the user mentions "deploy", "release", "version bump", "Docker Compose", "Helm", "CI/CD", "wrangler", or needs to understand the deployment topology and release process.
| name | ios-debug |
| description | iOS build, test, and debugging workflows for the Llamenos project. Covers SSH to Mac M4, xcodebuild commands, simulator selection, XCFramework rebuilds, and UniFFI binding sync. Use when building iOS, running XCUITests, debugging crypto FFI issues, or troubleshooting Xcode/SPM problems. |
| user-invocable | false |
Host alias: ssh mac
Hardware: Mac mini M4, macOS 15.x, Xcode 16+
iOS Simulator runtime: iOS 17+ — available: iPhone 15 series, iPhone 16 series, iPad Pro/Air/mini
Worktree path: ~/.worktrees/<branch-name> (NOT ~/projects/llamenos/.worktrees/)
Always init PATH for non-login SSH shells:
ssh mac 'eval "$(/opt/homebrew/bin/brew shellenv)" 2>/dev/null; export PATH="$HOME/.asdf/shims:$HOME/.asdf/bin:$PATH"; <your-command>'
Or use the helper from the project root:
bun run mac:run "<command>"
~/projects/llamenos/~/.worktrees/<branch>/apps/ios/Sources/apps/ios/LlamenosCoreFFI.xcframework/apps/ios/Sources/Generated/LlamenosCore.swiftWhen reading iOS files on mac from Linux:
ssh mac "cat ~/.worktrees/<branch>/apps/ios/Sources/..."
NEVER use swift build — UIKit unavailable on macOS for iOS-only packages.
# Build iOS app (requires xcodegen first)
bun run ios:build
# Full: xcframework + build + unit tests + UI tests
bun run ios:all
# Individual steps
bun run ios:xcframework # Rebuild Rust XCFramework
bun run ios:test # Unit tests (LlamenosTests)
bun run ios:uitest # XCUITests on simulator
bun run ios:status # Check Xcode/Rust/xcodegen status
# Build for simulator (SPM scheme)
ssh mac "cd ~/projects/llamenos && eval \"\$(/opt/homebrew/bin/brew shellenv)\" && xcodebuild build -scheme Llamenos-Package -destination 'platform=iOS Simulator,name=iPhone 16'"
# Run unit tests
ssh mac "cd ~/projects/llamenos && eval \"\$(/opt/homebrew/bin/brew shellenv)\" && xcodebuild test -scheme Llamenos-Package -destination 'platform=iOS Simulator,name=iPhone 16'"
# List available simulators (when device not found)
ssh mac "xcrun simctl list devices available"
# Must run before xcodebuild when project.yml changes or new files added
ssh mac "cd ~/projects/llamenos/apps/ios && xcodegen generate"
SPM scheme naming: SPM generates Llamenos-Package (not just Llamenos)
When Rust crypto changes (new functions, signatures):
# 1. Build XCFramework from Rust (on mac)
ssh mac "cd ~/projects/llamenos/packages/crypto && ./scripts/build-mobile.sh ios"
# 2. Copy to iOS app (on mac — paths are relative to project)
# The build script handles copying; verify with:
ssh mac "ls ~/projects/llamenos/apps/ios/LlamenosCoreFFI.xcframework/"
# 3. Copy updated UniFFI bindings
ssh mac "cp ~/projects/llamenos/packages/crypto/dist/ios/LlamenosCore.swift ~/projects/llamenos/apps/ios/Sources/Generated/LlamenosCore.swift"
CRITICAL: LlamenosCore.swift bindings MUST match the XCFramework version. Mismatch causes a UniFFI checksum crash at runtime.
-34018 Keychain error in testsExpected — missing entitlement in SPM test runner. Keychain tests always fail in xcodebuild test (SPM context). Use the .xcodeproj via xcodegen for full XCUITest runs.
@Observable + Mirror reflection doesn't workSwift @Observable macro rewrites stored properties as private. Mirror cannot access them by name. Use known keys + direct FFI calls in tests instead.
EXCLUDED_ARCHS for simulatorXCFramework only has arm64 slices. Always set:
EXCLUDED_ARCHS[sdk=iphonesimulator*] = x86_64
(already in xcconfig — check if missing after xcodegen regeneration)
Use iPhone 15 or iPhone 16 — Xcode 16+ has these models available.
xcrun simctl list devices available | grep -E "iPhone (15|16)" | head -1 | awk -F'[()]' '{print $2}'
Test files using UserDefaults, URL, or Date must have:
import Foundation
SPM doesn't auto-import it for test targets.