Browse / Professional & finance / repo-structure-agency
repo-structure-agency
matteotitta
One Claude Code workspace for your agency and every client: per-client context folders, 11 context skills, an example client.
Open matteotitta/repo-structure-agency → Checked against the four rules.
agencyagent-skillsb2b-saasclaude-codeconsultinggtmmarketingtemplate
Built for Claude Code
ships .claude CLAUDE.md and nothing for other agents.
In its own words
One Claude Code workspace for your own business and every client you serve. Each client gets their own context folder, so Claude never mixes one client's positioning into another's work. You don't rebuild the setup for every new engagement.
Marketing for one company? Use repo-structure-in-house instead.
Start in three steps
- Create your copy. Click Use this template above, or run:
- Read the example client.
clients/active/pulse-analytics/is a made-up B2B SaaS client with every context file filled in. - Onboard your first real client. Copy
clients/_template/toclients/active/ /, open Claude Code and say which client you're working on, then run:
Do the same in my-agency/ for your own positioning and content.
Web research works best with an Exa key in .env (copy env to .env). Without one, the skills fall back to plain web search.
What's inside
The idea: the hard part of agency work with AI isn't the prompt. It's keeping six clients' context apart and current. Each client folder holds everything Claude needs for that client, and the root CLAUDE.md makes Claude ask which client before it reads or writes.
Add skills for each lane
The 11 skills here build each client's context. Add the plugin for the work you sell. Each one reads the active client's context/:
Want to package your own method as skills? Start from gtm-skill-template.
Quoting 63% of the README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.