MCP HubMCP Hub
SKILL·E3F4B0

vibe-creating-prompt

Alisa0808
업데이트됨 22 days ago
5 조회
134
20
134
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 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.

스킬 보기
polymarket
메타

이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.

스킬 보기
creating-opencode-plugins
메타

이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.

스킬 보기
sglang
메타

SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.

스킬 보기