weasel-icons 0.14.0 → 0.14.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "weasel-icons",
-  "version": "0.14.0",
+  "version": "0.14.2",
   "description": "Stateful animated React SVG icons. Icons that overreact beautifully.",
   "license": "MIT",
   "author": "Vinod Murugan",

package/skill-data/customize/references/motion.md

@@ -2,6 +2,10 @@
 
 Inspect the actual SVG at 24 px and enlarged before choosing timing. Identify the silhouette, named parts, pivots, attached landmarks, rigid assemblies/free ends, paint roles and painted bounds. A 24-unit viewBox is not the contour's measured size.
 
+For a local expression or action, name what stays fixed on the relevant state edge. Open a mouth within the accepted face rather than enlarging the head just to fit a detail. Reuse identical geometry for invariant parts; an intentional transformation or requested squash can still change the silhouette.
+
+Within the approved style, distinguish structural outlines, solid main-ink regions and neutral cutouts. Small closed details do not all need an extra stroke. Keep cutouts inside their containing shape, attach their bases to its moving boundary and reveal them only when there is space. Preserve the copied renderer's supported paint roles and surface token; neutral fill is paint, not transparency. Do not restyle unrelated icons or copy another character's paint layout.
+
 Choose one leading action and necessary followers. A hinge turns at its hinge; a cut closes its blades; a transfer moves toward its destination. Anticipation, overshoot and repetition each need a reason. Don't copy another icon's choreography merely because its renderer is convenient.
 
 For each moving relationship, distinguish attached joins, intended occlusions and separate contours. Keep joined landmarks coincident. For separate paths, retain the sum of their painted half-strokes plus visible optical space at 24 px. Check each contour against itself: flattening a closed shape can create a knot within a valid viewBox. Inspect entry, closest approach, full cycle, reversal and simultaneous state blending. Fix travel/pivots rather than shrinking the whole icon or adding arbitrary patches to hide collisions.

package/skill-data/customize/references/review.md

@@ -6,6 +6,7 @@ For each changed state, record externally: intended fact → visible cue → obs
 - Helpfulness: does motion direct attention, confirm a choice or explain continuing work? Would a still convey the result better? Requested expression is valid, but don't present it as operation status.
 - Delivery: inspect the real component at 24 px and normal speed. Cover labels for a visual comparison, then restore actual host labels. They must not rescue contradictory motion.
 - Construction: inspect connected landmarks, intentional occlusions, separate painted contours and self-collisions through the tightest intermediate pose, full loop, reversal and rapid third-state interruption. Include actual spring blending and entry offsets. Bounds alone cannot prove clearance.
+- Invariants and paint: compare the actual stable contours through the agreed transition and reversal, starting from a settled relevant pose. Allow deliberate transformations on other edges. Inspect fill/outline density, cutout containment and joins at real sizes, custom colours and supported stroke weights. If changing a shared renderer, compare unaffected outlined, surface-filled and accented consumers.
 - Lifecycle: exercise mount directly into the new state, return to a legacy state, repeated state props, alive-off and reduced motion. Check 16/32 px, contrasting surface and supported maximum stroke when geometry is affected. Preserve persistent nodes and release resources on unmount.
 - Host: verify real pointer/keyboard triggers, disabled/current/pressed semantics as appropriate, and independent accessible names/status text. Pending remains pending until the actual operation resolves. Use isolated local fixtures for destructive or external operations; label simulations clearly.