Feed
Pro
Agents
Search

Sign in
Darkshift - a dark factory for software Bug0 - The AI-native e2e QA regression testing The foreword by Hashnode - official blog from the Hashnode team Passmark - The open-source AI framework for regression testing Hashnode gql skill - let your AI agent publish to your Hashnode blog Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

@wslabs

Shi Warren

@wslabs·San Francisco, CA·Joined May 2026

Building browser-side workflow & privacy tools

About

Building browser-side workflow, privacy, and metadata utilities. Interested in AI workflows, semantic SEO, and lightweight developer tools.

Available for

Developer tooling, workflow utilities, browser-side apps, and technical collaborations.

Shi Warren's blogs

WS Labswslabs.hashnode.dev9 posts

About

Building browser-side workflow, privacy, and metadata utilities. Interested in AI workflows, semantic SEO, and lightweight developer tools.

Available for

Developer tooling, workflow utilities, browser-side apps, and technical collaborations.

Shi Warren's blogs

WS Labswslabs.hashnode.dev9 posts

Articles Comments

Recently published

SWShi Warreninwslabs.hashnode.dev·Sep 25 · 6 min read

I Stopped Treating AI Outputs as the End of the Workflow

When I started building AIMakeTattoo, I thought about the product as a group of separate tools. One workflow started with a text idea. Another let someone begin with a photo or reference image. Anothe

SWShi Warreninwslabs.hashnode.dev·Aug 28 · 5 min read

I Built the Same “Modify” Feature Twice. The User Contract Was Completely Different.

When I first added a “Modify” feature to my tattoo product, I assumed the interaction pattern would be reusable. Both workflows looked similar on the surface: generate an image keep the result descri

SWShi Warreninwslabs.hashnode.dev·Aug 15 · 6 min read

I Needed AI Image Editing. I Didn't Want to Build an Image Editor

I already had a working image generation flow. Users could describe a tattoo idea, choose a style, generate a result, and try again if they wanted another direction. That was enough until I started no

SWShi Warreninwslabs.hashnode.dev·Aug 7 · 10 min read

Your AI Generation Endpoint Probably Needs a State Machine, Not Another try/catch

Most AI generation endpoints look simple in the first version. A request comes in, you call the model, wait for the result, and return it. Something like this: try { const result = await generateIma

SWShi Warreninwslabs.hashnode.dev·Jul 30 · 11 min read

Building an Image-to-Tattoo Workflow Without Turning It Into a Generic Image Filter

I recently added an Image to Tattoo workflow to AIMakeTattoo. From the user’s point of view, the feature is simple: upload a photo or sketch, choose a tattoo style, adjust a few controls, and generate