{"summary":"Linear부터 Spring까지, 자주 쓰는 일곱 가지 애니메이션 속도 곡선이 각각 어떤 동작에 맞는지 다룹니다.","notes":"<p>애니메이션의 리듬은 속도 곡선으로 나타냅니다. 곡선이 가파를수록 속도 변화가 크고 더 빨라 보입니다. 메뉴가 나타나고, 대화상자가 닫히고, 표시 막대가 미끄러지는 동작에 모두 기본값 <code>ease</code>를 쓰면, 사용자는 요소가 나타나는지, 사라지는지, 자리를 옮기는지 구분할 수 없습니다. 자주 쓰는 곡선은 다음과 같습니다.</p>\n        <ol>\n        <li><strong>Linear</strong>: 진행 막대나 로딩처럼 그냥 ‘돌아가고 있는’ 것으로 보이는 것에 씁니다. 일정한 속도로 움직이며 시작과 끝이 모두 딱딱합니다. <code>linear</code>.</li>\n        <li><strong>Ease-out과 Strong ease-out</strong>: Toast, 메뉴, 대화상자, 드로어처럼 떠 있는 요소와 모달 요소의 등장에는 빠르게 시작해 느려지는 Ease-out을 씁니다. <code>cubic-bezier(0, 0, .58, 1)</code>. 아이콘, 글자, 선택된 캡슐처럼 클릭 후 곧바로 자리를 잡는 작은 요소에는 시작이 더 빠르고 마무리가 더 긴 Strong ease-out을 씁니다. <code>cubic-bezier(.22, 1, .36, 1)</code>이며, 반응이 가장 즉각적으로 느껴집니다.</li>\n        <li><strong>Ease-in</strong>: 대화상자가 닫히거나 Toast가 사라지는 것처럼 요소의 퇴장에 씁니다. 느리게 시작해 빨라지며 깔끔하게 떠납니다. <code>cubic-bezier(.42, 0, 1, 1)</code>. 등장에는 쓰지 않습니다. 시작이 느려서 인터페이스 반응이 굼뜬 것처럼 보입니다.</li>\n        <li><strong>Ease-in-out</strong>: 탭 아래에서 미끄러지는 표시 막대, 캐러셀 넘기기, 목차의 부드러운 스크롤처럼 화면 안에서 자리를 옮기는 요소에 씁니다. 양 끝이 느리고 가운데가 가장 빠릅니다. <code>cubic-bezier(.42, 0, .58, 1)</code>.</li>\n        <li><strong>Overshoot</strong>: 체크, 좋아요, 배지 표시처럼 작고 경쾌한 확인에 씁니다. 끝점을 약 10% 지나쳤다가 돌아옵니다. <code>cubic-bezier(.34, 1.56, .64, 1)</code>. 큰 패널에는 쓰지 않습니다. 그러면 화면 전체가 흔들립니다.</li>\n        <li><strong>Spring</strong>: 드로어가 되튀는 동작, 당겨서 새로고침, 드래그 정렬 후 자리 잡기처럼 손을 뗀 뒤 제자리로 돌아가는 동작에 씁니다. 도착한 뒤 한두 번 살짝 흔들리다 멈춰서 Overshoot보다 실제 물체처럼 보입니다. 사용자가 손을 뗄 때 요소에는 이미 속도가 있고, 스프링은 그 속도를 이어받아 움직일 수 있습니다.</li>\n        </ol>\n        <p>또한 이 곡선들을 모션 토큰으로 정의하고 역할에 따라 쓰면, 제품 전체의 리듬을 일관되게 유지할 수 있습니다.</p>\n        <p>함께 제공하는 Prompt는 먼저 프로젝트의 모든 전환과 애니메이션을 나열하고, 아직 기본 ease를 쓰거나 등장에 ease-in을 쓴 곳과 각각 바꿀 곡선을 표시합니다. 그다음 모션 토큰을 추가하고 곡선과 시간을 하나씩 조정합니다.</p>","prompt":"Give the motion in my product the right easing curves, so things arrive, leave and move the way they should feel. Work inside my existing code and design system: keep what each animation does, how far it goes and what triggers it. Change how it moves over time, and its duration where that is off.\n\n0. Start from what exists\n- Find every transition and animation: CSS transitions and keyframes, animation libraries (Framer Motion, GSAP, the Web Animations API) and hand-written requestAnimationFrame loops. List each with its component, its trigger, its duration and its curve.\n- Flag the ones left on the CSS default `ease`, `linear` on something that moves, and `ease-in` on something that appears.\n\n1. The curves as tokens\nDefine them once, next to the other motion tokens, and use only these:\n- --ease-out: cubic-bezier(0, 0, .58, 1). Anything that enters: toasts, menus, popovers, dialogs, drawers.\n- --ease-out-strong: cubic-bezier(.22, 1, .36, 1). Small parts settling in right after a click: an icon, a label, a selected pill. It feels the most responsive.\n- --ease-in: cubic-bezier(.42, 0, 1, 1). Anything that leaves, and only that: a toast timing out, a dialog or drawer closing, a menu collapsing, a list item swiped away. It starts slow and leaves at full speed, so on an entrance it feels late and then stops with a bump.\n- --ease-in-out: cubic-bezier(.42, 0, .58, 1). Something that stays on screen and only changes place or size: the indicator under tabs or a segmented control, a carousel turning a page, items making room during a reorder, a sidebar resizing, smooth-scrolling to an anchor. Not for coming in: its slow start reads as lag.\n- --ease-overshoot: cubic-bezier(.34, 1.56, .64, 1). Runs about 10% past its place and comes back. Small, playful confirmations: a checkbox tick, a like, a badge count popping in, a switch knob settling. Never on a dialog, a drawer or anything larger than about 64px, and not on actions people repeat all day.\n- --ease-spring: linear(0, .32, .78, 1.04, 1.09, 1.06, 1.02, 1, .99, .99, 1). Things let go after a drag or a swipe, so they settle like an object: a bottom sheet snapping open or back, a card returning after a half swipe, pull-to-refresh springing back, a reordered item dropping into place. Prefer the animation library's own spring fed with the release velocity; use this token only where there is none, and fall back to --ease-out-strong where linear() is not supported.\n- linear: only for things that run rather than move: spinners, progress bars, marquees.\n- The CSS default `ease` is not a choice. Replace it wherever a curve was left unset.\n\n2. Durations\n- Small UI (toasts, tooltips, menus, checks): 150-250ms in, 120-200ms out. Exits are shorter than entrances.\n- Medium (dialogs, popovers with content, drawers): 250-350ms.\n- Large or full-screen (sheets, page transitions): 350-500ms. Longer feels slow.\n- Springs and overshoots: about 1.5x the plain duration, since the settle takes time.\n- Keep the durations as tokens beside the curves (--duration-sm, -md, -lg).\n\n3. Apply them by role\n- Entrances: ease-out, coming from where the thing belongs (a toast from the top edge, a menu from its trigger), over a short distance (8-24px), growing from 96% and fading in a little sooner than it moves. A light blur (about 8px) that clears as it lands is a nice touch on toasts.\n- Exits: ease-in, the same path reversed, and shorter.\n- Moves on screen: ease-in-out.\n- Parts inside something that has just appeared (its icon, its text, a count) may follow 100-200ms later on the strong ease-out, so it lands in steps rather than all at once.\n- Gestures: while the pointer or finger moves, follow it 1:1 with no easing. On release, finish on the spring, from the release velocity if the library allows.\n- Hover and press: 100-150ms ease-out. Never animate layout on hover.\n- Animate transform and opacity (filter sparingly), not top, left, width or height, which lay out and repaint every frame.\n\n4. Keep it consistent and accessible\n- One curve per role across the product. Don't tune each component by hand.\n- Respect prefers-reduced-motion: keep the opacity changes, drop movement and scale, and turn springs and overshoots into a plain 150ms fade.\n- Never make a user wait on an animation: nothing blocks input, and a new action interrupts the old animation from where it is.\n\n5. Deliver\n- First list every animation you found, its current curve and duration, and the role and curve you will give it.\n- Then add the tokens, switch each animation over, and list every file you touched.\n- Don't change what animates, how far it goes or what triggers it. If an animation has no clear role, ask me first.","skill":"/skills/kubai-easing-curves/SKILL.md","skillText":"# 按场景选择缓动曲线\n\n《999 个小技巧，让你 Vibe 的产品更有质感》第 011 期 · @kubai087\n\n在用户的项目里按下面的要求改造。要求以用户的口吻写成：文中的 I、me、my 指用户；写着要先问的地方，先停下来问用户再继续。\n\n## 改造要求\n\nGive the motion in my product the right easing curves, so things arrive, leave and move the way they should feel. Work inside my existing code and design system: keep what each animation does, how far it goes and what triggers it. Change how it moves over time, and its duration where that is off.\n\n0. Start from what exists\n- Find every transition and animation: CSS transitions and keyframes, animation libraries (Framer Motion, GSAP, the Web Animations API) and hand-written requestAnimationFrame loops. List each with its component, its trigger, its duration and its curve.\n- Flag the ones left on the CSS default `ease`, `linear` on something that moves, and `ease-in` on something that appears.\n\n1. The curves as tokens\nDefine them once, next to the other motion tokens, and use only these:\n- --ease-out: cubic-bezier(0, 0, .58, 1). Anything that enters: toasts, menus, popovers, dialogs, drawers.\n- --ease-out-strong: cubic-bezier(.22, 1, .36, 1). Small parts settling in right after a click: an icon, a label, a selected pill. It feels the most responsive.\n- --ease-in: cubic-bezier(.42, 0, 1, 1). Anything that leaves, and only that: a toast timing out, a dialog or drawer closing, a menu collapsing, a list item swiped away. It starts slow and leaves at full speed, so on an entrance it feels late and then stops with a bump.\n- --ease-in-out: cubic-bezier(.42, 0, .58, 1). Something that stays on screen and only changes place or size: the indicator under tabs or a segmented control, a carousel turning a page, items making room during a reorder, a sidebar resizing, smooth-scrolling to an anchor. Not for coming in: its slow start reads as lag.\n- --ease-overshoot: cubic-bezier(.34, 1.56, .64, 1). Runs about 10% past its place and comes back. Small, playful confirmations: a checkbox tick, a like, a badge count popping in, a switch knob settling. Never on a dialog, a drawer or anything larger than about 64px, and not on actions people repeat all day.\n- --ease-spring: linear(0, .32, .78, 1.04, 1.09, 1.06, 1.02, 1, .99, .99, 1). Things let go after a drag or a swipe, so they settle like an object: a bottom sheet snapping open or back, a card returning after a half swipe, pull-to-refresh springing back, a reordered item dropping into place. Prefer the animation library's own spring fed with the release velocity; use this token only where there is none, and fall back to --ease-out-strong where linear() is not supported.\n- linear: only for things that run rather than move: spinners, progress bars, marquees.\n- The CSS default `ease` is not a choice. Replace it wherever a curve was left unset.\n\n2. Durations\n- Small UI (toasts, tooltips, menus, checks): 150-250ms in, 120-200ms out. Exits are shorter than entrances.\n- Medium (dialogs, popovers with content, drawers): 250-350ms.\n- Large or full-screen (sheets, page transitions): 350-500ms. Longer feels slow.\n- Springs and overshoots: about 1.5x the plain duration, since the settle takes time.\n- Keep the durations as tokens beside the curves (--duration-sm, -md, -lg).\n\n3. Apply them by role\n- Entrances: ease-out, coming from where the thing belongs (a toast from the top edge, a menu from its trigger), over a short distance (8-24px), growing from 96% and fading in a little sooner than it moves. A light blur (about 8px) that clears as it lands is a nice touch on toasts.\n- Exits: ease-in, the same path reversed, and shorter.\n- Moves on screen: ease-in-out.\n- Parts inside something that has just appeared (its icon, its text, a count) may follow 100-200ms later on the strong ease-out, so it lands in steps rather than all at once.\n- Gestures: while the pointer or finger moves, follow it 1:1 with no easing. On release, finish on the spring, from the release velocity if the library allows.\n- Hover and press: 100-150ms ease-out. Never animate layout on hover.\n- Animate transform and opacity (filter sparingly), not top, left, width or height, which lay out and repaint every frame.\n\n4. Keep it consistent and accessible\n- One curve per role across the product. Don't tune each component by hand.\n- Respect prefers-reduced-motion: keep the opacity changes, drop movement and scale, and turn springs and overshoots into a plain 150ms fade.\n- Never make a user wait on an animation: nothing blocks input, and a new action interrupts the old animation from where it is.\n\n5. Deliver\n- First list every animation you found, its current curve and duration, and the role and curve you will give it.\n- Then add the tokens, switch each animation over, and list every file you touched.\n- Don't change what animates, how far it goes or what triggers it. If an animation has no clear role, ask me first.\n"}