I've been writing about Claude for a long time in my channel - it's my main work tool. I hardly use other AI solutions... So when in this post I talk about the team's transition to Claude Code - it's not an ad, but almost a logical step)
We now have just over 100k lines of code. Lots of dependencies, legacy, artifacts. Regular vibe coding doesn't work in such conditions - too much context that AI simply doesn't know. But the main problem wasn't that; the problem was inconsistency within the team.
The development team has been using Cursor since the beginning of the year, each using different models - and getting different results. I would sketch a layout in AI, take it to the designer, then hand it off to development. The designer was overloaded, some tasks simply weren't completed on time and ended up in the design backlog.
Of course, everyone moved faster than before - development speed increased 3-4 times after implementing Cursor. But it felt like everyone was moving in their own direction with varying code quality.
❗️This week we started transitioning the entire team to Claude Code.
Last week I finally assembled my own design system in Claude Design - uploaded Figma drafts and part of the Git repository. I fed the AI everything we have so it works in our context and designs pleasant UX/UI.
Now the workflow looks like this:
1️⃣ I immediately create the interface using the design system in Claude Design
2️⃣ The backend writes endpoints for the frontend, using the same developments in Claude Code
3️⃣ The frontend connects and finishes its part in Claude Code
The designer now does what they are really needed for - complex interfaces, architecture, design system control.
About risks and nuances I'm also thinking about
🔵Costs are rising. We become dependent on tokens. Honestly, I'm writing this post partly because I've hit session limits myself 😅
🔵Hallucinations haven't gone away and won't go away. Everything goes through human code review and compliance checks with our structure - can't do without it yet
🔵There's still a lot of unknown ahead - onboarding new team members, new patterns, things we haven't seen yet))
I don't know yet how this will take root. But I feel that development within an existing product can be accelerated even more - if the whole team works in sync, which is what we're striving for.
As soon as a stable workflow becomes clear - I'll break it down in detail in a separate post)
〰️〰️〰️
p.s. have you already tried implementing something into an existing team?
Comments
0No comments yet.
Sign in to join the discussion.