메뉴
Send feedback to the Viv team about the plugin, language, compiler, runtime, or documentation. Use when the user wants to report an issue, suggest an improvement, or share what's working well.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Answer questions about Viv, an engine for emergent narrative. Use when the user asks about Viv language constructs, authoring workflows, sifting patterns, actions, plans, reactions, tropes, queries, selectors, the compiler, the runtime, or emergent narrative in general.
Write Viv integration code — adapters, test harnesses, simulation runners, runtime integrations. Use when the user needs TypeScript, JavaScript, or Python code that works with the Viv compiler or runtime.
Sync the Viv install. Default flow: check for newer published versions of the compiler, runtime, monorepo, and editor plugins; review CHANGELOGs for breaking changes; and upgrade what's behind with user approval. Also handles downgrades, alignment, and reinstalls when the context calls for it.
Diagnose and fix Viv errors. Use when compilation fails, the runtime throws errors, the compiler and runtime are out of sync, or something isn't working as expected with Viv code.
Set up Viv in the current project. Conversational walkthrough that explains each step and asks before making changes. Run this first in any new Viv project.
Critique Viv code for optimization, clarity, emergent potential, and idiomatic style. Use when the user wants feedback on working code — performance, design, naming, missing constructs, or narrative potential. Does not make changes; produces a report.
| name | feedback |
| description | Send feedback to the Viv team about the plugin, language, compiler, runtime, or documentation. Use when the user wants to report an issue, suggest an improvement, or share what's working well. |
| argument-hint | [feedback] |
You are the user's Viv partner. If you haven't run viv-plugin-orient yet this session, run it now.
The user wants to send feedback to the Viv team. Help them compose and deliver it.
Understand the feedback. Is it:
Draft the feedback. Write it up clearly on the user's behalf. Include:
vivc --version)Show the draft to the user and ask for approval before sending anything.
Deliver it via GitHub issue (if the user has gh authenticated):
gh search issues --repo siftystudio/viv "<keywords>"gh issue create --repo siftystudio/viv --title "..." --body "..."If gh isn't available or the user prefers not to post publicly, they can email support@sifty.studio directly.
$ARGUMENTS