Tag
#claude-code
The Skills I Actually Kept: My Claude Code Skills, and What I Use vs Build
The Claude Code skills I actually kept — article drafting, a full deploy pipeline, design-system contracts, self-testing — and the one rule I use to decide when to reuse a pre-built skill versus write my own: who's going to maintain it in six months.
UI Thrashing: The Reset Protocol That Actually Works
When AI-driven UI coding turns into an endless loop of micro-tweaks, don't negotiate with the model — kill the session, max the thinking effort, resend everything, and let it plan without more questions.
Claude Chat, Claude Co-Work, or Claude Code: How to Know Which One You Actually Need
The three tiers of working with AI — Claude chat, Claude co-work, and Claude Code — and the exact signal that tells you when it's time to move up a level.
When GSD Became the Bottleneck, I Built Something Lighter
GSD asks a lot up front and forgets what it asked — great for serious multi-phase builds, terrible for rocket-ship mode. Here's the lightweight way of working I reach for instead: high effort, a two-item plan, round-based questions, big-bang execution, and two skills that auto-run the UAT.
MCP, Skills, Commands, Agents: A Product Manager's No-BS Guide to AI Buzzwords
A product manager's plain-language explanation of MCP, Skills, Commands, and Agents — revisited with the repo habits that came out of actually living with them: a docs folder as memory, granular Skills over plugins, CLI over MCP where it counts, and picking a model per task.
My AI Coding Stack: A Practical Guide to Using ChatGPT, Cursor, Claude Code, and Lovable
An evolving, practical AI coding stack — ChatGPT, Cursor, Claude Code, and Lovable — updated with how I now default to the Claude Code CLI, route Opus, Sonnet, and GPT to different jobs, and why I dropped Fable.
The Skill That Stops Claude From Forgetting Your Tasks
A new skill that turns a raw, unstructured brain-dump into a forced checklist of tasks for Claude — and makes it report back exactly what it did.
Fable vs. Opus: My Token-Budget Verdict
I burned through two paid Max accounts in three days switching to Fable. Here's why I went back to Opus, and where Sonnet actually wins.
Let AI Test Its Own Work: A UAT Loop With Claude Code and Playwright
The practice I use to have Claude Code test its own work with a UAT file, Playwright, and per-persona .env credentials — then ask it to fix what it finds and retest, almost on its own.
If You Want to Ride the Horse, You Need to Speak Its Language: A Non-Engineer's Survival Guide to Git and GitHub
A plain-language glossary and workflow guide to Git and GitHub for non-developers using AI coding tools.
GSD (Get Shit Done): The Framework That Changed How I Build Serious Software With AI
A deep dive into the GSD plugin for structuring multi-phase software projects with LLMs, from planning to autonomous execution and testing.
I Vibe Code Every Day Without an Engineering Team. Here Are the 3 Modes I Switch Between
Three modes of AI coding—auto-edit, planning, and GSD—and how matching the mode to the task drives better results without an engineering team.
Context Is Everything: Keeping AI Coding Agents From Losing the Plot
Why saturating a coding agent's context window quietly wrecks its output, and the docs/backlog/handover system I use to give agents real memory across a multi-repo project.
Permission Modes for AI Coding: Bypass, Auto-Edit, and Planning
Bypass, auto-edit, and planning are three different gears in Claude Code, not one setting — and knowing when to shift into planning is what saved a deploy bug I couldn't fix any other way.
When ChatGPT Is Not Enough: How I Planned an XTerra with AI
Planning an XTerra triathlon revealed why ChatGPT struggles with long projects, and how moving to Claude Code with files and MCP fixed memory and dates.