Community Posts

Ready-to-paste copy for launch surfaces.

One-liner

StitchFlow turns prompts into UI directions, local HTML, and screenshots across Codex, Claude Code, OpenClaw, GitHub Copilot, and Gemini CLI.

Show HN

Title option 1

Show HN: StitchFlow – turn prompts into local UI screens, HTML, and screenshots

Title option 2

Show HN: StitchFlow – a portable Stitch workflow for Codex, Claude Code, and more

Body draft

I built StitchFlow to make Google Stitch easier to use as a practical local workflow instead of only a raw SDK.

It turns product briefs into UI directions, Tailwind-friendly HTML, and screenshots, and it works across Codex, Claude Code, OpenClaw, GitHub Copilot, and Gemini CLI.

What I wanted was simple:
- prompt -> useful UI direction
- local HTML and screenshots the team can review immediately
- one reusable install flow across multiple agent clients

Repo: https://github.com/yshishenya/stitchflow

Would love feedback on:
- install UX
- positioning
- what client support matters most

X / Twitter

Post 1

Built `StitchFlow`: a portable local workflow that turns product briefs into UI directions, Tailwind-friendly HTML, and screenshots across Codex, Claude Code, OpenClaw, GitHub Copilot, and Gemini CLI.

Prompt -> UI -> local artifacts.

https://github.com/yshishenya/stitchflow

Post 2

Most AI UI demos stop at mockups.

I wanted something more practical:
- reusable workflow
- local HTML
- local screenshots
- variants + edits
- support across multiple coding agents

So I built `StitchFlow`.
https://github.com/yshishenya/stitchflow

Post 3

Prompt-to-UI is nice.
Prompt-to-local-HTML-and-screenshots your team can review immediately is better.

`StitchFlow` packages Google Stitch into a portable workflow for Codex, Claude Code, OpenClaw, Copilot, and Gemini CLI.

https://github.com/yshishenya/stitchflow

Reddit

r/opensource / r/SideProject

Built an open-source workflow around Google Stitch that turns prompts into UI directions, Tailwind-friendly HTML, and screenshots.

The main thing I wanted was not just generated screens, but local artifacts a team can review immediately.

It works across Codex, Claude Code, OpenClaw, GitHub Copilot, and Gemini CLI.

Repo: https://github.com/yshishenya/stitchflow

Would love feedback on install UX, positioning, and what ecosystem support matters most.

r/webdev / design-engineering angle

I built `StitchFlow` to make prompt-to-UI workflows more practical for product/design engineers.

Instead of stopping at a mockup, it saves local HTML and screenshots, supports edits and variants, and works across several agent clients.

Repo: https://github.com/yshishenya/stitchflow

Curious what matters more here:
- cleaner HTML output
- better prompt recipes
- faster iteration loops
- stronger install UX

Discord / Telegram

Сделал `StitchFlow` — portable local workflow вокруг Google Stitch.

Что даёт:
- prompt -> UI direction
- локальные HTML и screenshots
- edits / variants
- работа через Codex, Claude Code, OpenClaw, Copilot и Gemini CLI

Репо: https://github.com/yshishenya/stitchflow

Если интересно — потестируйте install flow и скажите, где больше всего трения.

DEV / blog intro

Google Stitch is powerful, but most teams still need a practical workflow around it.

I built `StitchFlow` to bridge that gap: it turns product briefs into UI directions, Tailwind-friendly HTML, and screenshots, saves artifacts locally, and works across multiple agent clients instead of one locked-in tool flow.

FAQ snippets for replies

What makes it different?

The raw SDK is flexible, but StitchFlow focuses on the workflow layer: installability, prompts, reusable skill packaging, local artifacts, and cross-client support.

Why local HTML and screenshots?

Because teams usually need artifacts they can review and build from immediately, not only a hosted generation experience.

Who should try it first?

Product/design engineers and agent builders are the best first-fit users.