A SaaS team closed its AI coding context gaps with two workshops and moved everyone to one tool
Published
How can AI replace developers each trying different AI tools and models?
- Replaces: Developers each trying different AI tools and models, with:
- poor generated code clogging code review and sometimes forcing rewrites;
- AI misdiagnosing bugs;
- domain knowledge living only in the heads of the people who built each system.
- What to connect:
- Claude Code as the team standard: Rocketspark cancelled all its Cursor licences and moved everyone to premium Claude seats;
- a shared /.ai/ folder of rules and skills, symlinked into .cursor and .claude so it's maintained in one place;
- the Drive connector, so meeting transcripts reach Claude.
- Workshop one, "reverse prompting": each developer asks Claude, based on their last six weeks of git history, which rules, skills or context it was missing. The outputs become a to-do list of context files.
- Workshop two: interview a domain expert on a recorded Google Meet, then have Claude turn the transcript into a skill file committed to the repo.
- Examples: Google Workspace billing and dunning, API middleware, domain reseller and DNS, Nginx/PHP hosting.
- Results: eight internal workshops so far. No cost stated.
- Who it's for: Small software teams on a proprietary codebase where models don't know the house rules, and anyone who wants a shared, versioned skill library for their agents.
From the Morning Tokens issue of Oct 19, 2026