Makepad Evolution

Self-improving skill system for Makepad development that learns from your work.

Key Features

• Self-Evolution: Accumulate knowledge from discoveries
• Self-Correction: Automatically fix skill errors
• Self-Validation: Verify skill accuracy against reality
• Usage Feedback: Track pattern health and effectiveness
• Version Adaptation: Multi-branch support for different Makepad versions
• Personalization: Adapt to project-specific style

When to Evolve

Trigger skill evolution when any of these occur:

Evolution Process

1. Capture the Learning

When you discover something new:

User: "I found a better way to handle async state loading"
Assistant: "Let me capture this pattern for makepad-patterns skill."

[Document the pattern with:]
- Problem it solves
- Code example
- When to use it
- Trade-offs

2. Verify Against Reality

Check if the pattern works:

• Test in real project
• Verify it compiles
• Confirm it solves the problem
• Check performance impact

3. Integrate into Skill

Update the relevant skill file with:

• New pattern documentation
• Code examples
• Usage guidelines
• Related patterns

Self-Correction

When a skill contains incorrect information:

1. Detect - Notice the error during development
2. Verify - Confirm against official docs or working code
3. Fix - Update the skill with correct information
4. Annotate - Mark what was wrong and why

Usage Feedback

Track which patterns are most useful:

Version Adaptation

Support multiple Makepad versions:

// Makepad rik branch (current)
makepad-widgets = { git = "https://github.com/makepad/makepad", branch = "rik" }

// Makepad main branch (stable)
makepad-widgets = { git = "https://github.com/makepad/makepad", branch = "main" }

Skills can include version-specific notes:

• [rik] - Available only in rik branch
• [main] - Available in stable main branch
• [v0.4+] - Available from version 0.4 onwards

Contribution Guidelines

When contributing new patterns:

1. Test thoroughly - Works in real projects
2. Document clearly - Problem, solution, trade-offs
3. Provide examples - Complete, runnable code
4. Cite sources - Link to reference implementations
5. Follow structure - Match existing skill format

Quality Checklist

Before adding to skills:

• Pattern solves a real problem
• Code example compiles and runs
• Tested in production-like scenario
• Documented trade-offs and limitations
• Follows Makepad best practices
• Includes links to references

Evolution Metrics

Track skill improvement over time:

• Coverage: Percentage of Makepad features documented
• Accuracy: Percentage of patterns that work first try
• Usefulness: Patterns used in actual development
• Freshness: Time since last update

Resources

• Makepad Repository
• Robrix - Pattern source
• Moly - Pattern source

Related: Agent Messaging Skill and Agent Ops Incident Notifier. Hub: skills.