evolution

Capture and codify reusable Makepad learnings with evolution markers and contribution templates.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/RoooyHe/betula --skill evolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolution
Source: https://github.com/RoooyHe/betula/tree/main/.claude/skills/evolution
Command: npx skills add https://github.com/RoooyHe/betula --skill evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables Makepad-skills to self-improve and contribute improvements during development, ensuring patterns, hooks, and guidance stay current with evolving Makepad workflows.

Core Features & Use Cases

  • Self-improvement workflow: automatically captures learnings from sessions and evolves skills.
  • Structured contribution: guides evolution with templates, markers, and a reviewer-friendly workflow.
  • Collaboration and reuse: surfaces knowledge across teams and projects for reuse.

Quick Start

Example: evolve evolution to add a new widget-pattern to robius-widget-patterns/_base/.

Frequently Asked Questions about evolution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture and reuse Makepad widget patterns across different projects?

To capture Makepad widget patterns across projects, the evolution skill automatically codifies reusable learnings from development sessions and enforces contribution templates with author and source metadata. This structured workflow ensures patterns are surfaced for team collaboration and project reuse.

How does the self-improvement workflow for Makepad skills operate?

The self-improvement workflow operates by automatically capturing learnings from active development sessions and applying evolution markers to codify them. It continuously updates Makepad skills with new hooks automation and widget patterns to keep guidance current across projects.

What is the best way to structure Makepad contributions for reviewer-friendly submission?

The best way to structure Makepad contributions is by using enforced evolution markers and contribution templates. This guides users through a structured submission workflow, ensuring author and source metadata are properly attached for reviewers to validate reused knowledge.

Do I need specific templates to evolve Makepad skills with new hooks automation?

Yes, you need specific contribution templates and evolution markers to evolve Makepad skills with new hooks automation. These structures ensure the captured knowledge is properly codified with author and source metadata before being submitted through the workflow.

Can I use this skill to update Makepad documentation contributions across development sessions?

Yes, you can use this skill to update Makepad documentation contributions across development sessions. It automatically captures learnings and applies evolution markers to keep documentation current with evolving Makepad workflows for reuse across teams.

Why does Makepad knowledge capture require structured metadata and markers?

Makepad knowledge capture requires structured metadata and markers to effectively codify learnings for self-improvement and cross-project reuse. Enforcing contribution templates with author and source metadata ensures the knowledge remains organized and accessible to teams.