Token导航 LogoToken导航

Agent Skill · 前端设计

motion-and-storytelling(动作和讲故事)

motion-and-storytelling 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

motion-and-storytelling 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 5,261。

总安装 706周安装 30GitHub Stars 6下载 247核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:motion-and-storytelling(动作和讲故事)
来源仓库:https://github.com/dembrandt/dembrandt-skills
仓库路径:skills/motion-and-storytelling
安装命令:
npx skills add https://github.com/dembrandt/dembrandt-skills --skill motion-and-storytelling
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/dembrandt/dembrandt-skills --skill motion-and-storytelling

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合整理仓库状态与协作事项。适用于围绕代码变更、仓库维护或团队协作进行信息梳理的场景。通过 npx skills add 命令从 GitHub 仓库安装,需确认权限和维护状态。使用前建议核实是否会触发联网、命令执行或文件读写操作。

motion-and-storytelling 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/motion-and-storytelling

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/dembrandt/dembrandt-skills --skill motion-and-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

motion-and-storytelling 怎么安装?

在终端执行 npx skills add https://github.com/dembrandt/dembrandt-skills --skill motion-and-storytelli…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

motion-and-storytelling 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

motion-and-storytelling 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

motion-and-storytelling 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

motion-and-storytelling 用的人多吗?

公开数据是累计安装 706 次,近一周安装 30 次,下载 247 次,GitHub 6 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

motion-and-storytelling 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
motion-and-storytelling

动作和讲故事 · 本页

7066只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Motion and Storytelling in UI

Animation and motion are not decoration — they are communication. When applied with the same discipline as typography or colour, they tell the user what is happening, where to look, and what the product feels like to use. The source material — Disney's 12 principles, cinematic language, comic book conventions — is centuries of accumulated knowledge about how to communicate through movement and sequence.

The key word is subtlety. In UI, motion should be felt, not watched.


Disney's 12 Principles Applied to UI

1. Squash and Stretch

Objects compress on impact and extend on acceleration. In UI: a button that scales down slightly on press and springs back communicates physicality and responsiveness.

button:active { transform: scale(0.96); }
button { transition: transform 80ms ease-out; }

Use sparingly — reserved for primary CTAs and satisfying confirmations.

2. Anticipation

A small preparatory movement before the main action. In UI: a menu item shifting slightly before opening, or a loading indicator appearing before a transition begins, prepares the user for what is coming.

3. Staging

Present one idea clearly at a time. In UI: entrance animations should direct attention to the new content, not compete with existing content. When a modal opens, the rest of the page dims — that is staging.

4. Straight Ahead vs Pose to Pose

Pose to pose — defining start and end states and letting the system interpolate — is the CSS/JS approach. Define clear initial and final states; let transition or a spring physics library handle the in-between.

5. Follow-Through and Overlapping Action

Elements don't all stop at the same time. In UI: staggered list item entrances (each item enters 40–60ms after the previous) feel more natural than all items appearing simultaneously.

.item:nth-child(1) { animation-delay: 0ms; }
.item:nth-child(2) { animation-delay: 50ms; }
.item:nth-child(3) { animation-delay: 100ms; }

6. Ease In and Ease Out

Nothing in nature starts or stops instantly. Use easing curves, not linear transitions.

EasingUse for
ease-out (fast start, slow end)Elements entering the screen — feels natural arrival
ease-in (slow start, fast end)Elements leaving the screen — feels intentional exit
ease-in-outElements moving between positions on screen
Spring physicsInteractive elements that respond to touch/drag

Never use linear for UI motion — it reads as mechanical and unfinished.

7. Arcs

Natural movement follows arcs, not straight lines. Tooltips and popovers that scale from their origin point (rather than fading uniformly) follow this principle. transform-origin matters.

8. Secondary Action

A supporting motion that reinforces the main action. In UI: an icon inside a button that shifts slightly when the button is pressed. A checkmark that draws itself after a form submission. These details reward attention without demanding it.

9. Timing

Duration is meaning. Fast = responsive, energetic. Slow = weighty, important.

DurationUse for
80–120msMicro-interactions (button press, hover)
150–250msComponent transitions (dropdown open, tooltip)
250–400msPage-level transitions, modal entrance
400–600msHero animations, onboarding sequences
> 600msAlmost always too long — the user is waiting

10. Exaggeration

A small, deliberate overstatement makes an action feel satisfying. In UI: a success checkmark that overshoots slightly before settling, or a notification badge that pops just slightly larger than its final size. The exaggeration is 10–15%, not theatrical.

11. Solid Drawing (Solid Design)

Respect the 3D space of the interface. Elements should move in ways consistent with their perceived layer — a bottom sheet slides up from below because it lives below the content, not from the side. A tooltip appears near its trigger, not across the screen.

12. Appeal

The overall motion should feel right for the brand. A playful consumer app can use bouncier, springier motion. A financial tool uses precise, controlled transitions. Appeal is not decoration — it is brand personality expressed through time.


Cinematic Techniques

Reveal and Entrance

Content that enters the viewport has more impact when it arrives, rather than simply existing. Scroll-triggered entrance animations — a section fading up as the user scrolls into it — borrow from cinematic reveals. The key: the content drives in from a meaningful direction (below, because that's where the user is scrolling from).

@keyframes fade-up {
  from { opacity: 0; transform: translateY(24px); }
  to   { opacity: 1; transform: translateY(0); }
}

Parallax

Background elements moving slower than foreground elements creates depth. In web: a hero background image moving at 50% scroll speed while content moves at 100% creates a sense of layers. Use subtly — aggressive parallax causes motion sickness.

Cut vs Dissolve

  • Hard cut (instant state change): fast, decisive, efficient. Use for navigation between pages, closing modals.
  • Dissolve / crossfade: gradual, considered, connected. Use when two states are related — a tab switching, an image gallery transitioning.

Scene Setting

The first frame of a section sets the scene before detail appears. A hero with a strong image and large type, followed by supporting details appearing after a brief delay, is a cinematic opening. The user's eye is directed to the subject before reading begins.


Comic Book Conventions

Panel Sequence

Comics tell stories through a sequence of static frames that imply motion between them. In UI: step indicators, onboarding carousels, and progress flows use the same logic — each "panel" is a moment in a sequence, and the user's eye moves between them.

Speed Lines and Energy

Emphasis lines, radial gradients, and directional blur suggest motion and energy without actual animation. A button with a subtle directional gradient implies it is pointing somewhere. A loading indicator with trailing opacity implies direction.

Typography as Tone

In comics, the size, weight, and style of lettering communicates emotion — a shout is set in large bold caps, a whisper in thin small italics. In UI: oversized display type for a hero carries energy; small muted caption text recedes. This is micro-typography as emotional register, not just hierarchy.

The Gutter

In comics, the reader's imagination fills the space between panels. In UI, transitions are the gutter — what happens between states. A smooth transition lets the user's brain construct a coherent mental model. A jarring jump forces them to re-orient.


Practical Rules

  1. Respect prefers-reduced-motion — always. Users with vestibular disorders or motion sensitivity must be able to use the product without animation.
@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    transition-duration: 0.01ms !important;
  }
}
  1. Motion should serve the user, not entertain them. Every animation should answer: does this help the user understand what happened, where something came from, or where to look next?
  2. Duration under 400ms for almost everything. If an animation takes longer, it is slowing the user down.
  3. Never animate layout properties (width, height, padding, top, left) — they cause reflow. Animate transform and opacity only — they run on the GPU.
  4. One motion at a time per region. Simultaneous competing animations create visual noise. Stage them.

Review Checklist

  • Does prefers-reduced-motion disable or reduce all animations?
  • Are all transitions using ease-out (enter), ease-in (exit), or ease-in-out (reposition)?
  • Is linear easing avoided?
  • Are durations under 400ms for component-level transitions?
  • Are only transform and opacity animated (not layout properties)?
  • Do entrance animations move from a meaningful direction (bottom for scroll-reveal, origin for scale)?
  • Does motion match brand tone (bouncy for playful, precise for enterprise)?
  • Are staggered entrances used for list items rather than simultaneous appearance?

平台分布

Codex

33.15%
按下载量换算82

Claude

30.82%
按下载量换算76

Cursor

19%
按下载量换算47

Gemini CLI

10.24%
按下载量换算25

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills