Agent skill
screenshot
Take a screenshot of the plugin UI using the standalone app CLI for debugging and documentation
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/screenshot-iplug2-iplug2
SKILL.md
Screenshot Plugin UI
Use this skill to capture screenshots of the plugin UI. This is useful for:
- Debugging UI design - Quickly verify control layouts, colors, and positioning without launching a DAW
- Documentation - Generate consistent screenshots for README files and wikis
- CI/CD pipelines - Automated visual regression testing or asset generation
Prerequisites
Build the standalone app (APP target) first:
cd [ProjectFolder]
xcodebuild -project "./projects/[ProjectName]-macOS.xcodeproj" -target APP -configuration Debug
The app will be built to ~/Applications/[PluginName].app
Take Screenshot
macOS
~/Applications/[PluginName].app/Contents/MacOS/[PluginName] --screenshot /path/to/output.png
Example
# Take screenshot of IPlugEffect
~/Applications/IPlugEffect.app/Contents/MacOS/IPlugEffect --screenshot ./screenshot.png
The app will:
- Launch and display the UI (audio/MIDI I/O is automatically disabled)
- Wait ~500ms for the UI to fully render
- Capture the window to a PNG file
- Exit automatically
Options
--screenshot <path>- Path to save the PNG screenshot (required)--no-io- Explicitly disable audio/MIDI (implicit when using --screenshot)
Tips
- Screenshots are high-DPI (Retina) resolution on supported displays
- The screenshot captures the plugin content area
- For iterative UI debugging, rebuild the APP target and re-run the screenshot command
- Combine with the
buildskill: build first, then screenshot
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?