agentsclimarketplace

Makepad reference

Skill SageV1/makepad-skills/skills/makepad-reference

CRITICAL: Use for Makepad troubleshooting and reference. Triggers on: troubleshoot, error, debug, fix, problem, issue, no matching field, parse error, widget not found, UI not updating, code quality, refactor, responsive layout, adaptive, api docs, reference, documentation, 故障排除, 错误, 调试, 问题, 修复From its SKILL.md

Install
npx -y skills add SageV1/makepad-skills --skill makepad-reference

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 1 command, including `MAKEPAD=lines cargo +nightly run`.

SKILL.md

1.9 KB, 396 tokens by cl100k_base, as published. Nobody here has run it

Makepad Reference

This category provides reference materials for debugging, code quality, and advanced layout patterns.

Quick Navigation

TopicFileUse When
API DocumentationOfficial docs index, quick API referenceFinding detailed API info
TroubleshootingCommon errors and fixesBuild fails, runtime errors
Code QualityMakepad-aware refactoringSimplifying code safely
Adaptive LayoutDesktop/mobile responsiveCross-platform layouts

Common Issues Quick Reference

ErrorQuick Fix
no matching field: fontUse text_style: <THEME_FONT_*>{}
Color parse error (ends in e)Change last digit (e.g., #14141e → #14141f)
set_text missing argumentAdd cx as first argument
UI not updatingCall redraw(cx) after changes
Widget not foundCheck ID spelling, use ids!() for paths

Debug Tips

# Run with line info for better error messages
MAKEPAD=lines cargo +nightly run
// Add logging
log!("Value: {:?}", my_value);
log!("State: {} / {}", self.counter, self.is_loading);

Resources

What ships with it: 4 files

59.7 KB alongside SKILL.md

Gives 0 of the 12 instructions most docs writing skills give in 396 tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Use text_style for font fields
  • Change color hex codes ending in e
  • Add cx as first argument to set_text
  • Call redraw after UI changes
  • Check ID spelling for missing widgets
  • Run with line info for error messages

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.