Live online workshop
Claude Code for Teams: one way of working for every developer's agent
Give every developer's Claude Code one way of working: a short shared instructions file, checked-in settings, a hook that blocks what must never happen, and a reviewer agent. Built on your own repo. Live online on Google Meet, 2 days, 3 hours a day, small group.
Acquis
You will leave able to
- Replace a long, ignored instructions file with a short root CLAUDE.md / AGENTS.md that holds only the always-on rules and routes to your standards.
- Check in shared project settings (.claude/settings.json): permissions and MCP servers every developer gets, separate from personal settings.
- Write a hook that blocks a command your team must never run, puts the remedy in the block message, and is tested both ways.
- Build a reviewer subagent that checks a diff against a list of standards locked before the work started.
- Package a procedure the team repeats as a skill or a slash command.
- Decide where each new lesson goes (hook, root file, standard, folder file, memory) with one decision table.
- Write a rollout plan that gets the setup onto every developer's machine through one merge request.
Pour qui
Built for
- Engineering leads with 5 to 30 developers using Claude Code: every developer's agent behaves differently, and you own the result
- Senior developers asked to "set up AI for the team": you need a setup the team adopts, not a personal config
- CTOs and technical founders at small product companies: you want one way of working before the team grows
Dates
Upcoming dates
- mar. 19 janv.09:00–12:00
- jeu. 21 janv.09:00–12:00
Heure de Dublin · Anglais En ligne
12 places · a lieu dès 4 inscrits
Places disponibles845,00 €
TVA comprise
Prix
Price
845,00 €jusqu’au 30 déc.
TVA comprise
puis 995,00 €
Équipe de 5 : 3 980,00 €
Programme
Agenda
Module 1
Day 1, 0:00 to 0:20: Where behaviour drifts
Module 2
Day 1, 0:20 to 1:20: Cut the instructions file
Module 3
Day 1, 1:30 to 2:30: Settings and the first hook
Module 4
Day 1, 2:30 to 3:00: Review and homework
Module 5
Day 2, 0:00 to 0:20: Homework debrief
Module 6
Day 2, 0:20 to 1:20: A reviewer subagent
Module 7
Day 2, 1:30 to 2:20: Skills, commands and shared MCP
Module 8
Day 2, 2:20 to 2:50: Roll it out
Module 9
Day 2, 2:50 to 3:00: Q&A and close
Formateur
Your trainer
Votre formateur
David Marsa
Founder of Neomanex. Builds agent-run software companies: ConvOps, Gnosari and the Neomanex directory. Teaches the workflows he runs his own company on.
Cours
Related workshops
Read before you come
Questions fréquentes
Questions
What is the Claude Code for Teams workshop?
Claude Code for Teams is a live online Neomanex workshop for engineering teams that already use Claude Code. Over two 3-hour sessions on Google Meet, each attendee builds a shared setup on their own repo: a short root instructions file that routes to standards, checked-in settings, a tested hook, a reviewer subagent and a rollout plan. Neomanex runs its own products on the same setup.
Who should attend Claude Code for Teams?
Neomanex built Claude Code for Teams for engineering leads, senior developers and technical founders whose developers each run Claude Code differently. You should have used Claude Code on real work for a few weeks. A team of five gets 20% off each seat, which suits a lead plus the developers who will maintain the setup.
What do I need installed before day 1?
Neomanex asks every attendee to arrive with Claude Code installed and signed in, git, a terminal, an editor and a repo you can change on a branch. Claude Code needs a Claude plan or API key that includes it. If you cannot bring your team's repo, Neomanex gives you a sample repo, so every exercise still runs end to end.
What time are the Claude Code for Teams sessions?
Neomanex runs Claude Code for Teams in two slots. The Europe slot is 17:00 to 20:00 Malaysia time, which is 09:00 to 12:00 in Dublin and London in winter and 10:00 to 13:00 in summer. The APAC slot is 10:00 to 13:00 Malaysia and Singapore time. The runs table shows every date in your local time.
Can I get a refund, or send a colleague instead?
Neomanex does not refund Claude Code for Teams seats. You can send a substitute attendee for free: tell Neomanex the new name and email before the first session, and the seat, the recordings and the certificate move to them. Anything outside this policy is handled case by case by writing to Neomanex.
Are the Claude Code for Teams sessions recorded?
Yes. Neomanex records both sessions and sends the recordings to the attendees of that run within 24 hours. The recordings show the trainer's screen and the group discussion. They support the live sessions and are not sold as a separate product.
Do I get a certificate for Claude Code for Teams?
Neomanex issues a certificate of completion 24 hours after day 2 to attendees who joined both sessions live. It names the workshop, the dates and the trainer. It is a Neomanex certificate, not an accredited qualification, and it does not count toward any training funding scheme.
How is this different from the Govern course on Neomanex Learn?
Govern is a self-paced Neomanex course that teaches one way of working for coding agents in nine lessons. Claude Code for Teams is live: you build the setup on your own repo with the trainer watching your diff, you add subagents, skills and shared MCP settings, and you leave with a rollout plan for your team. Govern works as pre-work or as a refresher.
What happens if the run does not reach its minimum?
Neomanex confirms or moves each Claude Code for Teams run 7 days before day 1. If the run is below its minimum size, Neomanex emails every buyer that day and moves their seat to the next run at no cost. If the next date does not work for you, write to Neomanex.
Neomanex is not affiliated with Anthropic. Claude and Claude Code are trademarks of Anthropic.