I've been heads-down on a pet project for the last couple months. Along the way I worked through two ideas and ended up wrapping each into a Claude Code skill and publishing them under MIT.
Idea one. Working with Claude Code, I noticed I was missing the kind of production-grade process I had on real product teams — task tiering by complexity, design docs before architectural changes, mandatory smoke tests, code review, a security checklist for sensitive features, a blameless incident log.
Without that, Claude is great at one-liners. But hand it "a new feature across three files" and it confidently writes an architecture you have to clean up afterward.
Idea two — getting ahead of it. I started thinking: how do I make every new project come up already on these rails, instead of me hand-rolling conventions from scratch each time? A boilerplate would help exactly once. Two weeks later, real work would surface new patterns (Sentry, event analytics, feature flags) that didn't make it into the template.
The first idea became dev-workflow. The skill classifies any task into a tier: XS (small — does it itself, smoke test, commit), M (feature — RFC before code, unit + integration tests, multi-agent code review), L (architecture, migration, security — plus /security-review, threat modeling, an OWASP checklist). On M/L, the final commit only happens after my explicit "ok".
In parallel, the skill keeps an incidents.md log in blameless style and scales security incrementally across S1 → S2 → S3 as the project grows.
The second became scaffold-project. It bootstraps a new project in a single conversation: CLAUDE.md (already wired to dev-workflow), an RFC folder, a backlog with the first task, git init, first commit.
The interesting part is the feedback loop. The first time I introduce a new infra pattern in any real project, the skill asks me: "extract this into an extension pack so the next project gets it for free?" I say yes or no. The template grows on its own, instead of me sitting around guessing what else to put in there.
I used to think AI dev tools were about speed. Now I see them more like a junior dev with extremely fast hands but no taste yet: without processes, any quick shortcut becomes debt within a week.
Links to both repos in the comments. If you're working with Claude Code — take them, MIT, symlink them in, edit them to fit.
#ClaudeCode #DeveloperExperience #AI