Community H3 prompt-expansion and validation harness — feedback welcome

Hi MiniMax-H3 maintainers — thank you for releasing H3 and the public prompt-writing guidance.

I maintain Omni-Rewriter, a small Apache-2.0 community project exploring a typed prompt-expansion workflow for image and video generators. We added an H3-oriented profile based only on public materials:

user intent → typed draft → deterministic validation → bounded repair → H3-oriented text

The current H3 path covers the public T2VA / I2VA / L2VA / FL2VA / Ref2VA routing, timestamped shot grammar, dialogue tags, media-role checks, and explicit first/last-frame constraints. Prompt expansion is kept separate from generation. We do not claim to reproduce or approximate the private H3-Context-IR implementation, and we do not present the project as an official MiniMax SDK.

We have also exercised optional H3-Base generation through a local SGLang deployment and published same-seed RAW vs expanded examples. These are community examples rather than a quality leaderboard or a universal improvement claim.

Links:

• Project: https://github.com/WayneJin0918/Omni-Rewriter
• H3 profile and boundaries: https://github.com/WayneJin0918/Omni-Rewriter/blob/main/docs/dialects/h3-pe-harness.md
• Adapter notes: https://github.com/WayneJin0918/Omni-Rewriter/blob/main/docs/dialects/h3-adapters.md
• Public examples: https://waynejin0918.github.io/Omni-Rewriter/home.html#cases

Would this kind of community prompt-validation tool be useful in a community resources or prompting section? If so, I would be glad to open a very small README PR in whatever location and wording you prefer. If it is outside the repository's scope, no worries at all — feedback on any incorrect H3 assumptions would still be very helpful.

Thank you for your time and for making the model and guidance available.

Start with the linked docs/dialects/h3-pe-harness.md and docs/dialects/h3-adapters.md, then inspect the repository README and any community-resources or prompting section. The issue does not identify a target file or wording; done would require maintainer agreement on scope and a small README or documentation change reflecting that decision.