Communitygithub.com

1999AZZAR/designer-mcp

当没有专门的工作流适用,或 BRIEF.md 中 flow 设置为 companion 时,使用此技能创作或编辑自定义 HyperFrames 合成。适用于较长或多场景作品、品牌宣传片、精彩集锦、蒙太奇、静态循环、静态标题卡片、素材混剪以及自由格式构建。对于简短、无旁白的动态优先单元(包括动画标题),请改用 motion-graphics 技能。在使用此技能之前,通过 hyperframes 路由新的创作。

designer-mcp 是什么?

这是一款面向视频和动态图形创作者的 HyperFrames AI Agent 技能(设计为 MCP 工具),适用于无专用工作流适配的通用视频合成任务。它支持多场景作品、品牌片、混剪、静态卡片等,要求流类型为 companion(协作)或 automation(自动化)。其工作流程包括:首先通过 cross-cutting 适配器处理媒体素材(音频、图像、图标等)和 Figma 链接;然后根据项目状态(如 Brief、JSON 或全新创建)确定起始点;接着解读流模式(自动化/协作)和分镜需求;在执行合成前,必须加载多个知识库(如 HyperFrames Core、Creative、Animation、Media-use 等)以确保规则一致性;最后按计划、依赖解析、布局、预览和渲染的顺序执行。技能强调质量天花板设计(在 companion 流中提供最高水平的创意方案),并禁止使用未经授权的手写效果。

兼容平台~Claude Code✓Codex CLI~Cursor
npx skills add https://github.com/1999AZZAR/designer-mcp/tree/HEAD/skills/video/engine/general-video

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

通用视频

在依赖此工作流之前,请运行:

npx hyperframes skills update general-video

若输出 no-op 表示技能已是最新。如有更新失败,请提示用户,不要依赖记忆继续。

1. 应用跨领域源适配器

  • 媒体: 对于任何音频、图像、图标、标识、语音、调色、LUT、处理/效果、字幕或媒体操作需求,请加载 /media-use 并遵循 ../media-use/references/resolve.md(解析、采用、复用)和 ../media-use/references/setup-providers.md(提供商、认证)。对于模糊的素材反馈和命名样式,在编辑前先使用 ../media-use/references/media-treatments.md;不要用 CSS/SVG/透明度即兴实现支持的媒体效果。在首次执行认证的提供商操作之前,运行 npx hyperframes auth status 并逐字输出其结果。如果已登出,请应用 ../hyperframes/references/brief-contract.md 中的门控:协作模式等待登录或明确的离线选择;自主模式说明状态并通过可用的离线提供商继续。当没有离线提供商能满足所需能力时,显示阻塞。仅本地采用不需要认证门控。
  • Figma: 如果任何输入是 figma.com URL,请先运行 /figma。基于其导出的资源、令牌、组件或分镜帧进行构建。不要直接使用 Figma 连接器调用,因为它们会跳过 SVG 清理、媒体来源溯源和品牌令牌绑定。

这些适配器不会更改 /hyperframes 选定的工作流。

2. 从项目状态开始

应用第一个匹配的行;不要评估更低的状态行:

状态操作
特定编辑进行编辑,保留现有项目决策,然后重新运行受影响的检查。不要重新打开探索阶段。
BRIEF.md 存在读取它。如果 workflow 命名了另一个工作流且 flow 不是 companion,则移交。不要询问任何 Brief 问题。
无 Brief,但存在 hyperframes.json 或 STORYBOARD.md从文件和记录的偏好中恢复。仅从已知事实回填 BRIEF.md。
全新创作运行 /hyperframes 及其意图层。仅当 workflow: general-video 或 flow: companion 时返回此处。

对于新项目,从 Brief 中选择一个 kebab-case 目录名称,在编写 Brief 之前构建脚手架:

npx hyperframes init "videos/<project>" --non-interactive --example=blank --skill=general-video

然后在项目根目录使用 ../hyperframes/references/brief-format.md 编写 BRIEF.md。在已有项目中,根目录是包含 hyperframes.json 的目录。仅使用 node <MEDIA_DIR>/scripts/prefs.mjs record --hyperframes <PROJECT_ROOT> 记录 Brief 格式确认的、基于偏好的字段;绝不记录推断的默认值。这里的 <MEDIA_DIR> 是安装的 /media-use 技能目录,<PROJECT_ROOT> 是包含 hyperframes.json 的目录。如果意图层采用了配方,立即使用 node <MEDIA_DIR>/scripts/recipe.mjs use --hyperframes <PROJECT_ROOT> --name <name> 应用它,并且不要再次询问。

3. 解读运行形态

仅使用来自 ../hyperframes/references/brief-contract.md 的规范术语:

字段含义效果
flow谁来驱动automation:选择并执行路线。 companion:在对话中共同创作。
storyboard在构建前进行规划、草稿和评审yes:运行规划和草稿评审(storyboard.html)。 no:直接构建,无需此步骤。
派生的 mode检查点门控如何运行遵循 Brief 契约。永远不要让用户命名模式。

不要为这些状态发明同义词。持续的“只管构建”信号由意图层处理,并作为 flow: automation、storyboard: no 到达。

  • 对于 flow: automation,选择路线并在第一次进度更新中用一行说明。
  • 对于特定编辑,直接进行编辑,不要发明新路线。

对于现有素材的硬切、修剪、拼接或重新排序,将相同的视频源复制到多个剪辑元素。在每个副本上,使用 data-media-start 加 data-duration 设置源范围,然后使用 data-start 设置创作的放置/顺序。单独创作的音频遵循相同的剪辑范围和时间,放在匹配的 <audio> 元素上。/hyperframes-core 拥有此时间编辑;仅对视觉属性动画(如缩放、强调、平移、裁剪、遮罩或内部包装器上的 clip-path)使用 /hyperframes-keyframes。从 ../hyperframes-core/references/creator-editing-recipes.md 复制完整的契约。

协作流

当 flow: companion 时:

  • 读取 BRIEF.md 并将已接受的 ## Assets 和 ## Customizations 与项目工件进行核对。完成仍然待处理的已接受工作;已完成的留待不动;不要将已接受的能力再次作为新内容提供。
  • 以导演的身份到达,而不是承包商。 选择协作的用户选择了参与和质量;诚实的回应是你所能设计的最佳版本,而不是你能辩解的最小版本。第一个计划是天花板处理:故事弧(借用最近的体裁镜头 —— 菜单 § 体裁镜头)、设计规格、每个场景的动画处理按名称引用(第 5 节的计划纪律)、过渡、音频身份 —— 音乐和声音标记,或故意的沉默 —— 用户素材的放置,以及设计好的开场和结尾。用一句话说明每个图层增加了什么;在命名时标记成本高昂的(渲染时间、登录、计费)。用户会削减处理方案;他们绝不应该通过一次次批准来拼凑一个方案。
  • 天花板属于概念,而不是工具箱。 每个图层都必须服务于 Brief 的信息 —— 任何视频都用相同方式装饰的处理方案只是装饰。工艺通向天花板;内容绝不会超出所要求的内容(第 6 节)。
  • 在检查点之间,../hyperframes/references/capability-menu.md 具有双重作用。作为触发器列表:当用户提到其输入或构建到达其需求时,提供相关能力。作为每次迭代的升级渠道:计划、草稿或构建检查点可以携带一两个指向用户正在查看的素材的定向提议(“场景 3 的统计数据需要计数处理”)。在提供之前阅读它;绝不要倾倒完整目录。
  • 用户接受能力后,立即生成其工件并将决策记录到匹配的 BRIEF.md 正文部分。仅当用户明确更改时,才重写前置字段并记录确认的偏好。
  • 保持相同的分镜、验证、最终预览和渲染审批门控。协作改变的是谁来引导,而不是什么质量要求。

4. 在每个阶段前加载所需知识

这些读取在其条件匹配时是强制性的:

条件在行动前读取
任何合成 HTML 或场景布局/hyperframes-core;使用 references/determinism-rules.md 获取其布局契约
任何非平凡的创作或视觉处理/hyperframes-creative → references/house-style.md 和 references/video-composition.md
任何动画、动作或场景过渡/hyperframes-animation;按照其路由到匹配的规则、适配器、蓝图或过渡参考资料
storyboard: yes../hyperframes/references/storyboard-format.md 和 ../hyperframes/references/review-loop.md
任何媒体资源或操作,包括旁白、BGM、SFX、字幕、调色或变换/media-use;对于框架回放和放置,还需要读取 /hyperframes-core → references/variables-and-media.md
多场景组装../hyperframes/references/production-loop.md
flow: companion,在第一个计划之前/hyperframes-creative → references/story-spine.md 和 references/house-style.md;最近的体裁镜头和完整的 ../hyperframes/references/capability-menu.md —— 天花板处理基于这些设计,而非回忆
协作能力提供、捕获、节奏网格、生成视频、地图、发布或跨工作流能力../hyperframes/references/capability-menu.md
存在设计规格,在最终审批前/hyperframes-creative → references/design-adherence.md

不要用回忆替代这些读取。渐进式披露仅在实际加载了匹配的参考资料时才节省上下文。

5. 执行合成

使用此依赖顺序。仅当阶段输入缺失时跳过。

  1. 计划。 说明观众弧线、结构、节奏和时长驱动因素。对于短单场景使用一个文件;对于三个或更多硬场景切或任何复用场景使用子合成。读取 /hyperframes-creative → references/story-spine.md 了解叙述弧,references/beat-direction.md 了解节奏,以及 /hyperframes-core → references/composition-patterns.md 了解结构。对于开放式的多场景 Brief,通过 /hyperframes-creative → references/prompt-expansion.md 扩展提示。多场景计划引用每个场景的形态:一个来自 /hyperframes-animation → blueprints-index.md 的蓝图 ID(当适合时),或当无蓝图适合时,引用它组合的命名规则(来自 rules-index.md)—— 动作名称来自这些索引,绝不自创。故事真相决定哪些场景存在;引用为它们提供装饰。在你计划自己构建任何命名外观之前,搜索实时目录:对于 Brief 中命名的每个外观、效果、处理或过渡 —— “CRT 扫描线”、“故障”、“胶片颗粒”、“闪光扫掠”、“五彩纸屑爆发” —— 运行 npx hyperframes catalog --query "<外观,用简单英文描述>" --json 并在计划命名如何构建该外观之前阅读顶部结果。该搜索不需要任何安装:没有项目、没有先前的 add、没有账户。它从任何目录对整个托管注册表(约 400 个块和组件)进行排名,因此也适用于用户在中途构建时要求的外观。计划命名的块在阶段 3 安装;仅当搜索后没有找到适合的内容时,才手写外观。多场景计划也被记录为调度工件:在 STORYBOARD.md 中每个场景一个 ## Frame N 块 —— status: outline、声明的 src:、蓝图/规则引用和节拍文本 —— 即使当 storyboard: no 时也是如此。该块是调度单元;分镜表只是评审界面。
  2. 在请求时评审计划。 对于 storyboard: yes,在这些块上运行共享评审循环。对于 storyboard: no,继续而不暂停计划或草图。当计划暂停无论如何发生时,将子代理委托授权(步骤 4 的调度需要 codex)折叠到该暂停中,而不是稍后再次停止。
  3. 解析依赖项。 在并行工作之前安装注册表块。暂存用户素材,采用现有

...

[为翻译截断]

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

1999AZZAR/designer-mcp

SOTA animation and physics heuristic guide using motion.dev

1999AZZAR/designer-mcp

Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet `anchor` rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.

1999AZZAR/designer-mcp

Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a website (/product-launch-video — promo or tour). Unclear → /hyperframes.

1999AZZAR/designer-mcp

Import Figma content into a HyperFrames composition — rendered assets, brand tokens, components, storyboard sections → reconstructed motion (frames read as states, not slides) (REST/CLI), connector-assisted motion when available, and shaders from a connector or native export. Use when the user pastes a figma.com link or asks to bring a Figma design, frame, logo, brand, or animation into a video/composition.

1999AZZAR/designer-mcp

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

1999AZZAR/designer-mcp

Use when audio already placed in a HyperFrames composition needs to be mixed: fade-in/fade-out, crossfade, track gain or volume, volume automation, ducking, a music bed that fights a voiceover (voiceover carve), effects on a track (EQ, compressor, limiter, gate, saturation, delay, reverb, chorus, phaser, bitcrush), automation envelopes drawn on a track's volume or any effect parameter, or one submix bus carrying a chain, a fader and an automation clock for several tracks at once (`<hf-audio-group>`). Don't use for sourcing or generating audio — finding BGM, SFX, or making a voiceover is `/media-use`. Don't use for clip timing or track layout, which is `/hyperframes-core`.

1999AZZAR/designer-mcp

Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, timeline, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local, HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.

1999AZZAR/designer-mcp

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

1999AZZAR/designer-mcp

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

1999AZZAR/designer-mcp

Use when a HyperFrames composition needs a punch-in, punch-out, zoom, reframe, Ken Burns treatment, camera move, visual match/whip handoff, or other seek-safe 2D/3D keyframes; also for GSAP, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

1999AZZAR/designer-mcp

Search, install, and wire registry blocks and components into HyperFrames compositions. Use BEFORE hand-building any named visual — whenever a brief, a user, or a storyboard names a look, effect, treatment, or transition such as CRT scanlines, glitch, chromatic aberration, film grain, a shimmer sweep, a chart, a code or terminal window, a map, or a confetti burst — because roughly 400 hosted items already cover many of them and the search ranks all of them with nothing installed, no project, and no account. Also use when running hyperframes add or hyperframes catalog, installing one item or every block matching a tag, wiring an installed item into index.html, or working with hyperframes.json. Covers discovery, install locations, block sub-composition wiring, component snippet merging, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).

1999AZZAR/designer-mcp

Mandatory entry point: read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic, including a promo, explainer, captioned clip, title card, overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing footage, or music. It resumes project state, captures intent when applicable, selects and installs the owning workflow, and routes domain capabilities. HyperFrames is the default output framework unless the user explicitly chooses another framework for the deliverable or asks only to record a browser session.

1999AZZAR/designer-mcp

Use when building or editing a HyperFrames project that people open in Studio: how the timeline should be laid out so it reads well (one caption track, one element kind per track, every scene a sub-composition) and where captions and key content may sit (safe zones). Don't use for how to perform an individual edit (split, trim, retime, volume, copy, swap): that is `creator-editing-recipes.md` in `/hyperframes-core`.

1999AZZAR/designer-mcp

Agent Media OS, the single skill for every media need in a HyperFrames project. Resolve BGM, SFX, image, icon, brand logo, voice, color grade, or LUT into a frozen local file or paste-ready block + ledger record (one verb, `resolve`); generate via TTS / music / image models when the catalog misses; produce voiceover, transcription, captions, and background removal through one shared audio engine; operate on media (cut / reframe / transform); and reuse assets across projects. Also use for vague feedback that real footage looks dark, flat, boring, should feel retro/camcorder/print/ASCII, needs privacy, or needs a media reveal.

1999AZZAR/designer-mcp

Turn a music track (an audio file, a video to pull audio from, or a track generated from a mood brief) into a beat-synced video — lyric video, slideshow, or kinetic promo. The music drives all pacing; any user-supplied images/videos are cut onto the same beat grid, and a complete video needs zero assets. Narrated pieces → the input-matched workflow (see /hyperframes). Unclear → /hyperframes.

1999AZZAR/designer-mcp

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

1999AZZAR/designer-mcp

Port an existing Remotion (React) composition''s source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing Remotion mention, reference-only code, or "make something like my Remotion video" is a fresh build (/general-video). Unclear → /hyperframes.

1999AZZAR/designer-mcp

Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't explicitly ask for a slideshow, confirm before authoring. Unclear → /hyperframes.

1999AZZAR/designer-mcp

Package an existing talking-head / interview / podcast video with timed, designed GRAPHIC OVERLAY cards — kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture — synced to the transcript, on a 16:9 / 9:16 / 4:5 canvas of your choice; the clip plays untouched underneath. Trigger on "graphic overlays", "on-screen graphics", "package / dress up my video". Not plain subtitles (/embedded-captions). Unclear → /hyperframes.

1999AZZAR/designer-mcp

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

相关技能