{{ p.name }}
{{ p.tagline }}
I’m Anthony — part-time vibe coder and early adopter. I build dashboards, calculators, membership sites, and landing tests by pairing with Claude Cowork, then ship them in the open. Every project comes with a live demo, a case study walking through how it got built, and a one-pager that shows the problem and the outcome.
It started as three scattered sources and a lot of manual cross-referencing. Now it’s one living dashboard that pulls domestic and international outbound travel from NTTO, CVB, and the U.S. Travel Association into a single view — so you can spot where travelers are heading before the crowds do, and watch it refresh as the data does.
{{ p.tagline }}
I’ve got a master’s in internet marketing and a habit of being an early adopter. When I discovered vibe coding with Claude Cowork, it clicked: I could ship real software without the overhead. So I built this site as both portfolio and playground — everything started as something I actually wanted to exist. I work nights and weekends, release in the open, and document the whole process. When I’m not coding, I’m running 5Ks, traveling, hunting new restaurants, or hitting festivals and theme parks.
Every project links to a working demo, a case study, and a one-pager showing problem → solution → outcome.
If you’re building your own Claude Cowork projects, let me know what you’re working on. Just getting started? These should give you some inspiration. Need help building something? Let’s connect.
“Claude doesn’t like being interrupted after it gives you direction. I got so excited by what I saw, but I needed to process all my thoughts first instead of just keeping the chat going.”
“I put my ideas into the lower models, then ask the complex questions as I go. Tip: tell Claude to map out the plan and outline your project before it starts any work.”
“Things are best in Projects — they keep Claude on track, and start a new chat every so often. You can also add chats to a Project later so Claude Cowork can reference them.”
“You can work on multiple projects, but that doesn’t mean you should — it takes up more of your usage. I should have jotted down every project first and asked Claude which would take the least and most time, then used that to decide how to move forward.”
“I’ve pretty much decided my older laptop will be the dedicated computer for Claude Cowork projects. It needs to stay running to process the items I have scheduled and keep the agents going.”
“Try not to ask for many versions at once — two max. I’ve found it’s best to focus on one site or design, let Claude get it right, then easily translate that into the other designs.”
“I have a project that called a lot of sites for research — it ran over 15 minutes and still wasn’t done, using 3 agents at the time. I could have run it in smaller chunks and regions instead of pulling all the data at once.”
“Ask Claude for a plan before it proceeds — it makes sure you know the roadmap it’s taking and can align to each step along the way. Take out any steps you don’t want right now and tell it to save them for later.”
“You can publish and host HTML sites and other projects for free with some providers — and even connect your own domain or use a subdomain.”
{{ u.body }}
{{ u.body }}
New to Claude and want a nudge, curious about a project here, or just want to talk shop? Email my AI inbox — it lands right where it needs to, and I read everything that comes in.
{{ cs.tagline }}
{{ cs.problem }}
{{ cs.solution }}
{{ cs.outcome }}
{{ cs.howBuilt }}
Get an occasional email when I ship a new project — with the case study and a downloadable one-pager. No spam, unsubscribe anytime.