Battle-tested agent configs I built to run my own solo founder stack — trading, marketing, code review, design, daily ops.
Drop them into ~/.claude/agents/ and they work.
All six packs. Every future pack I release (Month 1-12 free). Private Discord with other buyers. A copy of the ops-control dashboard HTML to run your agents locally.
Buy Bundle · $199These aren't theoretical prompts. I built each agent for a job I was doing myself — running my solo founder stack while bootstrapping a trading system, a motion-design business, and a dev portfolio.
Every agent has a sharp scope, anti-patterns to avoid, specific output format. They don't ramble. They don't pretend to be your friend. They do one job well.
The whole setup runs in ops-control, a localhost dashboard I built to brief agents, log runs, and track spend. The bundle includes it.
# your ~/.claude/agents/ ├ marketing-team/ │ ├ copywriter.md │ ├ outreach-writer.md │ ├ social-poster.md │ ├ funnel-strategist.md │ ├ seo-optimizer.md │ ├ ad-creative.md │ ├ ad-targeting.md │ └ ad-analyst.md ├ engineering-team/ │ ├ code-reviewer.md │ └ ... 5 more ├ design-team/ ├ strategy-team/ ├ trading-team/ └ life-ops/ # In Claude Code, just: $ claude "@copywriter rewrite this hero" $ claude "@risk-checker size this trade" $ claude "@morning-brief"
Stripe checkout. You get a .zip with all the agent files + a README.
Every file is a Markdown with YAML frontmatter. Claude Code reads it automatically — no restart, no config.
In Claude Code, reference by name: "@copywriter write hero for X" or run via the Agent tool. Each agent has its own scope + voice.
~/.claude/agents/ and Claude Code uses them.