Merch Drops6 min readMarch 24, 2026

How to Build an AI Wardrobe — The Essential Collection

From prompt engineer to AI whisperer, your closet should communicate what you actually do all day. Here's how to curate the essential developer wardrobe without looking like you wandered out of a stock photo.

Let's be honest: your current wardrobe is probably letting you down. Not in the classic I-have-nothing-to-wear sense — I mean your t-shirt game is mid. You own three variations of the same muted graphic tee you bought at a conference you barely remember, and one hoodie that's seen more deployments than your CI/CD pipeline.

It's time to curate an AI wardrobe. The essential collection. The drip that says I don't just use AI — I have opinions about it.

The Philosophy: Wear Your Tech Stack

Before we get into specific pieces, let's talk strategy. Your wardrobe is a communication layer. When you walk into a standup meeting, the room is reading you before you say a word. A well-placed t-shirt is a conversation starter, a flex, and a vibe check all at once.

The AI-culture closet isn't about brand signaling for tech bros. It's about identity. You're not just someone who writes code — you're someone who lives at the intersection of Large Language Models, deployment anxiety, and the eternal question of whether AI will replace your job before lunch.

That's worth celebrating.

The Foundation Pieces

Every solid wardrobe starts with a foundation. For the AI-curious developer, that means understanding your core aesthetic. Are you a "I use vim for everything" minimalist, or a "my dotfiles repo has 47 stars" maximalist? Both are valid. The key is intentionality.

Wardrobe tiers:
  ├── Foundation: Statement tees (2-3)
  ├── Rotation: Casual AI-culture pieces (3-4)
  ├── Flex: Limited drops and rare finds (1-2)
  └── Emergency: Conference tees you can't throw away (unquantifiable)

Start with one or two statement pieces that capture your actual relationship with AI. Not the relationship LinkedIn thinks you have — the real one. The one where you're equal parts excited, terrified, and deeply skeptical about what GPT-n will mean for your side project.

The Got Tokens Collection

Let's talk about the elephant in the room: tokens are expensive, tokens are everywhere, and the entire generative AI economy runs on the assumption that we keep feeding quarters into the machine.

The got-tokens design is the foundation piece your wardrobe is missing. It's minimalist enough to wear to a client meeting, ironic enough to make your Slack buddies laugh in the group chat. It captures a universal truth about modern development: we're all just token accountants now, watching our API bills like hawk-eyed parents at a Las Vegas casino.

Pair it with dark jeans and clean sneakers. That's the move. You're signaling competence without trying too hard.

The Sam Altman Owes Me Shirt

This is the piece that starts conversations. The sam-altman-owes-me design walks the razor's edge of tech humor — it's specific enough to be insider, vague enough to be universally relatable.

Here's the thing: we all have a running tab with Sam Altman. Every time an AI model hallucinates something confidently wrong, every time your copilot suggests a function that doesn't actually work, every time you ask for refactoring help and get back something that looks like it was written by a confused intern who's also a language model — that's time you could bill to a cosmic Sam Altman tab.

This shirt is for the developers who've been in the trenches. You know what it means. And the people who don't won't ask — they'll just nod and move on, which is exactly what you want.

Dangerously Skip Permissions

This is the piece for the rebellious ones. The dangerously-skip-permissions design is for when sudo became a lifestyle, when "it worked in dev" is your personal philosophy, and when your risk assessment methodology involves pressing buttons and hoping for the best.

Let's be real: every developer has that moment. You're in prod, something's broken, and the fastest path to resolution involves typing something you probably shouldn't type. The skip-permissions mindset isn't about being reckless — it's about velocity. Sometimes you need to move fast and break things, and this shirt is your armor while you do it.

Wear it on days when you have prod access and a deadline. Wear it when you're the only one who knows how the legacy system actually works. Wear it when you're about to make a decision that will either save the sprint or become a legendary post-mortem story.

Building Your Rotation

The mistake most developers make is treating their wardrobe like an afterthought. They grab what's clean, repeat outfits until hygiene becomes a concern, and wonder why their personal brand feels undefined.

Here's a rotation strategy that actually works:

Monday: Got tokens tee. It's the beginning of the week, your calendar is already full of meetings, and you need something that says "I understand the economy we're operating in."

Wednesday: Sam Altman owes me. Mid-week hump day energy. You've hit your third unexpected AI quirk of the week and you're processing it with humor.

Friday: Dangerously skip permissions. End of sprint, potentially risky deploy, weekend on the horizon. Go big or go home.

The other days? Mix in conference tees you can't throw away, standard developer gear, and whatever helps you feel like a functional human. Nobody's grading you on daily outfit variety.

The Deeper Truth About Developer Fashion

Here's what nobody tells you: the clothes don't make the developer, but they do make the developer feel something. There's power in a good tee. The right design at the right moment can shift your energy, remind you of your actual priorities, and make an abstract job feel more concrete.

AI is weird. It hallucinates, it hallucinates confidently, and it occasionally produces something genuinely magical. Your relationship with it deserves a wardrobe that reflects all of that complexity — the humor, the skepticism, the excitement, the mild existential dread.

The got-tokens shirt captures the economic absurdity. The sam-altman-owes-me shirt captures the cosmic joke. The dangerously-skip-permissions shirt captures the reality of actually shipping things.

Together, they form a complete statement about what it means to build software in 2026.

Final Thoughts: Your Wardrobe, Your Brand

You spend more time in meetings about AI strategy than you do picking out outfits. I get it. But here's the thing: your wardrobe is a long-term investment in how you present yourself to the world, and the dev community specifically rewards authenticity.

The pieces above aren't just shirts — they're conversation pieces, identity markers, and low-key flexes all at once. They're what you wear when you want the room to know you're not just another dev who thinks ChatGPT is magic. You're someone who's been in the trenches, who has the battle scars, who knows that tokens add up and that Sam Altman probably does owe you something.

Build the wardrobe. Rotate with intention. And for the love of all that is holy, don't wear the dangerously-skip-permissions shirt to your performance review.

Your AI wardrobe awaits. Go build something good-looking.

Mentioned in This Post

Keep Reading