lib-slint-expert
Execute the Slint GUI development task described in $ARGUMENTS.
Steps
- If
$ARGUMENTSis empty, report an error requesting a description of the GUI component or application. - Read
$SKILL_DIR/references/SLINT_GUIDE.mdfor core concepts, layout systems, styling, and animations. - If the user wants to start a new project, use the templates from
$SKILL_DIR/templates/. - For additional API details or usage patterns, consult
$SKILL_DIR/docs/README.mdor$SKILL_DIR/examples/README.md. - Implement the required UI components and associated Rust logic based on the user's prompt.
- Verify the UI handles cross-platform requirements if specified.
Examples
User Request: "Create a simple login form with Slint." Response Strategy: Generate a .slint file using VerticalLayout, TextInput for username and password, and a Button for submit. Include property bindings for the fields.
Troubleshooting
- If a component fails to render, verify that the bindings between Rust ModelRc and Slint properties are correctly set up.
More from bahayonghang/my-claude-code-settings
tech-design-doc
Generate technical design documents with proper structure, diagrams, and implementation details. Use when designing a new feature, documenting architecture decisions, or planning refactoring work. Default language is English.
106bidwriter
智能标书编写专家，专精工程咨询、建筑设计、市政工程领域的投标文件编写。
70article-cover
Generate article cover images as SVG. Use when creating cover/banner/header graphics for blogs, documentation, social media cards, or OG images. Trigger this skill whenever the user mentions article covers, blog banners, post thumbnails, social sharing images, or any visual header for written content — even if they don't explicitly say 'SVG'. Do not use it for full-scene illustrations, photo editing, or slide theme work.
63tech-blog
Write technical blog posts with source code analysis OR doc-driven research. Use when user wants to explain system internals, architecture, implementation details, or technical concepts with citations.
53git-commit-cn
Safely orchestrate Chinese Conventional Commits for staged Git changes, or for all working-tree changes when the user explicitly asks to include everything. Use when the user asks to write a commit message, split staged changes, split all changes, commit everything regardless of stage state, include untracked files in the commit set, organize a messy index before committing, prepare a Chinese commit, draft a Conventional Commit, or generate structured commit text without pushing by default.
47gemini-image
>-
46