Back to articles
Stop Repeating Yourself. Stop Repeating Yourself. No, Seriously — Put It in a Skill.

Stop Repeating Yourself. Stop Repeating Yourself. No, Seriously — Put It in a Skill.

via Dev.toMladen Stepanić

In my last post I talked about how the workflow is the work, how designing the pipeline matters more than any individual prompt. I still believe that. But I've now hit the next layer of the onion: what happens when the pipeline itself becomes repetitive? I've been using Claude Code across five projects. A React + Hono book inventory app, a legacy .NET modernization, a Swift macOS menu bar utility, a Rust audio DAW, and a Rust TUI for task visualization. Different languages, different domains, apparently very similar habits. And I didn't notice until I asked. The Prompt That Started It Credit where it's due. Chintan Turakhia posted a tweet , "Run this prompt frequently. You're welcome.", with a screenshot of a Claude Code prompt: scrape all of my claude sessions on this computer. give me a breakdown of all the things i do, things that are worth making into skills vs plugins vs agents vs claude.md So I did. My version had typos, his didn't, but the idea was the same: ask Claude Code to i

Continue reading on Dev.to

Opens in a new tab

Read Full Article
2 views

Related Articles