Antigravity-awesome-skills makepad-reference

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

install
source · Clone the upstream repo
git clone https://github.com/sickn33/antigravity-awesome-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sickn33/antigravity-awesome-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/antigravity-awesome-skills/skills/makepad-reference" ~/.claude/skills/sickn33-antigravity-awesome-skills-makepad-reference-2eef22 && rm -rf "$T"
manifest: plugins/antigravity-awesome-skills/skills/makepad-reference/SKILL.md
source content

Makepad Reference

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

When to Use

  • You need quick-reference material for common Makepad errors, debugging, or API lookups.
  • The task is diagnostic or reference-oriented rather than writing a focused feature in one subsystem.
  • You want a central starting point before diving into more specialized Makepad skills.

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: font
Use
text_style: <THEME_FONT_*>{}
Color parse error (ends in
e
)
Change last digit (e.g.,
#14141e
#14141f
)
set_text
missing argument
Add
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

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.