Short claude.md file, skills for various things like db schema, etc
For larger or complex features do a design session with claude, review design and make suggestions and collaborate, once design is dialed in ask to break in to tasks then do similar session collaboarating on plan.md files for each task/phase then have claude build it.
Claude is really really good at adding tests, leverage this for near 100% test coverage and it can also test that it's meeting the PRD/spec.
It's also creative and seems to like collaborating on the design and plan parts join in with that. Claude feels really similar to my favorite engineer I worked with as far as collaboration and even banter. It's nice.
Using claude code in the terminal btw, md files go in repo so all team, devs, consoles can see context across front and backend.
Use PRs run claude code review, I created a Minority Report style review skill as well, code quality, security, performance with anderton as the judge/orch
Then we have a human review PR as well
This process we are getting good code and faster velocity for sure, vs traditional SDLC for solo and with team
As far as reading the code, I think that will become less and less as long as it passes automated code review, it's performant, meets the spec and tests pass . . . SHIP IT
Watch DHH's recent RailsConf keynote, this is where we're heading, buckle up