
"I gave a webinar presentation titled 'Current Status of Claude Code Team Utilization - Small Practices and Future Prospects'"
Content Discussed
I spoke at the following webinar. Following the previous beginner edition, this is the practical edition of the Claude Code seminar.
The materials are as follows:
Additional Notes
It may be commonplace, but monorepos make it easier to align contexts. While you can get information from other directories using /add-dir
, features like @symbol search are still in development, so I think it's still evolving.
Related to the above, here's an example of efficiently editing ecspresso's ECS task definition using @symbol search after setting app environment variables in a monorepo.
I introduced two simple examples of reducing toil with Slash commands!
PR creation slash command:
This has been well-received within our team, and we've really felt how slash commands help reduce team toil! Thanks to team members who tried it out 🥰
A slash command for fixing static analysis issues that Claude often makes mistakes with. Since generic static analysis fix tasks will continue to arise, creating Claude Code Slash Commands benefits the entire team.
I recommend setting up .rgignore
in your project for more efficient @file symbol searches.
Regarding using Hooks to automatically fix static analysis issues:
I've also explained this in the following article, so please refer to it:
I also explained the technical points of interest about Serena MCP!
I explain what I want to try next from page 28 onwards!
In Conclusion
Although I'm still a 🔰 beginner, I talked about cases where we use it as a team! I think the later parts I wrote about are common team challenges, so accumulating practices using generative AI could become good case studies!
Thank you for all the reactions and questions during the webinar! There were nearly 50 questions, which really showed how much interest there is in this field!
Events are also scheduled for 9/16 and 9/26, so please join if you're interested!