Communitygithub.com

1999AZZAR/designer-mcp

當沒有專門的工作流程適用,或當 BRIEF.md 設定 flow: companion 時,用於創作或編輯自訂的 HyperFrames 合成作品。適用於較長或多場景作品、品牌與宣傳片、蒙太奇、靜態循環、靜態標題卡、素材重新混剪以及自由形式建構。對於簡短、無旁白、以動畫為主的單元(包含動畫標題),請改用 motion-graphics。在從 hyperframes 路由建立全新創作後,再使用此技能。

designer-mcp 是什麼?

此技能提供一個結構化、基於工作流程的方法,用於在 HyperFrames 生態系統中創作和編輯影片,遵循嚴格的規則以確保一致性、品質和可重複性。它專為需要較長或多場景合成、品牌宣傳片或自由形式建構的專案而設計。技能強制執行階段性流程:先執行強制性技能更新和跨領域適配器(如媒體和 Figma 整合),然後透過簡潔的狀態機決定專案起點(特定編輯、現有 BRIEF.md 或全新創作)。技能明確區分「自動化」和「伴隨」兩種流程,其中「伴隨」模式會將使用者定位為共同創作者,並要求提供詳盡的初始計畫草案(即「天花板處理」),強調服務概念而非工具選項。透過強制在所有階段加載特定參考文件(例如用於版式設計的 hyperframes-core 或用於創意指導的 hyperframes-creative),並禁止憑記憶替代,它將上下文消耗降至最低,同時確保輸出遵循既定的通訊協定和 HyperFrames 註冊表中的現成區塊。

相容平台~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

成功且無任何動作表示技能已是最新。請顯示更新失敗的訊息,而非依賴記憶繼續執行。

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 網址,請先執行 /figma。根據其匯出的資產、設計標記、元件或分鏡圖影格進行建構。請勿使用原始的 Figma 連接器呼叫,因為它們會跳過 SVG 清理、媒體來源追蹤和品牌標記綁定。

這些適配器不會改變 /hyperframes 所選定的工作流程。

2. 從專案狀態開始

套用第一個符合的列;請勿評估較低層級的狀態列:

狀態動作
特定編輯進行編輯,保留現有的專案決策,然後重新執行受影響的檢查。請勿重新開啟探索階段。
BRIEF.md 存在讀取它。若 workflow 指定了其他工作流程且 flow 不是 companion,則移交。不詢問任何簡報問題。
無簡報,但 hyperframes.json 或 STORYBOARD.md 存在從檔案和記錄的偏好設定繼續執行。僅根據已知事實回溯填寫 BRIEF.md。
全新創作執行 /hyperframes 及其意圖層。僅在 workflow: general-video 或 flow: companion 時返回此處。

對於新專案,請從簡報中選擇一個 kebab-case 格式的目錄名稱,並在建構環境前先建立目錄結構,然後撰寫簡報:

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>;切勿記錄推斷的預設值。此處 <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檢查點關卡的行為方式遵循簡報合約。切勿要求使用者指定模式。

請勿為這些狀態發明同義詞。正在進行的「直接建構」訊號由意圖層處理,並以 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的計劃規範)、轉場、音訊身份——音樂和音效標記,或刻意的靜默——放置使用者的素材,以及設計好的開頭與結尾。用一句話說明每個層級添加了什麼;標註成本較高的項目(渲染時間、登入、計費)。使用者應該修剪處理方式,而不是逐項批准來拼湊一個。
  • 天花板屬於概念,而非工具箱。 每個層級都必須服務簡報的訊息——一個對任何影片都一視同仁的處理方式只是裝飾。技藝應達到天花板;內容永遠不應超出所要求的範圍(§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
任何媒體資產或操作,包括旁白、背景音樂、音效、字幕、調色或轉換/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 了解結構。對於開放式的多場景簡報,透過 /hyperframes-creative → references/prompt-expansion.md 擴展提示。多場景計劃引用每個場景的形狀:當有合適的藍圖時,使用來自 /hyperframes-animation → blueprints-index.md 的藍圖 ID;若無,則使用它從 rules-index.md 組合的具名規則——動作名稱來自這些索引,絕非發明。故事的真實性決定了哪些場景存在;引用只是為它們披上外衣。在您計劃自行建構任何具名外觀之前,請先搜尋即時目錄:對於簡報中提到的每個外觀、特效、處理或轉場——「CRT 掃描線」、「故障」、「底片顆粒」、「閃爍掃掠」、「五彩紙屑爆發」——請執行 npx hyperframes catalog --query "<外觀的簡單英文描述>" --json 並在計劃命名該外觀如何建構之前,讀取前幾筆結果。此搜尋不需要安裝任何東西:不需要專案、不需要事先 add、不需要帳號。它會從任何目錄對整個託管註冊表(約 400 個區塊和元件)進行排名,因此也適用於使用者在建構過程中要求的外觀。計劃所命名的區塊將在階段 3 安裝;僅在搜尋結果中完全沒有合適的項目時,才自行手工編寫外觀。多場景計劃也會記錄為派遣工件:每個場景在 STORYBOARD.md 中有一個 ## Frame N 區塊——status: outline、宣告的 src:、藍圖/規則引用和節拍文字——即使 storyboard: no 也是如此。該區塊是派遣單位;分鏡圖表單僅是審查界面。
  2. 在要求時審查計劃。 對於 storyboard: yes,對這些區塊執行共享的審查循環。對於 storyboard: no,繼續進行,無需計劃暫停或草稿表。如果無論如何發生了計劃暫停,請將子代理委派授權(codex 在步驟 4 派遣時需要)合併到該暫停中,而不是稍後再次停止。
  3. 解析依賴項。 在並行工作之前安裝註冊表區塊。準備使用者資產,採用現有專案文件,並驗證所有必要元素。此階段確保存取權限和資產就緒。
  4. 在建立Frames / 場景時派遣。 使用 /hyperframes 工具按順序處理每個 Frame 區塊。每個 Frame 的輸出應為獨立的 HTML 或 subcomposition,遵循核心合成模式。
  5. 執行驗證。 針對設計合約和品質標準檢查輸出。進行必要的調整以滿足技術和藝術要求。
  6. 生成最終預覽。 為核准準備輸出。這包括渲染最終影片或生成審查素材。
  7. 尋求渲染核准。 在完成製作前獲得最終核准。這是最終檢查點,確保所有要素都符合專案目標。

6. 完成並交付

收尾步驟:

  • 確保所有資產都正確打包。
  • 根據需要更新 BRIEF.md 和 STORYBOARD.md 檔案,以反映最終狀態。
  • 在專案根目錄執行最終清理指令:npx hyperframes finalize --project <project>。
  • 提供最終交付摘要,包含專案位置的檔案路徑和主要決策的摘要。

7. 更新技能

定期檢查技能更新以確保相容性:

npx hyperframes skills update general-video

在開始新專案或遇到預期外的行為時,請務必執行此指令。

故障排除

  • 技能未找到: 確保技能已正確實作:npx hyperframes skills list。
  • 驗證錯誤: 檢查是否已正確遵循所有參考規則。
  • 資產問題: 確認所有媒體資產都已正確安裝且可存取。
  • Figma 連接器警告: 始終透過 /figma 路由 Figma URL,而非直接呼叫 connector。
  • 權杖錯誤: 執行 npx hyperframes auth status 確認驗證狀態。

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.

相關技能