Code style guide derived from gpui-component implementation patterns.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongpui-style-guideExecute the skills CLI command in your project's root directory to begin installation:
Fetches gpui-style-guide from longbridge/gpui-component and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate gpui-style-guide. Access via /gpui-style-guide in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
10.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
10.9K
stars
Code style guide derived from gpui-component implementation patterns.
Based on: Analysis of Button, Checkbox, Input, Select, and other components in crates/ui
use gpui::{
div, prelude::FluentBuilder as _, AnyElement, App, Div, ElementId,
InteractiveElement, IntoElement, ParentElement, RenderOnce,
StatefulInteractiveElement, StyleRefinement, Styled, Window,
};
#[derive(IntoElement)]
pub struct MyComponent {
id: ElementId,
base: Div,
style: StyleRefinement,
// Configuration fields
size: Size,
disabled: bool,
selected: bool,
// Content fields
label: Option<Text>,
children: Vec<AnyElement>,
// Callbacks (use Rc for Clone)
on_click: Option<Rc<dyn Fn(&ClickEvent, &mut Window, &mut App)>>,
}
impl MyComponent {
pub fn new(id: impl Into<ElementId>) -> Self {
Self {
id: id.into(),
base: div(),
style: StyleRefinement::default(),
size: Size::default(),
disabled: false,
selected: false,
label: None,
children: Vec::new(),
on_click: None,
}
}
// Builder methods
pub fn label(mut self, label: impl Into<Text>) -> Self {
self.label = Some(label.into());
self
}
pub fn on_click(mut self, handler: impl Fn(&ClickEvent, &mut Window, &mut App) + 'static) -> Self {
self.on_click = Some(Rc::new(handler));
self
}
}
impl InteractiveElement for MyComponent {
fn interactivity(&mut self) -> &mut gpui::Interactivity {
self.base.interactivity()
}
}
impl StatefulInteractiveElement for MyComponent {}
impl Styled for MyComponent {
fn style(&mut self) -> &mut StyleRefinement {
&mut self.style
}
}
impl RenderOnce for MyComponent {
fn render(self, window: &mut Window, cx: &mut App) -> impl IntoElement {
// Implementation
self.base
}
}
#[derive(IntoElement)]
pub struct Select {
state: Entity<SelectState>,
style: StyleRefinement,
size: Size,
// ...
}
pub struct SelectState {
open: bool,
selected_index: Option<usize>,
// ...
}
impl Select {
pub fn new(state: &Entity<SelectState>) -> Self {
Self {
state: state.clone(),
size: Size::default(),
style: StyleRefinement::default(),
}
}
}
impl Sizable for MyComponent {
fn with_size(mut self, size: impl Into<Size>) -> Self {
self.size = size.into();
self
}
}
impl Selectable for MyComponent {
fn selected(mut self, selected: bool) -> Self {
self.selected = selected;
self
}
fn is_selectedImplementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
frontend-design
633anthropics/claude-code
Frontendsame categoryui-animation
230mblode/agent-skills
Frontendsame categorypremium-frontend-ui
228github/awesome-copilot
Frontendsame categoryhigh-end-visual-design
183leonxlnx/taste-skill
Frontendsame categoryantigravity-design-expert
181sickn33/antigravity-awesome-skills
Frontendsame categoryinterior-design-expert
133erichowens/some_claude_skills
Frontendsame categoryReviews
4.8★★★★★55 reviews- PPratham Ware★★★★★Dec 28, 2024
gpui-style-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- EEvelyn Chawla★★★★★Dec 16, 2024
Solid pick for teams standardizing on skills: gpui-style-guide is focused, and the summary matches what you get after install.
- FFatima Li★★★★★Dec 4, 2024
I recommend gpui-style-guide for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- HHiroshi Flores★★★★★Dec 4, 2024
gpui-style-guide is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- FFatima Menon★★★★★Nov 23, 2024
Solid pick for teams standardizing on skills: gpui-style-guide is focused, and the summary matches what you get after install.
- HHiroshi Farah★★★★★Nov 23, 2024
gpui-style-guide reduced setup friction for our internal harness; good balance of opinion and flexibility.
- MMichael Thomas★★★★★Nov 7, 2024
I recommend gpui-style-guide for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- MMichael Li★★★★★Oct 26, 2024
Useful defaults in gpui-style-guide — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- NNoah Shah★★★★★Oct 14, 2024
gpui-style-guide has been reliable in day-to-day use. Documentation quality is above average for community skills.
- WWilliam Johnson★★★★★Oct 14, 2024
Registry listing for gpui-style-guide matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 55
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.