Eval strategy for this skill
This skill ships with:
evals/evals.jsonfor output-quality checksevals/trigger-train.jsonfor description tuningevals/trigger-validation.jsonfor held-out trigger validationevals/rubric.mdfor human or LLM review
How to iterate
- Run the trigger sets multiple times and compute trigger rates.
- Improve the
descriptionusing only failures from the train split. - Re-check on the validation split.
- Run the output-quality evals with and without the skill (or against the previous skill version).
- Use the rubric to compare visual polish, architecture choice, and performance reasoning, not just syntax.
What this skill should outperform
A strong run should consistently:
- choose retained mode,
Picture,Atlas, or shader approaches for the right reasons - keep Reanimated state on the UI thread
- avoid
createAnimatedComponent/useAnimatedPropsaround Skia nodes - remember web bootstrap and snapshot caveats
- address reduced motion for decorative or always-on motion
- produce visually directed output rather than generic examples
High-value failure patterns to watch
- returns valid Skia code but with no aesthetic concept
- uses the wrong render mode for the workload
- animates via React state or JS-thread churn
- forgets
GestureHandlerRootVieworLoadSkiaWeb - uses generic text nodes when
Paragraphis clearly the right API - answers "performance" questions without talking about render mode or workload shape