CyWire Master Prompts

Brett Snyder — Sat, 16 May 2026 21:01:51 +0000

Yes, another SaaS sent into the wild. Another prompt builder? Not quite.

I built CyWire first as a foundational resource for myself last year. I wanted a way to create AI features for future websites without rebuilding the same prompt structure every time.

The goal was simple: take variable-based user inputs, run them through a reusable Master Prompt, and get back reliable structured data that an app, website, or platform could actually use.

A CyWire Master Prompt is basically a reusable AI feature blueprint. It defines the input variables, instructions, output structure, and expected scope so the LLM returns data in a format the platform can work with.

That was the goal, anyway.

The input engine and Master Prompt generator were rebuilt several times before they worked the way I wanted. To test the concept, I created two Master Prompts in CyWire:

One to create a micro-lesson on any subject.

One to create a course scaffold on any subject.

Then I built PushPad.com as a test bed for both.

I added the CyWire-generated Master Prompts into the PushPad codebase, used AI to wire the variables from the user input forms, and connected an LLM to the full prompt section.

It worked.

I have not gone back and finished all the frontend features on PushPad yet, but the structured output came back the way I expected.

But I need to back up, because it was not that easy at first.

My first version used a seven-step Master Prompt flow. Seven prompts. It had everything I could imagine an educator might want.

I could get through a few steps, but the costs started climbing fast. The output started drifting. Memory use and token caps became a problem. The quality I wanted was expensive, and the generation time was rough.

So I had to backtrack. Then start over. Then start over again.

Eventually, I scrapped the multi-step workflow entirely. Each step could block progress that had already been made, and each step needed to be smaller than what I actually wanted.

The best balance ended up being one strong Master Prompt.

That gave me the best bang for the buck and the most consistent output.

I removed the large few-shot examples and created my own tiny micro-shot examples instead. I tightened up the variable names, fixed consistency issues, and found the right sections and lengths to compile into the final full prompt.

After that, I deleted all my old test prompts and had the system generate 340 Master Prompts.

Out of the 340 generated, only five had to be regenerated and edited. In each case, the issue came from input that was too general and allowed nested looping. Tightening the input fixed it each time.

I also added a free community section where people can donate their own Master Prompts, plus a marketplace where people can sell them. You can just post a link to your items.

Sure, there are probably ways someone could exploit that. But really, I built this because I wanted a better way to create Master Prompts the way I wanted them, without rebuilding the same approach over and over again.

Free accounts for free master prompt downloads are open if any devs want to try it and give feedback:

CyWire.com

PS: Since this is a dev forum, message me and I will be happy to give you Pro access to test the ai features out for a bit.

Hello World

Brett Snyder — Sat, 16 May 2026 20:54:22 +0000

Hey there! Glad to be here.

DEV Community: Brett Snyder

CyWire Master Prompts

Hello World