Your idea deserves a video that holds attention.

A topic, a method or a reference video. Choose a path to turn it into a short with a hook, visuals, voice and captions. Here are INEMA’s five engines and what to ask for with each one.

“Viral” is the name of the production line. Reach and views are not guaranteed.

Five paths. One idea at a time.

The names may seem similar, but the input and the result differ. Start with what you want to tell.

What do you have to start with?

Your starting pointStart withWhat defines the video
A method in stepsrtexA topic in “N pieces”; the documented default aims for 60–90 seconds.
A short, strong thesisr7exSeven triggers; the format described in the guide aims for 40–50 seconds, including the final card.
An illustrated explanationrtexjpVoice and an illustrated character, without lip sync or HeyGen.
A video linkrefazvideoThe reference provides the content; you define the new explanation and its format.
A topic, text or projectexplicavideoThe format, audience, duration and channel need to be clear in the request.

The commands are shortcuts for the INEMA environment. The repositories are materials to study and adapt: having the code does not automatically set up your avatar, voice or channel.

The hook draws viewers in. The explanation keeps them watching.

A strong headline isn’t enough. The video needs to deliver on its promise.

PartWhat needs to happen
HookStart with the pain point or desire of the viewer. A concrete image helps make the promise clear, even without sound.
ExamUse a verified statistic or a real demonstration. Every number needs a source.
DevelopmentExplain one topic using an example that carries through from one scene to the next. With rtex, organize it into pieces; with r7ex, follow the guide’s seven triggers.
Caveat and payoffState the idea’s limits and deliver on the opening promise.
ClosingAsk an opinion question related to the topic. Don’t promise to send materials in exchange for a comment.

From request to video review.

Each engine has its own commands. The work involves these decisions.

StageWhat to check
1 · Scope and sourcesAudience, thesis, format and destination. For refazvideo, include the reference and transcribe it before writing.
2 · ScriptHook, lines, visuals and closing. Review the facts before producing the voice and avatar.
3 · Voice and visualsrtex and r7ex use HeyGen Studio; rtexjp uses a local voice and character. The others follow the chosen format.
4 · EditingSync the scenes and captions to the actual narration. Check the opening screen and text size on a phone.
5 · ReviewRun the engine validator, inspect the frames, and watch the final file with sound. Fix cuts, blank screens, and incorrect words.
6 · PublishingCheck the title, thumbnail, description, and channel. Use the project’s publishing workflow; yt-pubx is one part of INEMA.

Costs depend on the approach: machines, GPUs, and subscriptions aren’t free. rtexjp doesn’t require HeyGen, but it does require local resources. The examples show the workflow; they don’t start production from this page.

Say what you want the person to understand.

Examples to adapt for the INEMA environment. Change the topic, audience, and channel before submitting. To install on another machine, follow each project’s guide.

One method · rtex

/rtex Como organizar as fontes de uma pesquisa em três peças. Público: quem está começando. Uma demonstração com o mesmo exemplo do início ao fim. Mostre os limites do método.

One thesis · r7ex

/r7ex Ter muitas ferramentas não significa ter um processo. Público: profissionais que usam IA no trabalho. Explique com um exemplo concreto e termine com uma pergunta de opinião.

One illustrated reel · rtexjp

/rtexjp Por que guardar o contexto ajuda a retomar um projeto. Um tema, voz local, personagem ilustrado e uma comparação visual fácil de entender.

One reference · refazvideo

Faça um vídeo novo com refazvideo.
Assunto: [o que quero explicar].
Referência: [URL do vídeo].
Público: [para quem]. Formato: short 9:16.
Escreva uma explicação própria, confira as fontes e mostre o storyboard antes da produção.

One topic · explicavideo

/explicavideo Como transformar uma tarefa repetida em um processo. Público iniciante, short 9:16, um exemplo completo. | portao

In explicavideo, | portao asks you to pause and approve the brief and visuals. Without this, the bot command may continue through to publication according to the request and configured channel. Read the guide before using it.

See the result before choosing.

Examples published by the projects. Some are from earlier versions; the guide explains the current standard.

The code for each approach.

Read the README and project instructions before installing or producing.

Continue with what you need.