메뉴
Use the steve CLI to automate macOS apps via Accessibility APIs. Use when you need to drive Mac UI (apps, windows, menus, elements), run UI smoke tests, or script interactions using steve commands and JSON output. Never decide to use steve on your own. Only use when told to.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
User-owned external project notes in ~/.field_notes. Use when the user asks to check, search, read, save, append, update, or consult field notes; phrases include "check field notes", "look in field notes", "save to field notes", "what do field notes say", "what's next", progress notes, planning notes, external docs, cross-project memory, or docs that should live outside a repository.
Style review notes for UI/design work. Use when reviewing or implementing visual style, layout, components, typography, icons, cards, themes, or dark mode. Bias toward minimal, simple interfaces with a slight note of whimsy.
Control the user own Chrome browser via Playwriter extension with Playwright code snippets in a stateful local js sandbox. Use this over other Playwright MCPs to automate the browser — it connects to the user's existing Chrome instead of launching a new one. Use this cli for navigating JS-heavy websites (Instagram, Twitter, cookie/login walls, lazy-loaded UIs) instead of webfetch/curl. ALWAYS load this skill before using any playwriter commands
Open and drive Pi's HTML Super Review UI for uncommitted changes or git ranges. Use when the user asks for super-review, review current changes, review against master/origin, or read comments from the review UI.
Rebase a feature worktree on main/master, resolve conflicts, ff-only merge into the trunk worktree, then rebase feature on updated trunk.
Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.
| name | steve |
| description | Use the steve CLI to automate macOS apps via Accessibility APIs. Use when you need to drive Mac UI (apps, windows, menus, elements), run UI smoke tests, or script interactions using steve commands and JSON output. Never decide to use steve on your own. Only use when told to. |
Use the steve CLI to automate macOS applications through the Accessibility API. Prefer steve when you need deterministic, scriptable UI control with JSON responses.
PATH. If not, download it from the GitHub releases page: https://github.com/mikker/steve/releasessteve apps
Use --app, --bundle, or --pid to select the app, and --window to scope to a window title.
steve elements --app "System Settings" --window "Settings"
Use --text to match visible text via AXValue, AXDescription, or AXStaticText title (case-insensitive substring).
steve find --text "Dictation Mode" --window "Settings"
After a text match, use --ancestor-role and --click to press a nearby container row/cell/button.
steve find --text "Dictation Mode" --window "Settings" --ancestor-role AXRow --click
steve click --title "OK"
steve type "hello world"
steve key cmd+shift+p
steve menu "File" "New"
--window and --text over raw coordinates.wait for UI state changes before clicking:steve wait --title "Results" --timeout 5