Activity
Mon
Wed
Fri
Sun
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
What is this?
Less
More

Memberships

AI Automation Society

427.7k members • Free

AI Video Bootcamp

25.3k members • $9/month

Comunidad Fundamentos IA

23.5k members • Free

AI OS

1.1k members • Free

Contenido Irresistible

18.9k members • Free

5 contributions to AI Automation Society
Day 1 — I skipped the newsletter and applied WAT to a real product
I'm building a multi-tenant CRM for beauty salons, so instead of the newsletter I used Day 1 to build the no-show recovery module with the WAT structure: workflow in markdown, a deterministic detection tool, and the agent deciding the recovery strategy per client. The interesting part wasn't the build — it was the bug. I accidentally used a different AI chat inside VS Code (not Claude Code) and it wrote the "decision tool" as a hardcoded if/else with 2 branches. Tests were green. Everything looked fine. I asked Claude Code to audit what the other assistant had built. It found that the tool had collapsed Layer 2 (the agent's reasoning) into Layer 3 (deterministic execution) — exactly the separation WAT exists to protect. An if/else with 2 branches can never produce 10 different strategies for 10 different clients. I decided to rewrite it as a validator: the agent decides at runtime and returns structured JSON, and the tool only checks the schema and allowed values. 11/11 tests green. Two takeaways: - Self-healing catches execution errors, not architectural ones. - Green tests don't mean correct architecture. I needed a second agent to audit the first. Wait your comments, ¡thanks in advance! 🫡
Day 1 — I skipped the newsletter and applied WAT to a real product
@Jason Elam ¡Hey Jason! This is the best note I've gotten. You're right that my tests catch the instance, not the category — especially #3: my allowed values are hardcoded in the validator right now, which means every new strategy touches code and every salon that wants its own templates breaks the abstraction. Moving them to per-tenant config and testing that adding one requires zero code changes. "Knowing which layer is allowed to think" is going straight into my CLAUDE.md. Appreciate you taking the time, man. Grettings from Argentina. 🫡
@Julius Waggoner ¡Thanks Julius! 🫡
n8n / claude / hermes
which tool you guys use mostly? to build skills / automations / general work??
Poll
76 members have voted
Most people talk about hermes agent but I haven't tried it yet. Rise your hand who need more hours a day to learn more about AI 🤪
Zero Editors. 5.2 Million Views. One Client.
A few months back I started building AI content systems for clients, fully automated, no editors, no script writers, no managers, nothing manual. The numbers still surprise me every time I look at them. One reel hit 5,251,777 views. 93.9% came from people who had never seen the account before, meaning 2.8 million completely new accounts discovered the brand through content alone. No paid ads. No cold outreach. Just consistent content the algorithm kept pushing because it never stopped running. That same system generated 42 inbound leads and helped close $25,800 in business across four different clients. Here's the actual lesson in this. Most businesses don't have a content problem, they have a consistency problem. Remove the human bottleneck and the algorithm rewards you for showing up every single day without fail. AI doesn't get tired. Doesn't take a sick day. Doesn't forget to post because life got busy. That's the whole system. If you want to see exactly how this works, drop a comment or send me a DM.
Zero Editors. 5.2 Million Views. One Client.
¡It sounds great! I want to no more about that, congratulations on the number you reached. 🎸
What do you get if you upgrade to AIS+?
Some of you have never heard of the AIS+ community. Others have but the part that trips you up is the actual difference between the two. Either way, this post will give you clarity. This free group is a bundle of quick resources pulled from my YouTube videos, plus a massive open community that anyone can join. It's a great place to get your bearings and see what's possible. But it's open to everyone, it can be noisy and overwhelming, and there's no path through it. You can get help from other members, but I rarely answer questions here. AIS+ is the opposite: - A step by step roadmap with a clear order, so you're never guessing what to do next - A much smaller community of people who are seriously committed to building and selling AI agents - I answer questions every day and run a weekly Q&A call where you can get direct access to me For the course material: The roadmap takes you from zero to building and selling AI agents, and the whole thing is built on the latest tech like Claude Code and Codex. We update it constantly. The old n8n material has been archived. It's still there if you want it, but it's no longer the focus, because the way you build today has moved on and the courses moved with it. Here's the actual roadmap inside, in order, with when each piece opens up: 1. Start Here (opens the moment you join). Gets you oriented. How the community works, the path ahead, and how to get help when you need it. 2. Build Your Portfolio (opens the moment you join). Why a portfolio matters, beginner level tutorials, and what types of projects to focus on. You end up with real work you can show a client. 3. Claude Code (opens the moment you join). This is now its own dedicated course. Build faster, turn ideas into working automations, and go deep on the tool serious builders are using right now. This takes you from beginner to advanced, step-by-step. 4. Get Your First Clients (opens after 30 days). Getting your first clients is hard, because you don’t have any case studies yet. So, we analyzed all of the success stories from our members and found they get their initial clients with two different techniques: warm outreach and Upwork. So, we teach both techniques in detail with exactly what to say, exactly how to position yourself when you have no proof.
Zero price but massive value. Zero excuses. Let's stop postponing our progress — progress belongs to those who don't postpone. 🫡
🚀New Video: Claude Code for Non-Coders (6 Hour Course)
This is a complete beginner course on becoming AI native with Claude Code, no coding background required. I take you from your very first prompt all the way to building your own skills, sub-agents, a second brain, and automations that run on their own in the cloud. It's all real examples and step-by-step builds, so you can follow along and walk away with AI systems that actually do work for you. Feel free to skip around using the timestamps below to whatever piques your interest.
This community have an incredible value inside. It's a tier one community. ¡I be happy to be here! 😀
@Padaree U. Great question — I was wondering the same thing! From what I understand, it's not that WAT died, it's more that Claude skills absorbed part of it. A skill is basically a Workflow (the markdown SOP) packaged in a format Claude loads natively, so you no longer need to maintain a separate workflows/ folder for many use cases. That said, I think WAT still shines as a mental model, especially when your automation grows beyond a single skill: the moment you have deterministic scripts doing the heavy lifting and the agent just deciding when and how to use them, you're doing WAT whether you call it that or not. The framework is the architecture; skills are just one way to implement the "W" layer. I'm applying it to a SaaS I'm building right now — agent as the brain, code as the weapons — and honestly the separation of concerns is what keeps the outputs reliable. Curious to hear Nate's take too! This community it's great and I hope that leverage our progress. Juan Manuel, for whatever you need 🫡
1-5 of 5
@juan-manuel-alan-pouso-6490
Bajista, Programador en Curso y Técnico en Marketing. ARG 🇦🇷🧉

Active 18m ago
Joined Jul 18, 2026
Powered by