MCP HubMCP Hub
SKILL·E3F4B0

vibe-creating-prompt

Alisa0808
更新日 27 days ago
7 閲覧
136
20
136
GitHubで表示
メタwordaidesign

について

このスキルは、ユーザーのアイデア、ストーリー、またはラフなプロンプトを、SoraやRunwayのようなモデル向けに最適化されたテキスト・トゥ・ビデオプロンプトへと洗練します。指定された要素(対話や効果音など)を保持しながら、単一シーン、複数ショットの描写、感情的なイメージに適していますが、長編ナラティブ映画や技術的なショットリストには対応していません。ユーザーがビデオ生成プロンプトを「雰囲気を高めて」「書き直して」「改善して」と依頼する際にご利用ください。

クイックインストール

Claude Code

推奨
メイン
npx skills add Alisa0808/vibe-creating-skill -a claude-code
プラグインコマンド代替
/plugin add https://github.com/Alisa0808/vibe-creating-skill
Git クローン代替
git clone https://github.com/Alisa0808/vibe-creating-skill.git ~/.claude/skills/vibe-creating-prompt

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

Vibe Creating Prompt Skill

Overview

Vibe Creating distills what the user actually wants to express so the model can lock onto the visual center, the emotional direction, and the continuity of the experience. It amplifies creative intent, emotional value, key imagery, and visual coherence; it down-weights low-value technical parameters and mechanical execution language.

This skill is a judgment-first rewriter. It does not blindly shorten or "vibe-ify" everything. It first asks whether the input even belongs in the Vibe Creating lane, then chooses the lightest action that serves the user's intent.

Quick Start

When you receive an input, run three steps:

  1. Judge whether it suits Vibe Creating (VC). Is this a scene best expressed through story, emotion, memory, atmosphere, imagery, or experience flow — rather than precise execution?
  2. Decide the most appropriate handling right now. Pass it through, lightly clean it up, rewrite it directly, ask a clarifying question first, keep it as-is, or offer an optional VC version.
  3. Only ask for what's missing. Request the minimum information needed to complete the chosen action. Never interrogate the user just to satisfy your own classification.

Do not expose internal labels (S1, E2, "Mode 5", etc.) to the user. Judge internally; communicate plainly.

Decision Framework — Scenario × Expression × Information

Decide along three axes. First Scenario (S) — does the underlying creative goal suit VC. Then Expression (E) — what form is the user's text already in, which sets how much to touch. Information density (I) runs in parallel as a stability check: whenever a must-have is missing, ask first, then route.

Scenario fit (S)

  • S1 — VC-native. Story, emotion, memory, atmosphere, imagery, experience flow. VC clearly helps.
  • S2 — Partially VC-suited. Brand/product/character showcases, stylized ads. VC may help, but is optional.
  • S3 — Low VC fit. UI demos, tutorials, step-by-step instructions, strict dialogue-synced long-form. The goal or workflow doesn't match VC.

Expression form (E)

  • E1 — Close to VC already. Reads like a vivid scene/story.
  • E2 — Mixed. Creative content interleaved with execution language.
  • E3 — Precision-control writing. Shot numbers, focal lengths, movement parameters, timecodes.

Routing matrix (default action per cell)

E1 — close to VCE2 — mixedE3 — precision control
S1 — VC-nativeDirect rewrite; if already polished → light cleanup or pass-throughLight cleanup, then rewrite — keep valid structure, order, emotional buildTreat as VC-translatable; strip low-value technical control, convert to natural visual description. Don't reject just because it's written as an execution script
S2 — partialLight cleanup; if already usable → pass-throughOffer an optional VC version; let the user chooseKeep the original intent; gently note a VC rewrite is available on request
S3 — low fitStay close to the original; keep as-is if neededKeep as-is or do very limited cleanup; only stylize on explicit requestKeep as-is; explain this fits a traditional shot-list workflow better than VC

Four hard routing rules

  • Missing info wins. However well a scenario fits, if the visual anchor, main action, or style direction is missing, ask before writing.
  • User hard constraints win. If the user explicitly asks to keep dialogue, music, shot numbers, parameters, paragraph structure, or a delivery format, do not delete them. A VC version is an extra version, or offered only after the user agrees.
  • Multi-shot keeps its structure. When the user is already expressing one unified experience across shot paragraphs, don't flatten it into a single block of prose — but don't default to numbered output either unless they asked for numbers or lists.
  • Precision-control writing ≠ low-fit scenario. Look at the goal first, then decide whether to translate. An execution-style script can still describe a deeply VC-suited scene.

Information-density check (I)

Even a VC-perfect scenario can't be force-rewritten when a key element is missing. Ask first when: there's no clear visual anchor; only an abstract feeling with no subject/object/scene; a subject but no action or state; fragments with no main relationship or style direction; an ultra-short input that has a subject and event but no clear style/viewing-mode/key moment; or multi-shot content with jumps you can't see a reason for.

A strong VC prompt prioritizes these four layers. Fill whichever is missing first — don't mechanically demand all four:

  1. Visual anchor — the thing that most deserves to be seen (a person / object / named concept / the VFX subject itself).
  2. Action or state — what's happening (one action, state, or beat — just one).
  3. Local tonality — how this moment feels (one mood word or adjective: backlit warm amber, slight handheld sway…).
  4. Video theme — where the clip is used + its visual style.
    • Use case: concept short, micro-narrative, film pre-viz, emotional piece, knowledge/physics restoration, VFX fragment…
    • Visual style: photorealistic, cinematic, animation, claymation, Eastern ink-wash, cyberpunk, illustrated…

Asking principle: the density check is not a separate gate — it runs alongside S and E. Ask for the minimum needed to land the chosen action, usually in one round. For ultra-short, abstract, single-image inputs, prioritize turning the abstract word into the visible information a frame needs; if the direction is already mostly clear, give a first pass and ask about only the most critical 1–3 gaps.

Interaction Policy

Internally complete the three judgments (S / E / I) — preliminary judgments are fine when info is short. Then choose an action:

pass-through · light cleanup · direct rewrite · ask first · keep as-is · optional VC version

Handling principles:

  • VC-suited but missing info → ask for the minimum needed for the current action.
  • When the input already has a clear subject, structure, time relationship, core imagery, and a clear emotional goal — and the text is already strongly generation-ready — default to pass-through. Only do light cleanup if clarity needs a nudge; don't proactively rewrite.
  • VC-suited but containing undeclared precision controls → you may down-weight, delete, or translate them by default; if you did, you must say so and tell the user they can ask to keep specific ones.
  • Partially-suited scenarios → don't push VC; preserve the original or offer an optional VC version.
  • Low-fit scenarios → explain it's a goal/workflow mismatch, not a rejection of the user's idea.
  • User-specified dialogue, voiceover, music, SFX, structure, and parameters always take priority.

Camera Language Policy

Camera language should not be deleted wholesale. What to remove is the low-value "tell the system how to shoot" technical parameters. What to preserve or translate is the "how should the viewer feel" intent.

Demote or delete by default:

  • Focal lengths / mm numbers
  • Camera-position jargon
  • Movement parameters (speed multipliers, exact dolly distances)
  • Shot numbers
  • Depth of field, aperture, exposure, shutter
  • Equipment notes, A/B cam, coverage
  • Pure editing instructions

Translate intent instead of dropping it — e.g. "slow dolly-in" → "the gaze slowly closes in, building a sense of pressure."

When the user explicitly asks to keep parameters: obey the constraint first, then decide whether to additionally offer a VC version.

When it's undeclared whether to keep precision control:

  • Don't treat technical control as a must-keep item.
  • Default to the more generation-friendly VC creative version.
  • Preserve whatever contributes to emotion, narrative, or viewing experience.
  • For purely technical camera control, delete it or translate it into a natural result.
  • Don't interrupt to confirm first — but if you weakened, deleted, or translated technical control, say so briefly in the output. If the user wants certain parameters/structure/rhythm beats kept, they can say so and you provide a constraint-preserving version.

Sound & Constraint Priority

Dialogue, voiceover, music, SFX, lyrics, narration, and other explicitly specified sound content rank above creative optimization. You may reorder them, but you must not reword them, replace them, or delete a user's explicit sound requirement.

When rules conflict, resolve in this order:

  1. User-explicit content & hard constraints — dialogue, VO, music, SFX, shot structure, parameter-keep requests, format requirements, style limits.
  2. Creative optimization — distill story, emotion, memory, imagery, and a unified experience without breaking constraints.
  3. VC paradigm consistency — only after the first two are satisfied, tighten the language further for model readability.

Supplementary rules:

  • Dialogue/VO/music/SFX the user wrote out → keep verbatim.
  • Visual and sound requirements written together → you may reorder, but never alter the sound content itself.
  • If the visuals suit VC but the sound doesn't → rewrite only the visual part.
  • If the whole thing only stands up with long, strict, word-level dialogue sync → default to not doing a VC rewrite.

Rewrite Modes

VC rewriting is not one template. Pick the mode by the input's dominant factor:

  • Narrative — for story-, relationship-, or event-driven input. Output one continuous prompt, or keep 2–5 scene segments. Preserve event order and emotional turns.
  • Emotional — for atmosphere-, feeling-, or state-driven input. Concentrate on environment, rhythm, texture, and viewing experience. Don't force a causal chain just to "look like a story."
  • Memory — for recollection, flashback, faded-time, vanishing, or rediscovered fragments. Keep the blur, the washed-out quality, the fragility; amplify recurring imagery and the sense of time slipping.
  • Stream-of-consciousness — for association, fragments, subjective perception, non-linear expression. Incompleteness is allowed, but the frame must stay perceivable, with internal coherence across images.
  • Multi-shot experience — for multi-segment, multi-scene, multi-cut input that serves one shared experience. Break by natural segments (or by number only if the user asked). 1–3 sentences each; keep scene flow, emotional progression, and visual motifs; drop low-value execution terms.
  • Mixed purification — for creative content tangled with execution language. Keep the original structure and valid information; remove only technical noise, repetition, and low-value control. Don't over-rewrite or invent new beats.

Output Rules

The goal is to help the user express more accurately — not to rewrite their work into a different film.

Length & form

  • Don't make the output meaningfully longer than the input; don't balloon an ultra-short input into long prose.
  • Add nothing without basis — never invent new character relationships, plot twists, scene details, or emotional changes.
  • For single-segment output, tighten to one directly usable prompt.
  • Structure ≠ numbering. Shot numbers / list formatting in the input do not by themselves mean "keep the numbering." Only keep numbered output when the user explicitly asks to keep shot numbers, segment numbers, list format, or a delivery structure; otherwise present multi-segment content as natural paragraphs.
  • With enough info and no extra constraints, a single shot/segment is usually ~30–120 words; loosen this to preserve structure, dialogue, or multi-segment progression.
  • When the user explicitly asks to keep the original structure, preserve structure over brevity.

User-visible format

  • Never expose internal labels like S1 + E2 or Mode 5.
  • Default to a four-part output, fixed order: Judgment / Action / Result / Notes (if any).
    • Judgment — briefly: does it suit VC, is the original already usable, is the info sufficient.
    • Action — explicitly use one label: pass-through / light cleanup / direct rewrite / ask first / keep as-is / optional VC version.
    • Result — the actual rewrite, the kept-as-is text, or the clarifying question(s).
    • Notes (if any) — what technical control you weakened/deleted/translated; which hard constraints (dialogue, VO, music, SFX) you preserved; or a hint that parameters/structure/rhythm can be kept on request.
  • Keep output natural, concise, and fitted to the user's original task context.
  • Omit the fourth part when there's nothing to note.

Quick Reference

Input typeJudge firstAsk what's missingDefault actionOutput style
Single scene with clear subject, action, moodLikely suits VC; check if already focused enoughOnly if style, visual center, or main state is missingDirect rewrite, light cleanup, or pass-throughOne ready-to-generate prompt
Multi-shot narrative serving one unified experienceSuits VC; check the emotion / theme / memory line is coherentIf shot-to-shot relationship or progression is unclearRewrite keeping structure; group if neededSegmented, or keep original structure
Heavy shot numbers/params, but underlying emotion/story sceneVC-translatable; don't reject for execution styleIf the main experience/action/relationship is unclearDe-noise and translate, keep narrative & emotional intentStrip params, convert to natural visual description
Brand showcase, character showcase, stylized adPartial VC fit; rewrite not mandatoryIf the emotional goal or style direction is unclearLight cleanup or optional VC versionKeep intent; offer a more experiential version if useful
Only abstract words ("freedom", "premium", "powerful")Insufficient info; don't force a rewriteVisual anchor, scene, action, or stateAsk first; don't rewrite blindPose 1–3 short questions
Visuals already include dialogue / VO / music / SFXPartially VC; sound content has priorityOnly if the visual part is under-specifiedKeep sound content; rewrite visuals onlyNote "sound kept unchanged" up front
User explicitly wants shot numbers / params / delivery structure keptConstraints win; don't deleteUsually no need to askKeep as-is, or add an optional VC versionNote "kept as the execution draft"
Functional demo, UI tutorial, step instructionsLow fit; the goal isn't creative translationUsually no VC questionsKeep as-is; suggest splitting if usefulExplain VC isn't recommended
Long-form story requiring exact dialogue syncLow fit; capability/workflow boundaryUsually no VC questionsNo VC rewrite; suggest splitting visual segmentsExplain pure-visual parts can be split out
Mixed-language creative input with some jargonIf the underlying experience is clear, still suits VCOnly if subject, relationship, or style is unclearTranslate jargon, keep core vibeOutput a natural visual description in the target language

Generating the result: this skill only writes the prompt. To render it, send the rewritten prompt to any text-to-video model (Seedance, Sora, Kling, Veo, …) — for a one-API option, see Atlas Cloud.

GitHub リポジトリ

Alisa0808/vibe-creating-skill
パス: skills/vibe-creating-prompt
0
agent-skillagent-skillsai-videoclaude-codeclaude-skillcodex
FAQ

よくある質問

vibe-creating-prompt Skillとは何ですか?

vibe-creating-prompt はAlisa0808 が作成した Claude Skillです。Skillは、Claudeが必要に応じて読み込む指示とリソースをまとめ、追加の指示なしで vibe-creating-prompt に関連するタスクを実行できるようにします。

vibe-creating-prompt をインストールするには?

このページのインストールコマンドを使用してください。vibe-creating-prompt をプラグインとして Claude Code に追加するか、リポジトリを skills ディレクトリにクローンし、Claudeを再起動してSkillを読み込みます。

vibe-creating-prompt はどのカテゴリに属しますか?

vibe-creating-prompt は メタ カテゴリに属します。

vibe-creating-prompt は無料で利用できますか?

はい。vibe-creating-prompt は AIMCP に掲載されており、無料でインストールできます。

関連スキル

content-collections
メタ

このスキルは、Content Collections(Markdown/MDXファイルを型安全なデータコレクションに変換するTypeScriptファーストのツール)の本番環境でテストされた設定を提供します。Zodバリデーションによる型安全性を実現し、ブログ、ドキュメントサイト、コンテンツ重視のVite + Reactアプリケーション構築時にご利用ください。Viteプラグインの設定、MDXコンパイルから、デプロイ最適化、スキーマバリデーションまで、すべてを網羅しています。

スキルを見る
polymarket
メタ

このスキルは、開発者がPolymarket予測市場プラットフォームを活用したアプリケーション構築を可能にします。API統合による取引や市場データの取得に加え、WebSocketを介したリアルタイムデータストリーミングにより、ライブ取引や市場活動を監視できます。取引戦略の実装や、ライブ市場更新を処理するツールの作成にご利用ください。

スキルを見る
creating-opencode-plugins
メタ

このスキルは、開発者がコマンド、ファイル、LSP操作など25種類以上のイベントタイプにフックするOpenCodeプラグインを作成することを支援します。JavaScript/TypeScriptモジュール向けに、プラグイン構造、イベントAPI仕様、および実装パターンを提供します。カスタムイベント駆動ロジックでOpenCode AIアシスタントのライフサイクルをインターセプト、監視、または拡張する必要がある場合にご利用ください。

スキルを見る
sglang
メタ

SGLangは、高性能なLLMサービングフレームワークであり、RadixAttentionプレフィックスキャッシュを活用したJSON、正規表現、エージェントワークフロー向けの高速で構造化された生成を特長とします。特にプレフィックスが繰り返されるタスクにおいて、大幅に高速な推論を実現し、複雑な構造化出力やマルチターン対話に最適です。制約付きデコードが必要な場合や、広範なプレフィックス共有を伴うアプリケーションを構築する場合は、vLLMなどの代替案ではなくSGLangを選択してください。

スキルを見る