skills.rest
zerx-lab
zerx-labCOMMUNITY
Explore all skills by this author →
GitHub

gpui-style-guide

Standardize GPUI component code patterns across projects.

62|1|Updated Feb 5, 2026
Search Tags:#rust#coding-standards#gpui#style-guide#component-patterns#gpui-component
One-click install
npx skills add https://github.com/zerx-lab/rmx --skill gpui-style-guide
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpui-style-guide
Source: https://github.com/zerx-lab/rmx/tree/main/.opencode/skills/gpui-style-guide
Command: npx skills add https://github.com/zerx-lab/rmx --skill gpui-style-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide standardizes GPUI component development by codifying structure, trait implementations, naming conventions, and API patterns observed in gpui-component codebases, helping teams maintain consistency across projects.

Core Features & Use Cases

  • Establishes a standardized component pattern including identity, configuration, content, and callbacks to align implementations across crates/ui.
  • Documents trait implementations and naming conventions to prevent drift and facilitate code reviews.
  • Use Case: When adding or reviewing a GPUI component, consult this guide to ensure alignment with existing patterns.

Quick Start

Follow these guidelines when scaffolding a new GPUI component, ensuring it derives IntoElement, follows the component documentation pattern, and adheres to theme usage and rendering patterns.

Frequently Asked Questions about gpui-style-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize GPUI component patterns across multiple Rust projects?▼

To standardize GPUI component patterns across Rust projects, apply a consistent style guide for component authoring that codifies identity, configuration, content, and callback structures. This prevents implementation drift and architectural misalignment across different crates.

What traits should a GPUI component implement for code review alignment?▼

A GPUI component should derive IntoElement and follow standardized trait patterns and naming conventions. Aligning with these documented trait implementations ensures that code reviews catch structural drift and maintain codebase consistency.

When do I need a style guide for gpui-component implementations?▼

You need a style guide for gpui-component implementations when your team is actively scaffolding new UI elements or reviewing code. It enforces rendering patterns and theme usage to maintain architectural alignment at scale.

How to scaffold a new GPUI component following coding standards?▼

To scaffold a new GPUI component following coding standards, ensure it derives IntoElement, adheres to established theme usage, and follows documented rendering patterns. This enforces structural consistency from the initial creation phase.

What is the best way to maintain consistency in Rust GPUI rendering patterns?▼

The best way to maintain consistency in Rust GPUI rendering patterns is to codify component documentation, trait implementations, and theme usage. This standardizes architectural alignment and prevents drift during component authoring and reviews.

Related Skills

Explore More Software Engineering Skills→
longbridgelongbridge
12.5k

new-component

Guides creation of new GPUI components using established Rust patterns.

Official
Intermediate
pradyumnasagarpradyumnasagar
6

release-management

Manages ORS skill releases with versioning, changelogs, and marketplace updates.

Community
Intermediate
longbridgelongbridge
12.5k

gpui-style-guide

Guide GPUI component structure, trait implementations, and naming conventions.

Official
Advanced
zerx-labzerx-lab
62

rust-coding-guidelines

Enforce Rust GPUI coding standards for error handling and naming conventions.

Community
Advanced