Claude Code consultant

You've seen what Claude Code can do on your own projects, and now your whole development team should be working with it. The team runs from seniors who have done the job for decades to juniors on their first, and you don't want to lose either of them on the way, with the seniors frustrated that the job changed or the juniors working with something they can't see into.

• Claude Code set up on your codebase, with project instructions that tell it how your team builds, tests and names things.
• Skills for the jobs your team repeats, such as a release, a migration or a new endpoint, written with the developer who does each one best.
• Connectors to the tools your team already works in, such as GitHub, your issue tracker and your docs.
• Claude Code reading new issues and drafting a plan before anyone starts, on the work that suits it.
• A review process for what Claude Code writes, so every pull request is read by someone who understands it before it merges.
• Hands-on sessions with your developers on their own tasks, the seniors and the juniors each starting from where they are.
• The whole setup written down in your repo, so a new hire picks it up on day one.

1. You walk me through how your team builds, from the first issue to the release.
2. I set Claude Code up on your codebase, with the instructions, skills and connectors your team needs.
3. Each developer works through real tasks with it alongside me, and the setup is tuned on what comes up.
4. The setup lives in your repo, and your team runs it from there.

My own team builds with Claude Code every day, on LGTM, an open-source framework I built. It breaks a request into issues, has Claude Code work on them in parallel, and puts every change in a pull request that a person reviews before it merges. It's on GitHub, so your team can read how it works before we talk.

For the teams outside engineering, Claude Cowork and the skills they use are on Custom Claude skills.