بنقرة واحدة
visual-test
Visual Test - GPUI Terminal
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Visual Test - GPUI Terminal
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Development skill for Rust GUI applications using GPUI framework (Zed's UI framework). Use when working on GPUI-based desktop applications - creating views, managing state, handling actions, or reviewing/refactoring existing code. Triggers on Rust GUI development, GPUI views, Entity/Context usage, terminal emulators, code editors, or any desktop app built with GPUI.
Expert guidance for Axum 0.8.x web framework development in Rust. Use when working with Axum 0.8+, migrating from 0.7 to 0.8, or when users mention path parameter syntax issues, async_trait problems, or Option extractor changes.
Set up Tailwind v4 with shadcn/ui themed UI. Workflow: install dependencies, configure CSS variables with @theme inline, set up dark mode, verify. Use when initialising React projects with Tailwind v4, setting up shadcn/ui theming, or fixing colors not working, tw-animate-css errors, @theme inline dark mode conflicts, @apply breaking, v3 migration issues.
| name | visual-test |
| description | Visual Test - GPUI Terminal |
Automated visual regression testing for the GPUI terminal renderer. Builds the app, runs it headless with test patterns, captures a screenshot, and analyzes the rendering.
Must be in the nix dev shell (nix develop) which provides cage and grim.
Build the app:
cargo build -p zremote-gui
Run headless screenshot capture with the terminal test patterns script:
./scripts/headless-screenshot.sh \
"bash -c './scripts/terminal-test-patterns.sh; sleep 999'" \
/tmp/zremote-visual-test.png \
3
If the app needs a server connection, start the local agent first:
./scripts/headless-screenshot.sh \
"./target/debug/zremote-gui --exit-after 8" \
/tmp/zremote-visual-test.png \
5
Read and analyze the screenshot:
Use the Read tool on /tmp/zremote-visual-test.png to visually inspect the rendered terminal.
Check for rendering issues:
Report findings: List any rendering issues found with specific descriptions. If everything looks correct, confirm the visual test passes.
Run this after any changes to:
crates/zremote-gui/src/views/terminal_element.rs (rendering)crates/zremote-gui/src/views/terminal_panel.rs (state/layout)crates/zremote-gui/src/theme.rs (colors)