Returns

The Regenerate Guarantee

Every design in our store ships under one system-level instruction: if it doesn't land, it doesn't ship. That's the standard your gear clears before it ever touched a shelf.

But we've all been there. The prompt was clean. The intent was clear. And the output still missed. That's not failure, that's iteration. So, we built our return policy the way you'd build a good workflow: with a regenerate button.

How It Works

You get a 30-day context window, starting the day your order is delivered.

If your swag isn't what you expected, fit, feel, vibe, anything. Send us a message via our contact page with your order number. That's it, that's the entire prompt. One line of input.

We handle everything downstream:

We pay the return shipping. All of it. Bad output should never cost you tokens.
Your refund processes within two business days of the item landing back at the Forge. Not "up to." Not "please allow." Two, as in a finite number.

The Constraints (Stated Up Front, Where They Belong)

You know what a well-specified prompt looks like, so we're not going to bury the parameters in fine print:

Returns must be initiated within 30 days of delivery. After that, the context window closes.
Printed pieces that have been worn or washed are out of scope. Once you've run inference on it, it's yours.

That's it. Two constraints. No hidden system prompt, no adversarial edge cases, no dark patterns. If a policy needs a lawyer to parse, it was written to be misunderstood.

Why We Do It This Way

Because you don't fine-tune trust. You either ship it in the base model or you don't have it.

We know exactly who you are: someone who tests before deploying, who reads the docs, who deletes anything that doesn't perform. Your closet should work the same way your prompt library does, ruthlessly curated, zero filler.

We wouldn't have it any other way.

Every prompt has to earn its output. Every piece has to earn its place in your wardrobe. Ours will, or it comes back on our dime.