Start a fresh conversation. Replace the highlighted placeholders.
Use makepad-skills to create a Rust Makepad UI implementation for [screen or interaction], using appropriate Makepad patterns, and provide the resulting code plus any setup or packaging steps needed to run it.
Required inputs
[screen or interaction]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: makepad-skillsdescription: "Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting."risk: safesource: "https://github.com/ZhangHanDong/makepad-skills"date_added: "2026-02-27"
Makepad Skills
Overview
Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.
When to Use This Skill
Use this skill when you need to work with makepad ui development skills for rust apps: setup, patterns, shaders, packaging, and troubleshooting..
Procedure
This entrypoint is a directory guide, not the full upstream Rust UI library.
Identify the target platform, Rust toolchain, installed Makepad revision and desired
UI behavior. Prefer the specific installed AAS skill (makepad-basics,
makepad-widgets, or makepad-deployment) matching the task after verifying it is
available. Inspect actual project manifests and compile the smallest affected
example before broad integration; do not assume upstream APIs match the installed
version. For shader/layout issues, inspect actual rendered output when available.
Packaging, signing, device deployment and provider downloads require their own scope.
Return changed paths, actual build results and unverified platform behavior.
Example
User request:
Use @makepad-skills for this task: Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.