Skip to content

feat: add video-prompt-design subagent for Veo 3 meta prompt framework#156

Merged
marcusquinn merged 3 commits intomainfrom
feature/video-prompt-design-subagent
Jan 23, 2026
Merged

feat: add video-prompt-design subagent for Veo 3 meta prompt framework#156
marcusquinn merged 3 commits intomainfrom
feature/video-prompt-design-subagent

Conversation

@marcusquinn
Copy link
Owner

@marcusquinn marcusquinn commented Jan 23, 2026

Summary

  • Adds video-prompt-design subagent to tools/video/ based on the Veo 3 Meta Framework
  • Provides structured 7-component prompt engineering for AI video generation (Subject, Action, Scene, Style, Dialogue, Sounds, Technical)
  • Follows build-agent best practices: YAML frontmatter, AI-CONTEXT block, progressive disclosure, under 100 instructions

Changes

  • New: .agent/tools/video/video-prompt-design.md - Complete subagent with character consistency templates, camera positioning syntax, audio hallucination prevention, domain-specific templates, and Veo 3 limitations
  • Updated: .agent/AGENTS.md - Added to subagent folder table and progressive disclosure section
  • Updated: README.md - Added to imported skills table, Video Creation section, and Animation & Video section

Design Decisions

  • Kept model-agnostic where possible (techniques apply to Veo 3, Sora, Kling, etc.)
  • Used upstream_url in frontmatter to track source repo
  • Enabled webfetch: true for fetching latest model documentation
  • All code blocks use text language specifier (no bare fences)

Summary by CodeRabbit

  • Documentation
    • Added Video Prompt Design documentation with structured 7-component guidance for AI video generation, examples, and checklists.
    • New Video Prompt Design entry added across tools lists, README sections, and CLI/help references for video creation.
    • Registered Video Prompt Design as a new skill source so it appears in the imported skills catalog.

✏️ Tip: You can customize this high-level summary in your review settings.

Add structured AI video prompt engineering subagent based on the
snubroot/Veo-3-Meta-Framework. Includes 7-component format (Subject,
Action, Scene, Style, Dialogue, Sounds, Technical), character
consistency templates, camera positioning syntax, audio hallucination
prevention, and domain-specific templates.

Updates AGENTS.md subagent table and progressive disclosure section.
Updates README.md with new skill entry and video creation references.
@gemini-code-assist
Copy link

Summary of Changes

Hello @marcusquinn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the system's capabilities in AI video generation by integrating a dedicated subagent for advanced prompt engineering. It provides users with a robust, structured framework to create high-quality, consistent, and detailed prompts for various AI video models, thereby improving the overall output and efficiency of video content creation.

Highlights

  • New Video Prompt Design Subagent: Introduced a new subagent, video-prompt-design, located under tools/video/, which provides a structured approach to AI video generation prompt engineering.
  • Veo 3 Meta Framework Integration: The new subagent is based on the Veo 3 Meta Framework, offering a 7-component prompt engineering structure (Subject, Action, Scene, Style, Dialogue, Sounds, Technical) applicable to models like Veo 3, Sora, and Kling.
  • Comprehensive Prompting Guidance: The subagent includes detailed guidance on character development, camera work (shot types, movement, positioning), dialogue design, audio engineering, negative prompts, physics-aware prompting, and specific formulas like the selfie video formula.
  • Adherence to Best Practices: The new subagent follows established best practices, including YAML frontmatter, an AI-CONTEXT block, progressive disclosure, and keeping instructions concise (under 100).
  • Documentation Updates: The AGENTS.md and README.md files have been updated to reflect the addition of the new video-prompt-design subagent, ensuring it is discoverable and properly documented within the system.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 23, 2026

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

This pull request adds a new Video Prompt Design skill: a comprehensive 7-component meta-prompt guide for AI video generation, registers it in agent configs, and updates agent and public README documentation to reference the new tool.

Changes

Cohort / File(s) Summary
Agent docs & registry
.agent/AGENTS.md, .agent/configs/skill-sources.json
Added video-prompt-design to the tools table and Subagent Folders in .agent/AGENTS.md; registered a new skill entry in .agent/configs/skill-sources.json pointing to .agent/tools/video/video-prompt-design.md.
Video Prompt Design guide
.agent/tools/video/video-prompt-design.md
New documentation (detailed 7-component meta-prompt framework) including quick reference, core format, camera/dialogue/audio guidelines, negative prompts, domain templates, examples, and Veo 3 notes.
Public README updates
README.md
Added video-prompt-design to Imported Skills and to Video Creation / Animation & Video sections and CLI references describing the structured prompt-engineering skill.

Sequence Diagram(s)

(omitted — changes are documentation and registry updates without multi-component runtime control flow)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

🎬✨ A seven-part map for frames and sound,
Prompts assembled, every detail found.
Scenes, style, dialogue—crafted tight,
Docs now steer the model toward the light. 🚀

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: adding a new video-prompt-design subagent implementing a Veo 3 meta prompt framework, which is the primary focus across all modified files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new video-prompt-design subagent based on the Veo 3 Meta Framework. The changes include adding the subagent's documentation, which provides a structured 7-component framework for AI video prompt engineering, and updating the AGENTS.md and README.md files to reflect this new capability. The new subagent documentation is comprehensive and well-structured. My feedback includes a couple of suggestions to improve clarity and consistency in the prompt design guidance to ensure the AI agent can interpret it as effectively as possible.

Action: [Movements, gestures, timing, micro-expressions]
Scene: [Environment, props, lighting, weather, time of day]
Style: [Camera shot, angle, movement, colour palette, depth of field]
Dialogue: [Character]: "Speech" (Tone: descriptor)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The dialogue format presented here in the quick reference is slightly different from the more detailed example provided on lines 112-113 ((Character Name): "Exact dialogue here"). To ensure maximum clarity and consistency for the agent, it's best to use the same, most complete format in all examples. This reinforces the single best practice.

Suggested change
Dialogue: [Character]: "Speech" (Tone: descriptor)
Dialogue: (Character Name): "Speech" (Tone: descriptor)

```

**Critical Techniques**:
- Camera positioning: Include `(thats where the camera is)` for spatial anchoring

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There's a small typo here and also on line 94. "thats" should be "that's". Correcting this will improve the professionalism of the documentation and any prompts generated based on it.

Suggested change
- Camera positioning: Include `(thats where the camera is)` for spatial anchoring
- Camera positioning: Include `(that's where the camera is)` for spatial anchoring

@github-actions
Copy link

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 351 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Fri Jan 23 20:41:16 UTC 2026: Code review monitoring started
Fri Jan 23 20:41:17 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 351
Fri Jan 23 20:41:17 UTC 2026: Qlty - 0 issues found, auto-formatting applied
Fri Jan 23 20:41:19 UTC 2026: Codacy analysis completed with auto-fixes

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 351
  • VULNERABILITIES: 0

Generated on: Fri Jan 23 20:42:37 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In @.agent/tools/video/video-prompt-design.md:
- Around line 94-95: Replace the typo in the camera positioning example string:
change "thats" to the contraction "that's" in the line containing "Close-up shot
with camera positioned at counter level (thats where the camera is) as the
character demonstrates the product" so the example reads "...(that's where the
camera is)..." for correct punctuation and clarity.

Comment on lines +94 to +95
"Close-up shot with camera positioned at counter level (thats where the camera is)
as the character demonstrates the product"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix minor typo in camera positioning example.

Use “that’s” to improve clarity.

✏️ Proposed fix
-"Close-up shot with camera positioned at counter level (thats where the camera is)
+"Close-up shot with camera positioned at counter level (that's where the camera is)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"Close-up shot with camera positioned at counter level (thats where the camera is)
as the character demonstrates the product"
"Close-up shot with camera positioned at counter level (that's where the camera is)
as the character demonstrates the product"
🤖 Prompt for AI Agents
In @.agent/tools/video/video-prompt-design.md around lines 94 - 95, Replace the
typo in the camera positioning example string: change "thats" to the contraction
"that's" in the line containing "Close-up shot with camera positioned at counter
level (thats where the camera is) as the character demonstrates the product" so
the example reads "...(that's where the camera is)..." for correct punctuation
and clarity.

@augmentcode
Copy link

augmentcode bot commented Jan 23, 2026

🤖 Augment PR Summary

Summary: Introduces a video-prompt-design subagent that documents a Veo 3–oriented meta-prompt framework for AI video generation.
Changes:

  • Added .agent/tools/video/video-prompt-design.md with a 7-component prompt format plus character, camera, dialogue, audio, and negative-prompt guidance.
  • Updated .agent/AGENTS.md to register the new video tool and link it in the progressive disclosure section.
  • Updated README.md to surface the new tool in the imported skills table and video-related docs sections.
Why: Make prompt engineering more structured and repeatable to improve quality and consistency across models (Veo 3, Sora, Kling). Technical Notes: Uses YAML frontmatter with an upstream_url reference and enables webfetch; the guidance standardizes “Subject/Action/Scene/Style/Dialogue/Sounds/Technical” output with explicit audio + negative constraints. Mentions Veo 3 constraints (8s/16:9) and recommends short dialogue limits per generation. Includes templates for consistent characters and domain-specific audio libraries to reduce hallucinations. No runtime code changes; updates are documentation/agent-instructions only.

🤖 Was this summary useful? React with 👍 or 👎

Copy link

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. 2 suggestions posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

upstream_url: https://github.com/snubroot/Veo-3-Meta-Framework
tools:
read: true
write: true
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

video-prompt-design enables write/edit tools in frontmatter; since this subagent appears to be guidance-only, consider disabling them to follow least-privilege and reduce accidental workspace modification risk.

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

|-------|--------|-------------|
| **cloudflare-platform** | [dmmulroy/cloudflare-skill](https://github.com/dmmulroy/cloudflare-skill) | 60 Cloudflare products: Workers, Pages, D1, R2, KV, Durable Objects, AI, networking, security |
| **remotion** | [remotion-dev/skills](https://github.com/remotion-dev/skills) | Programmatic video creation with React, animations, rendering |
| **video-prompt-design** | [snubroot/Veo-3-Meta-Framework](https://github.com/snubroot/Veo-3-Meta-Framework) | AI video prompt engineering - 7-component meta prompt framework for Veo 3 |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is listed as an imported skill with “automatic update tracking”, but there’s no corresponding entry for video-prompt-design in .agent/configs/skill-sources.json, so aidevops skill check/update won’t be able to track upstream changes.

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

@marcusquinn
Copy link
Owner Author

Re: thats vs that's - this is intentionally without apostrophe. The upstream Veo 3 Meta Framework documents this as the exact syntax that triggers Veo 3's camera-aware processing. Using that's (with apostrophe) may not produce the same camera positioning behaviour. Keeping as-is to match the proven community-verified syntax.

…ue format, add skill tracking

- Set write/edit to false (guidance-only subagent, least-privilege)
- Use (Character Name): format consistently in quick reference
- Add video-prompt-design entry to skill-sources.json for upstream tracking
Remove quality tiers, domain templates, meta prompt generation layers,
and success metrics - these are aspirational fluff from upstream that
don't help craft better prompts. Consolidate physics/movement into one
section. Keep only actionable prompt engineering guidance.
@github-actions
Copy link

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 351 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Fri Jan 23 21:18:07 UTC 2026: Code review monitoring started
Fri Jan 23 21:18:07 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 351
Fri Jan 23 21:18:07 UTC 2026: Qlty - 0 issues found, auto-formatting applied
Fri Jan 23 21:18:09 UTC 2026: Codacy analysis completed with auto-fixes

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 351
  • VULNERABILITIES: 0

Generated on: Fri Jan 23 21:19:24 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@sonarqubecloud
Copy link

@github-actions
Copy link

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 351 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Fri Jan 23 21:18:59 UTC 2026: Code review monitoring started
Fri Jan 23 21:19:00 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 351
Fri Jan 23 21:19:00 UTC 2026: Qlty - 0 issues found, auto-formatting applied
Fri Jan 23 21:19:02 UTC 2026: Codacy analysis completed with auto-fixes

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 351
  • VULNERABILITIES: 0

Generated on: Fri Jan 23 21:20:17 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@marcusquinn marcusquinn merged commit d49694a into main Jan 23, 2026
9 checks passed
@marcusquinn marcusquinn deleted the feature/video-prompt-design-subagent branch January 23, 2026 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant