lib-slint-expert_skill

This skill helps you develop and optimize GUI applications with Slint and Rust by guiding component design, layouts, styling, and cross-platform deployment.
  • Python

10

GitHub Stars

5

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill bahayonghang/my-claude-code-settings --skill lib-slint-expert

  • DOC.md13.6 KB
  • GETTING_STARTED.md7.3 KB
  • README.md8.4 KB
  • SKILL.md21.5 KB
  • SOURCE_STRUCTURE.md4.9 KB

Overview

This skill is a comprehensive Slint GUI development expert derived from the official Slint source material. It guides Rust integration, component design, layouts, styling, animations, cross-platform deployment, and performance optimization for native and embedded UIs. Use it to accelerate building maintainable, high-performance Slint applications.

How this skill works

The skill inspects Slint UI patterns and idioms and translates them into practical recipes for component architecture, data binding, and Rust interop. It explains layout systems (VerticalLayout, GridLayout, ListView), styling and theme switching, property animations, and platform-specific build configurations. It also gives concrete optimization tactics for memory, rendering, and efficient data models.

When to use it

  • Starting a new Slint + Rust native GUI project or porting an existing UI
  • Designing reusable Slint component libraries and app-wide themes
  • Implementing data binding and Rust-side models for dynamic lists
  • Optimizing rendering and memory usage for desktop, WASM, or embedded targets
  • Configuring cross-platform builds and platform-specific styles

Best practices

  • Keep components small, focused, and configurable via properties
  • Prefer composition over inheritance and expose callbacks for interactions
  • Use ModelRc/VecModel for large or dynamic lists to avoid full redraws
  • Use weak references for Rust callbacks to prevent circular ownership
  • Limit simultaneous animations and use clip: true for complex shapes
  • Organize UI files under ui/components and keep Rust models separate

Example use cases

  • Create a themed dashboard with GridLayout for metrics and ListView for activity feeds
  • Build a reusable component library: PrimaryButton, Card, LoadingSpinner
  • Integrate Rust-side VecModel to add/remove list items from native code
  • Target web via WASM with a platform-aware build.rs and minimal CSS reset
  • Deploy to embedded displays using the software renderer and an explicit repaint loop

FAQ

Expose a callback in the Slint component, set up the callback from Rust, and capture a weak reference to the window to avoid circular references.

When should I use ListView vs a for-loop layout?

Use ListView for large or dynamic datasets for virtualization and better performance; use for-loop layout for small, static sets.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
lib-slint-expert skill by bahayonghang/my-claude-code-settings | VeilStrat