Makepad Skills Evolution workflow skill. Use this skill when the user needs This skill enables makepad-skills to self-improve continuously during development and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
evolution
description
Makepad Skills Evolution workflow skill. Use this skill when the user needs This skill enables makepad-skills to self-improve continuously during development and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/evolution from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
# Makepad Skills Evolution This skill enables makepad-skills to self-improve continuously during development.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Quick Navigation, Skill Routing and Bundling, Pattern N: [Pattern Name], Self-Correction, Self-Validation, Validation Report.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
You are maintaining makepad-skills and want the skill library to improve itself during development.
You need the workflow for deciding when a new pattern should become a skill update or hook-driven evolution.
You are working on self-correction, self-validation, or version adaptation for the skill set.
Hook - Trigger Event - Action
makepad-skill-router.sh - UserPromptSubmit - Auto-route to relevant skills
pre-tool.sh - Before Bash/Write/Edit - Detect Makepad version from Cargo.toml
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Is this a reusable pattern? (not project-specific)
Did it take significant effort to figure out?
Would it help other Makepad developers?
Is it not already documented in makepad-skills?
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Imported Workflow Notes
Imported: Evolution Process
Step 1: Identify Knowledge Worth Capturing
Ask yourself:
Is this a reusable pattern? (not project-specific)
#### Imported: Quick Navigation
| Topic | Description |
|-------|-------------|
| Collaboration Guidelines | **Contributing to makepad-skills** |
| [Hooks Setup](#hooks-based-auto-triggering) | Auto-trigger evolution with hooks |
| [When to Evolve](#when-to-evolve) | Triggers and classification |
| [Evolution Process](#evolution-process) | Step-by-step guide |
| [Self-Correction](#self-correction) | Auto-fix skill errors |
| [Self-Validation](#self-validation) | Verify skill accuracy |
| [Version Adaptation](#version-adaptation) | Multi-branch support |
---
## Examples### Example 1: Ask for the upstream workflow directly```text
Use @evolution to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @evolution against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @evolution for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @evolution using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Generic, reusable patterns
Common errors with clear solutions
Well-tested shader effects
Platform-specific gotchas
Performance optimizations
Project-specific code
Unverified solutions
Imported Operating Notes
Imported: Quality Guidelines
DO Add
Generic, reusable patterns
Common errors with clear solutions
Well-tested shader effects
Platform-specific gotchas
Performance optimizations
DON'T Add
Project-specific code
Unverified solutions
Duplicate content
Incomplete examples
Personal preferences without rationale
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/evolution, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
**For Troubleshooting**:
```markdown
### [Error Type/Message]
**Symptom**: What the developer sees
**Cause**: Why this happens
**Solution**:
```rust
// Fixed code
### Step 4: Mark Evolution (NOT Version)
Add an evolution marker above new content:
```markdown
<!-- Evolution: 2024-01-15 | source: my-app | author: @zhangsan -->
Step 5: Submit via Git
# Create branch for your contribution
git checkout -b evolution/add-loading-pattern
# Commit your changes
git add robius-widget-patterns/_base/my-pattern.md
git commit -m "evolution: add loading state pattern from my-app"# Push and create PR
git push origin evolution/add-loading-pattern
Imported: Self-Correction
When skill content causes errors, automatically correct it.
Trigger Conditions
User follows skill advice → Code fails to compile/run → Claude identifies skill was wrong
↓
AUTO: Correct skill immediately
Correction Flow
Detect - Skill advice led to an error
Verify - Confirm the skill content is wrong
Correct - Update the skill file with fix
Correction Marker Format
<!-- Correction: YYYY-MM-DD | was: [old advice] | reason: [why it was wrong] -->
Imported: Self-Validation
Periodically verify skill content is still accurate.
Validation Checklist
#### Imported: Validation Report### Code Examples- [ ] All `live_design!` examples parse correctly
- [ ] All Rust code compiles
- [ ] All patterns work as documented
### API Accuracy- [ ] Widget names exist in makepad-widgets
- [ ] Method signatures are correct
- [ ] Event types are accurate
Validation Prompt
"Please validate makepad-skills against current Makepad version"
Imported: Version Adaptation
Provide version-specific guidance for different Makepad branches.
Supported Versions
Branch
Status
Notes
main
Stable
Production ready
dev
Active
Latest features, may break
rik
Legacy
Older API style
Version Detection
Claude should detect Makepad version from:
Cargo.toml branch reference:
makepad-widgets = { git = "...", branch = "dev" }
Cargo.lock content
Ask user if unclear
Imported: Personalization
Adapt skill suggestions to project's coding style.
