For consultants, freelancers, and agencies
A toolkit for each client.
Give each client's projects their own default toolkit. The next time you start work there, their tools and instructions are already selected.
Claude Code · Codex · Cursor · Antigravity · opencode
$5/month after the trial. Cancel any time. Card required.
- Client A: web app
- Framework guidance, database tools, and test instructions
- Client B: launch site
- Brand guidelines, copywriting, and page review
- A different task
- Choose another toolkit for one launch
Example setup. A toolkit is not a security boundary between clients.
Reuse the setup across a client's projects
Give related projects the same default toolkit. Keep a separate toolkit when another client needs different tools, instructions, or settings.
Change tasks without changing the default
Choose a review or presentation toolkit for a single launch. The next launch uses the project's default again.
Questions
Can several projects use one toolkit?
Yes. Assign the same default toolkit to each project that needs it.
Does this isolate one client's data from another's?
Not by itself. Toolkit selection controls configuration, not a complete security boundary. Keep each client's service permissions and accounts separate.
How should I handle client API keys?
Configure the required credentials locally with the correct scope. Do not put secret values in toolkit files or assume that choosing a toolkit grants the right service access.