Designed & built Live

AveryJack Labs

Three browser-based prompt builders for AI image and video generators, built on a curated vocabulary of nearly 400 defined terms and a structured six-step cinematic workflow.

Project
AveryJack Labs
Role
Founder & Developer
Timeline
2025–Present
averyjacklabs.com
The AI Image Prompt Builder: a two-panel layout with Prompt Settings on the left — custom text, subject groups for General, Flora, Fauna and Food — and a Generated Prompt panel on the right offering a full prompt including MidJourney-specific parameters and a simple prompt that excludes them.

What it is

Three browser-based tools that assemble prompts for AI image and video generators: an image prompt builder, a video prompt builder, and Aurora, a step-by-step builder for cinematic video prompts.

They run anonymously in the browser. No account, no upload, no backend — work-in-progress persists to local storage.

The part that’s actually a knowledge problem

The interesting work here isn’t the React. It’s the vocabulary.

Underneath the interface sits a curated term set of roughly 380 entries, each with a written plain-language definition: 73 artistic media and styles, 227 named artists, and 83 Native American tribes. “Impasto” isn’t just an option in a list — it carries the definition thick paint application technique creating heavy texture and dimension.

That’s a controlled vocabulary with scope notes, which is the same artifact I build for enterprise knowledge bases. The reason it matters is identical in both cases: a term is only useful if the person choosing it knows what it means and uses it the same way every time. An untagged free-text prompt box gives you inconsistent results for the same reason an untagged knowledge base gives you inconsistent search results.

Design decisions

Two prompt outputs, not one. The image builder emits a full prompt that includes MidJourney-specific parameters — OmniReference, stylize, weird, chaos, line styles — and a simple prompt that strips them. The same creative intent has to be expressible for a platform that understands those flags and for one that would choke on them.

Three output formats for video. Plain text, Markdown, or JSON. Some generators want prose, some want structure.

Subject selection is capped. Each subject group — general, flora, fauna, food, seasonal, holiday — allows a small fixed number of picks rather than unlimited. The constraint is the feature: competing subjects are the most reliable way to produce a muddy image.

Aurora sequences the decisions. Six ordered steps run story and narrative first, then characters, visual style, audio, and technical specifications, with generation and export last. It’s an opinion about order — that you should decide what the thing is about before you decide how it’s lit.

Why it’s here

It’s a small product, but it’s the clearest example of me applying knowledge management technique somewhere nobody expects it. Faceted selection, controlled vocabulary, scope notes, constrained inputs, and multiple output serializations of one underlying record are knowledge-base patterns. Here they happen to produce prompts instead of articles.

Inside the project

2
averyjacklabs.com
The AveryJack Labs homepage presenting three builders as terminal-styled cards — IMAGE.PROMPT for MidJourney, DALL-E and Stable Diffusion, VIDEO.PROMPT for Sora, Runway and Pika, and AURORA.SYS as a six-step cinematic protocol.
Three tools, split by what they target rather than by feature tier.
averyjacklabs.com
The Aurora Video Builder showing Step 1 of 6, Story & Narrative, with a numbered workflow sidebar listing Story & Narrative, Characters, Visual Style, Audio & Sound, and Technical Specs, plus Randomize, Save Draft, and Reset controls.
Aurora breaks video prompting into six ordered steps instead of one large text box, so narrative comes before style and technical specs come last.

Questions about this work?

Happy to go deeper on any of it — the decisions, the trade-offs, or what I'd do differently.