gpui-test
About
The gpui-test skill helps developers write tests for GPUI applications, particularly for components, async operations, and UI behavior. It provides a testing framework with deterministic execution and supports both basic tests using `TestAppContext` and window-dependent tests with `VisualTestContext`. Use the `#[gpui::test]` attribute for GPUI-specific tests, opting for simple Rust tests when windows or rendering aren't required.
Quick Install
Claude Code
Recommendednpx skills add longbridge/gpui-component -a claude-code/plugin add https://github.com/longbridge/gpui-componentgit clone https://github.com/longbridge/gpui-component.git ~/.claude/skills/gpui-testCopy and paste this command in Claude Code to install this skill
GitHub Repository
Related Skills
evaluating-llms-harness
TestingThis Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.
cloudflare-cron-triggers
TestingThis skill provides comprehensive knowledge for implementing Cloudflare Cron Triggers to schedule Workers using cron expressions. It covers setting up periodic tasks, maintenance jobs, and automated workflows while handling common issues like invalid cron expressions and timezone problems. Developers can use it for configuring scheduled handlers, testing cron triggers, and integrating with Workflows and Green Compute.
webapp-testing
TestingThis Claude Skill provides a Playwright-based toolkit for testing local web applications through Python scripts. It enables frontend verification, UI debugging, screenshot capture, and log viewing while managing server lifecycles. Use it for browser automation tasks but run scripts directly rather than reading their source code to avoid context pollution.
finishing-a-development-branch
TestingThis skill helps developers complete finished work by verifying tests pass and then presenting structured integration options. It guides the workflow for merging, creating PRs, or cleaning up branches after implementation is done. Use it when your code is ready and tested to systematically finalize the development process.
