Brandon Gains

@NerdJey & I have been hosting founder dinners in Victoria for the past couple years. A third space where builders actually connect. No sales. No pitch decks. No forced networking. Just put cool people in a room and let the universe do its thing. DTC, SaaS, & Agency founders

A rough idea became a doc an engineer could read cold and know exactly what to build in one prompt. Not because Claude is magic. Because the skill is designed to ask the right questions, flag the right gaps, and write for the person who wasn't in the room. That's what a good PRD is supposed to do. Want this PRD Claude skill? Comment PRD and I'll share it with you - (must be following)

Bad PRDs get shared before they're ready. Someone fills in a template, sees it looks complete, and sends it to eng before Revenue has signed off on the tier limits. The ASSUMED callout system exists to stop that. It's a forcing function.

Most PMs write PRDs that read like meeting notes someone formatted. Vague problem statements. "TBD" everywhere. Nothing a senior engineer could actually build from. I built a PRD generator skill for Claude that turns a rough idea into a dev-ready doc. Here's what that actually looks like 🧵

My Anti AI Design Claude Skill on GitHub github.com/brandonsgitstu…

I'm sharing the skill if you want to fork it yourself. Take the base frontend-design skill in Claude → add your own blacklist, your own aesthetic principles, your own typography rules. Make it yours. That's the whole point. You can DM me for the HTML of the Claude redesign

I customized a Claude skill that kills AI slop in frontend design. Fed it a single prompt: "Reimagine @openclaw as a brutalist SaaS product." This is what it built. No templates. No purple gradients. No sparkle icons. 🧵

@Jacobsklug @openclaw @Lovable OS

I'm giving away my entire @openclaw architecture. Behind my $250k/month agency. After weeks of building, I've dialled in the exact system that runs my business 24/7. What's included: • Memory folder structure (how to organize agent context) • Cron job templates (daily briefs, meeting syncs, content automation) • How to build a custom dashboard in @lovable • API reference doc (so your agent never forgets its tools) • Voice training method (85 posts to teach it your style) • Supabase schema for dashboard connection Comment "OS" and follow. I'll DM it to you. P.S. This will probably blow up so give me some time to reply.

@mikefutia Agent

Anthropic just shipped Agent Teams into Claude Code and it completely changes how you run creative research and campaign workflows 🤯 OpenClaw has been blowing up up. 140K+ GitHub stars in a week. Everyone’s trying to configure multi-agent setups with it right now. Custom skills, MCP integrations, environment variables, Docker containers. It works. But let's be honest: it’s unnecessarily complicated for what 99% of business owners actually need. Anthropic saw the demand and made it native. No Mac mini, no VPS, not 6-hour installation setup. Instead, they built right into Claude Code. Here's how it works: Instead of one agent doing everything solo in a straight line, a lead agent breaks your task into pieces, spins up multiple teammates, and they all work on different parts of your project at the same time. One researches competitors, one audits your landing page, one analyzes ad creative. They talk to each other, share findings, and coordinate through a shared task list without you managing any of it. This is different from sub-agents. Sub-agents can only report back to the parent. They can't message each other or share discoveries mid-task. Agent teams can. That's the unlock. Best use cases I'm seeing for e-comm and agencies: → Competitor ad research across Meta, TikTok, and YouTube in parallel → Landing page QA from 4 angles at once (conversion, performance, copy, technical) → Creative brief development where audience research, competitive analysis, and concept ideation happen simultaneously → Product catalog audits where 4 agents each handle a segment of your SKUs → Campaign launch QA checking pixels, UTMs, forms, and compliance at the same time The catch: It's experimental. It burns through tokens fast. Each teammate has its own context window so usage scales with team size. But for complex marketing workflows where parallel work actually matters, it's a game changer. I put together a complete breakdown covering: → What agent teams are and how they actually work → How they're different from sub-agents (and when to use which) → How to enable them in your settings in 30 seconds → Copy-paste prompts for competitor research, landing page QA, and creative briefs → Best practices so you don't burn through tokens → The limitations you need to know before you start This is one of those features that sounds small on paper but completely changes how you run research and QA once you start using it. Want access completely for free? > Like this post > Comment "AGENT" And I'll send it over (must be following so I can DM)