Menu
Launch VivaDicta on a physical iOS device with print logging enabled for real-time console capture
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run an ASO audit on canonical App Store metadata under `./metadata`, then a krankie-based competitor keyword-gap analysis (no Astro subscription). Krankie replacement for asc-aso-audit. Use after `asc metadata pull`.
Pull VivaDicta App Store keyword rankings via krankie (free, self-hosted), compare against the previous check, and write a dated rankings report to the Obsidian vault. Krankie-based replacement for asc-aso-rankings (no Astro subscription required).
Prepare a new VivaDicta release — version bump, What's New screen, App Store metadata, code sweep, and pre-submission checklist
Measure VivaDicta test code coverage from the terminal. Use when asked what the test coverage is, a module's or the whole-app coverage %, which lines/files are covered, to get coverage without opening Xcode, or to see coverage after writing tests. Covers both the fast per-SPM-module path (swift test + llvm-cov) and the canonical whole-app path (xcodebuild + xccov), and which first-party targets count.
Count Swift lines of code across the VivaDicta codebase and refresh the production-vs-test history chart. Use when asked how many LOC / lines of code the project has, for a codebase-size or LOC breakdown by SPM module / main app / extension, how big a module or extension is, the prod-vs-test ratio, or to update / regenerate the LOC growth chart embedded in documentation/Module-Architecture.md.
Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.
| name | start-logs-device |
| description | Launch VivaDicta on a physical iOS device with print logging enabled for real-time console capture |
| disable-model-invocation | true |
Launch VivaDicta on a connected physical device with print logging enabled and keep the console capture running in a long-lived shell session.
mkdir -p logs
./scripts/launch_device.sh
logs/device-YYYYMMDD-HHMMSS.log.stop-logs-device skill when they want the newest file summarized../scripts/launch_device.sh uses xcrun devicectl device process launch --console.00008130-001250203C92001C.com.antonnovoselov.VivaDicta-beta.ENABLE_PRINT_LOGS=1 is set so mirrored print output is visible in the console stream.devicectl is available.