Evolve Makepad Skills Autonomously

The skill enables makepad-skills to self-improve continuously during development. Reliable auto-triggering runs through four Claude Code hooks: makepad-skill-router.sh on UserPromptSubmit auto-routes to relevant skills, pre-tool.sh on Bash/Write/Edit detects the Makepad version from Cargo.toml, post-bash.sh detects Makepad errors after a failed Bash command and suggests fixes, and session-end.sh prompts to capture learnings when a session ends. The router loads skill bundles by detected context - a "build app" query loads basics/dsl/layout/widgets/event-action/app-architecture, a "ui design" query loads dsl/layout/widgets/animation/shaders, and "create widget" or "best practice" queries load their own bundles - with dependency rules like robius-widget-patterns auto-loading makepad-widgets/makepad-layout.

Install command, quoted verbatim from the source:

### Install makepad-skills with hooks enabled
tmpdir="$(mktemp -d)"
trap 'rm -rf "$tmpdir"' EXIT
curl -fsSLo "$tmpdir/makepad-skills-install.sh" https://raw.githubusercontent.com/ZhangHanDong/makepad-skills/main/install.sh
cat "$tmpdir/makepad-skills-install.sh"  # review the full installer before executing
bash "$tmpdir/makepad-skills-install.sh" --with-hooks

Evolution triggers when a new widget pattern, shader technique, or compilation-error fix is discovered (high priority), a layout or build/packaging solution is found (medium), or a project-structure insight or core-concept clarification emerges (low) - each routed to a specific target skill file. The five-step evolution process is: identify whether the knowledge is reusable and not already documented; classify it (widget pattern, shader, troubleshooting, layout, deployment, project structure, or core concept) into its target file; format the contribution using a pattern template (name, description, live_design! DSL block, Rust implementation) or a troubleshooting template (symptom, cause, solution); mark it with an <!-- Evolution: date | source | author --> comment; and submit via a evolution/* git branch, commit, and PR. Self-correction detects when skill advice caused a compile/run failure, verifies the skill content was actually wrong, and updates it with a <!-- Correction: date | was | reason --> marker. Self-validation periodically checks that live_design! examples parse, Rust code compiles, and widget names/method signatures/event types are accurate. Version adaptation tracks three Makepad branches (main stable, dev active/may break, rik legacy) detected from the Cargo.toml git branch reference or Cargo.lock, or by asking the user. Personalization adapts suggestions to the project's own naming convention, code organization, comment style, and widget complexity. Quality guidelines say to add generic reusable patterns, common errors with clear solutions, and platform gotchas, but never project-specific code, unverified solutions, or duplicate content. The skill library itself spans 16 core skills (basics, dsl, layout, widgets, event-action, animation, shaders, platform, font, splash, plus five robius-*/molykit skills) and 3 extended skills (shaders _base/community, deployment, reference).

Use it when maintaining makepad-skills and wanting the library to improve itself during development, when deciding whether a new pattern should become a skill update, or when working on self-correction, self-validation, or version adaptation for the skill set.

Input is a development session's discoveries (a new pattern, a fixed error, a build issue) or a triggering hook event. Output is an updated skill file - a new pattern entry, a troubleshooting fix, or a correction marker - committed via an evolution/* branch and PR.

Maintainers of the makepad-skills library who want the skill set to capture reusable patterns, fix its own wrong advice, and stay adapted to the Makepad branch in use, rather than going stale between manual updates.