Building with AI creative tools: 7 notes on image-to-prompt, lip-synced avatars, video watermarks, Flowith and OpenCode for writing

Most AI writing online is about chat and code. The tools I actually reach for on side projects are a bit different: something to reverse-engineer a prompt from a picture, a way to make a talking-head video without paying per minute, a canvas that mixes many image models, and a coding agent that turns out to be a decent writing partner. These seven notes cover that ground, roughly in the order you'd meet them while making a piece of content: images, video, workspaces, writing, and finally where to look for the next idea.

Each section is my own summary of a public page, not official material from the projects, and details such as credit counts or model lists are what the page said when I saved it. Every section links to the longer note on redreamality.com.

1. ImagePrompt.org: start from a picture, not a blank prompt box

When you like an image but can't put its style into words, an image-to-prompt tool does the describing for you. ImagePrompt.org takes an upload and writes back a text prompt covering the subject, setting, art style, palette, lighting and mood, and sometimes pose, composition and camera angle. You can ask for a general description or for output shaped for Flux, Midjourney or Stable Diffusion. Free users get five Prompt Credits a day, and the reset time shows in your local timezone. The site says uploads are processed only long enough to write the prompt and then deleted. NSFW images are blocked, and abstract or very busy pictures tend to get vaguer descriptions, so treat the result as a first draft you edit rather than a finished prompt.

2. A talking-head video on your own machine with Easy-Wav2Lip

This tutorial, from a Chinese AI forum, makes the case that a narrated or live-selling style avatar video doesn't need a paid online service. The recipe is simple. Film yourself for 20 to 30 seconds in front of a green screen, with the phone on a tripod, speaking at an even pace and keeping your hands fairly still. Record the voice yourself or generate it with CapCut's text-to-speech, exporting audio only as a .wav. Then run Easy-Wav2Lip locally, load the clip and the audio in its web UI, set quality to Enhanced and turn on mouth tracking. If the teeth come out missing, switching to the Wav2Lip_GAN model is the suggested fix. The last step is keying out the green in CapCut (chroma key) or After Effects (Roto Brush), then adding a background, subtitles and music.

3. DeMark-World: how video watermark detection and inpainting fit together

DeMark-World, which grew out of SoraWatermarkCleaner, is an open-source framework that finds and removes the visible watermarks AI video models stamp on their output. The README lists Sora, Runway, Pika, Kling, Gemini/Veo and Luma. I keep the note mostly for the pipeline, which is a neat two-stage design. A YOLO model detects the watermark box frame by frame, and frames where detection misses borrow an averaged box from their neighbours. Then an inpainting backend fills the region: LaMa if you want speed, E2FGVI-HQ if you need the fill to stay consistent across frames. It ships a Streamlit UI, a Python API, a CLI and a REST server (port 5344 in the example), plus a GPU docker-compose file. It's Apache 2.0, but those watermarks exist to show a clip is AI-generated, so check the model provider's terms and be honest about where your footage came from.

4. Flowith as a canvas for many image models

Flowith calls itself an agentic workspace, and its home page shows why: one canvas gives you flows, a flow library, media history, a "Knowledge Garden" and a knowledge market. The image side is the most crowded part. When I saved it, the model picker listed Seedream 5.0 Pro, GPT Image 2.5 and Grok Image 2.0 among many others, some marked NEW and some discounted. Next to the models sit small single-purpose apps such as background removal, relighting, upscaling, crop and resize, virtual try-on and social post templates. The appeal is not having to switch sites every time you want to compare two models on the same brief. The model list changes often, so check the live page before you plan around one.

5. Flowith knowledge bases you can buy, through one example

The other half of Flowith is its knowledge market, where people sell curated knowledge bases that the AI can answer from. The page I noted is a bioinformatics base from a creator listed as Yiming-Shi-PhD (BrainMed Lab). It promises to pull frameworks, methods and open debates out of the literature, spot gaps and trends that suggest research directions, and lay out a field visually. The useful design detail is the side-by-side trial: the same question answered by the "standard" AI and by the AI backed by the knowledge base, so you can judge the difference before you pay. Purchases are one-off with lifetime access and updates, resale is forbidden, and the creator receives 80% after tax. It's a small but concrete example of packaging your expertise as context rather than as a course.

6. OpenCode as a writing partner: Plan first, then Build

A Chinese OpenCode tutorial has a lesson that has nothing to do with code: using the agent to write articles. The complaint it answers is familiar. Ask the AI for a finished piece in one shot and quality swings wildly. The fix is three stages. In Plan mode you agree on the topic, structure and outline without touching files. In Build mode the agent writes the draft into a file. You then stay in Build mode and iterate, pointing at the draft with @filename to revise, polish or expand. The lesson includes a prompt template that casts the AI as a senior content strategist and returns positioning, a section outline, key points per section and alternative titles. If the voice drifts between sessions, it suggests pinning style preferences in AGENTS.md, the same file you'd use for code conventions.

7. BuilderPulse: one build idea a day, with its sources

To close, something for deciding what to make next. BuilderPulse is a daily brief for indie hackers and micro-SaaS founders. It says it cross-checks more than 300 public signals each day, from Hacker News, GitHub Trending, Product Hunt, Hugging Face, Google Trends, Reddit, Indie Hackers, Lobsters and DEV, and boils them down to one concrete idea, a reason why it matters now, and links to the sources. The issue I saved suggested a local-first memory system for agents that distils sessions into searchable notes, pointing to a 1,900% week-over-week jump in searches for agent memory. Whether or not you build that, the format is worth copying: one idea, one reason, evidence attached. The content is CC BY-NC 4.0, so commercial reuse needs the author's written permission.

Images (1), video (2 and 3), workspaces (4 and 5), writing (6) and choosing what to build (7): that covers most of a small content project from first sketch to the next idea. Pick the step where you lose the most time and start there.

A Japanese version of this list is on Qiita.