Skills, workflows and automations I built, and the board I drew for each one.
A skill is a set of instructions an AI follows for one kind of job, like adding an order or building an ad.
A workflow is several steps with a check between each one, so nothing moves on until it passes.
An automation is something that runs on a schedule without me.
I spent a month watching AI fail the same way, and I kept guessing at fixes, changing three things at once. So I thought, okay, what if every fix is an experiment? I write the pass line first, test it with fresh chats and reviewers who can't see the answers, and change one thing at a time. A no-AI checker caught 93% of planted defects in 13s with 0 false alarms.
Testing a way of working. The steps in order:
To add an order or check a vendor payout, I had to re-explore the backend every single time. So I started asking in plain words, and the AI shows me the numbers first. Now every change is a dry run, then I confirm, then it reads the record back from live data. I ask in one sentence, and nothing goes live without a preview.
Running operations by chat. The steps in order:
A system only I can run isn't much use to anyone else. I wanted another person's AI to be able to rebuild it for them, after asking a few questions about their situation. It asks first, writes a blueprint, and the person confirms it before anything gets built. 8 skills are packaged this way, and the same ones run on both my computers from one synced folder.
Packaging a system for someone else. The steps in order:
On Vizi, my AI chats lost memory 115 times, and most of my "I told you before" moments came from that. So I moved the truth out of chat and into files, set the rules before any page gets drawn, and had every page checked before I saw it. After I approve, it's built to match and handed over through issues. Blind receivers scored 7 of 7 from the issues and 2 of 7 from the first email.
Redesigning a product. The steps in order:
Wiring a design to real data is where the design gets lost, and AI will happily edit the design until a check passes. So now I bring the design in unchanged, measure it, and give one worker one item at a time, with a separate auditor checking each. Questions about the design come to me in a batch. It loops until the checks find nothing. 547 of 547 screens identical to the board.
Building to match a design. The steps in order:
Technical risk in a live product is usually a feeling, not a list, and I wanted a list engineers could act on. So AI inspects the code and the infrastructure, each problem gets written down on its own, and they're ranked into stages. The engineers repair from the top. I direct it and decide the order. It became a ranked repair plan for the engineers.
Auditing a codebase with AI. The steps in order:
Most recurring work is plain code, and running it through AI just burns tokens. Why not run the job on my own machine, and let the AI wake up only when a flag fires? The cheapest model that can do the job leads, and I clear its memory before it gets heavy. A build chat that let a no-AI checker do the checking used 30% fewer tokens with no false "done".
Spending AI only where it counts. The steps in order:
An AI that builds something will often tell you it's done, and I kept seeing "done" mean "I changed something", not "it works". So I had a different AI review it, against checks written for that change, and if it fails it goes back to the builder. A person still signs off. Independent review has sent real work back to the builder with fixes.
Two AIs, one checks the other. The steps in order:
AI is good at judgement and unreliable at counting. In my tests, reviewers listed only 4 of 10 defects, even when I asked for one. So I split every check in two: a plain program counts the mechanical stuff, and the AI only judges what needs judgement. Look checker: found 6 of 6, 0 false alarms. The old checker found 2 of 6.
Programs check the AI. The steps in order:
My dashboards disagreed with reality. Analytics showed zero purchases, and the payment processor only sees the payments that succeed. So the database itself became the source of truth. I set up a live copy of it, defined an order once, and now every dashboard reads from that copy. It also showed me three traps I'd never have spotted.
One live copy of the data. The steps in order:
Searching for a job by hand is slow, and most of it is finding roles and checking they're still open. So I did the search by hand once, then built it. Overnight it finds roles, screens them, checks they're live and finds a contact. In the morning an AI applies, using only facts from one master document. It applies to 20 a day, and it gets more interviews than applying by hand.
A job search that runs overnight. The steps in order: