Mastodawn

I have not done any vibe coding and have a question for those who have.

Suppose you request a change, adding features, changing things around based on learning and testing, which is generally what happens after you've been working on something new.

Here's the question. What happens when you ask for a change that requires the codebase to be reorganized.

How did that go? Do the AIs know that's possible or do they just pile on special cases?

Show thread

Ricardo

@davew I have found that using Obra Superpower plugin/skills is of immense help to do just that, the first thing is to have claude code to map the repo and differentiate between instruction for him in Claude.md and for humans in readme.md
once the repo is properly described and mapped for claude you have your init context right, then for a refactoring or reorg of the code I would use an agent code reviewer to plan (superpower skill) and then only execute the plan once reviewed

Show thread

Ricardo Feb 21

@davew I have tested this approach both at work on a big legacy java repo which contained production code and dev spaghetis code lying around and to refactor personal code projects that I had initially developed with the help of chatgpt, with claude code I refactored and modernized all my custom python apps, it went really smooth, in both case I had to baby sit the process but the result was worth it

Show thread

Ricardo Feb 21

@davew now if you want to see full code implementation of existing specs into a plugin for indiekit made entirely with Claude Code
- microsub : https://github.com/rmdes/indiekit-endpoint-microsub
- ActivityPub https://github.com/rmdes/indiekit-endpoint-activitypub are good candidate, they both went from reading the specs to full blown implementation after dozens of rounds of testing and incremental changes

GitHub - rmdes/indiekit-endpoint-microsub: Microsub endpoint for Indiekit

Microsub endpoint for Indiekit. Contribute to rmdes/indiekit-endpoint-microsub development by creating an account on GitHub.

GitHub