explaingit

stevekwon211/slintcn

Analysis updated 2026-05-18

32SlintAudience · developerComplexity · 2/5LicenseSetup · easy

TLDR

A copy-paste component library that brings shadcn-style UI building blocks to native Slint desktop apps.

Mindmap

mindmap
  root((slintcn))
    What it does
      Copy paste UI components
      Theme tokens
      Block templates
    Tech stack
      Slint
      Rust
      TypeScript
    Use cases
      Native app UI
      Screen templates
      AI agent install via MCP
    Audience
      Slint developers
      Rust developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Add pre-built buttons, dialogs, tables, and other UI pieces to a native Slint desktop app.

USE CASE 2

Copy full screen templates like sign-in, dashboard, or settings pages into a project.

USE CASE 3

Customize component source files directly instead of fighting a theming API.

USE CASE 4

Let an AI coding agent install and inspect components through the included MCP server.

What is it built with?

SlintRustTypeScript

How do you get it running?

Difficulty · easy Time to first run · 5min

Install via the cargo or npm CLI, both write files directly into your Slint project.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

Slintcn is a component library for Slint, a toolkit for building native desktop applications. Rather than installing a package and styling it through a configuration API, slintcn follows the copy-paste ownership model: you run a command to add a component and the source files land in your project. From there you can change colors, adjust sizing, or modify behavior directly without working around a library's constraints. The library currently ships 56 UI components and 8 larger block templates. Components cover a broad range: basic buttons, inputs, cards, and badges, overlays like dialogs, sheets, and tooltips, selection controls like checkboxes, switches, tabs, and radio groups, navigation pieces like a sidebar, breadcrumb, pagination, and menubar, data display components like a sortable data table, calendar, and chart-adjacent progress and skeleton elements, and a small set of game HUD pieces including a hotbar, crosshair overlay, and compass strip. Block templates are for complete screen layouts. The eight available ones cover sign-in, login, pricing, dashboard, settings, team member management, a profile form, and a stats display with traffic bars. Installation uses either a cargo CLI or an npm CLI, and both install the same files from the same hosted registry. Running init sets up a theme token file, after that you add components by name. A lockfile tracks installed versions, and a diff command shows what changed in the registry since your install. The init command accepts a base color argument, with choices including neutral, zinc, slate, and stone. An MCP server is included for AI agent workflows. MCP-capable tools like Claude Desktop or Cursor can connect to it and use tools to list, inspect, and install components directly during a coding session. Documentation for each component is available as a hosted site with per-component pages and a live WASM preview.

Copy-paste prompts

Prompt 1
Walk me through installing slintcn into an existing Slint project using the npm CLI.
Prompt 2
Show me how to add the dialog and card components with slintcn.
Prompt 3
Explain how the init command and base color theming work in slintcn.
Prompt 4
How do I use the slintcn MCP server from Claude Desktop to install components?

Frequently asked questions

What is slintcn?

A copy-paste component library that brings shadcn-style UI building blocks to native Slint desktop apps.

What language is slintcn written in?

Mainly Slint. The stack also includes Slint, Rust, TypeScript.

What license does slintcn use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is slintcn to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is slintcn for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.