菜单
Use when Codex should validate chilla macOS desktop behavior, Tauri app launches, visible UI flows, or browser/app interactions after implementation or bug fixes, and Computer Use tools may be available.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run mixed Tauri Rust and TypeScript lint, typecheck, formatting, and verification commands. Use when Codex is asked to lint, check, test, verify, or prepare Rust/TypeScript/Tauri changes in this repository, especially after editing src-tauri, src, package.json, Taskfile.yml, flake.nix, or agent lint scripts.
Use when setting up or verifying Apple Developer ID signing credentials, Apple app-specific passwords, kinko secret storage, or local macOS notarization readiness for chilla without recording credential values.
Use when code changes in this repository should be validated by actually launching the local chilla app. After modifying runtime-affecting code, rebuild the debug app when needed and launch `target/debug/chilla` yourself instead of telling the user to run it.
Use when building, signing, notarizing, validating, or publishing macOS `.app` and `.dmg` release artifacts for this repository. Covers the Tauri macOS release config, local `task bundle-macos-dmg`, Apple signing/notarization inputs, GitHub Actions release workflow, and post-release tap follow-up.
Use when building and publishing the Nix tarball release artifacts for this repository with `nix build`. Covers flake target selection, tarball packaging, installer compatibility, GitHub release creation, and Homebrew tap updates for the current tarball-based cask path.
Use when writing, reviewing, or refactoring Rust code. Provides type safety patterns, error handling, project layout, and async programming guidelines.
| name | macos-computer-use-verify |
| description | Use when Codex should validate chilla macOS desktop behavior, Tauri app launches, visible UI flows, or browser/app interactions after implementation or bug fixes, and Computer Use tools may be available. |
| allowed-tools | Read, Grep, Bash |
Validate chilla behavior through the visible macOS UI when possible. Use this after changes that affect desktop app startup, PR diff rendering, file browsing, navigation, dialogs, or other runtime behavior that cannot be fully proven by build and unit tests.
Use Computer Use verification when all of these are true:
If Computer Use tools are unavailable, do not pretend UI verification happened. Run the strongest available non-UI checks and report that visible macOS verification was skipped because Computer Use was unavailable.
Prefer the Tauri debug app for fast local verification:
bun run tauri build --debug --bundles app
open -n /absolute/path/to/repo/target/debug/bundle/macos/chilla.app --args <args>
Use the exact app bundle path with Computer Use:
/absolute/path/to/repo/target/debug/bundle/macos/chilla.app
Use nix build only when the user explicitly asks to validate the Nix package output; it is slower and may omit untracked Git files unless built from a path source.
mcp__computer_use.get_app_state once before interacting with the app in each assistant turn.click for buttons, tabs, list items, menus, and controls.type_text or set_value for text fields.press_key for shortcuts and keyboard navigation.scroll for overflow content.A visible verification is credible only when Codex has observed the relevant UI state through Computer Use after the action.
For the PR diff viewer, verify:
Do not claim behavior was verified only because a process stayed alive, a build passed, or a log was empty.
Use concise reporting:
Visible verification: what was observed through Computer Use.Automated checks: commands that passed.Skipped/limited: any Computer Use limitation, inaccessible app, or unverified flow.