ClaudeThings
Summary
Boilerplate dies the moment you download it — locked to someone else's stack, stale within weeks, and zero help after the sale. ClaudeThings is built around the opposite premise: agents that read your project conventions and adapt, rather than code you inherit and maintain.
Running inside Claude Code via a single npx command, ClaudeThings drops 89 agents, 103 skills, and 181 slash commands into any project — split across an engineering kit and a marketing kit that share the same project context. The tech-lead agent plans and delegates; specialists like react-specialist, golang-pro, and security-auditor execute in their lanes; the marketing side handles everything from SEO audits to launch-day campaign briefs. Because agents read a CLAUDE.md you fill in once, stack-specific conventions carry through every task without re-prompting. The ceiling appears when your workflow needs to step outside Claude Code — there is no API, so external pipeline integrations require a different tool.
Bottom line: ClaudeThings works cleanly for a solo builder or small team shipping a full-stack product inside Claude Code; it breaks down the moment you need to wire these agents into an external CI pipeline or trigger them from outside the Claude Code environment.
Pricing Plans
- Price
- $49 one-time per kit; $89 one-time for bundle (launch price)
Engineer
$49 one-time, lifetime updates
- 58 engineering agents
- 61 skills
- 159 commands
Marketing
$49 one-time, lifetime updates
- 31 marketing agents
- 42 skills
- 32 commands
Bundle
$89 one-time (launch price), lifetime updates
- Both kits
- 89 agents total
- 103 skills
- 181 commands
View full pricing on claudethings.com →
Pricing may have changed since last verified. Check the official site for current plans.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Stack-agnostic agent design backed by CLAUDE.md context inheritance, so teams on Next.js, Django, Rails, Go, or Rust get consistent convention-aware output without re-prompting every session.
- Engineering and marketing agents share the same project context, which means launch copy and product code are written from the same source of truth — no separate briefing round for the growth side.
- Agents update automatically when the underlying Claude model improves, so the team does not freeze at the capability level it had on purchase day — no upgrade fee, no manual migration.
- À la carte agent installation via a single command, so teams that need only the debugger or security-auditor are not forced to manage the full 89-agent surface area.
- No global install required and no forced framework opinions, which means adding ClaudeThings to an existing project does not restructure your repo or override architectural decisions you have already made.
Cons
Sign in to edit- No API exists, so any team that needs to trigger agents from an external system — CI pipelines, webhook-driven workflows, or a custom dashboard — hits an immediate hard wall. Those teams add a separate agent orchestration platform alongside ClaudeThings, at which point they are running two systems.
- The entire surface area operates inside Claude Code, which means teams not already committed to Claude Code as their primary development environment are adopting both a tool and a workflow dependency simultaneously — teams on VS Code with custom toolchains or those who need IDE-agnostic automation will find no path forward here.
- With 89 agents, 103 skills, and 181 slash commands, the initial configuration and CLAUDE.md authoring carry real setup overhead; teams expecting immediate zero-configuration output will spend time teaching the system before it produces context-accurate results.
- Because ClaudeThings is a paid-only, closed-source product with no free tier and no API, teams that later need to extend agent behavior programmatically or audit the agent logic have no path to fork, inspect, or modify the underlying implementation — they are dependent on the vendor's release cadence for any capability gaps.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Node.js 18+ via npx
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-07-15T02:53:54.642Z
Best For
Who it's for
- Claude Code users building full-stack applications
- Teams needing both engineering and growth automation
- Projects requiring stack-agnostic, living agent teams
- Developers avoiding frozen boilerplate templates
What it does well
- Planning and delegating software features across stacks
- Running code reviews, tests, and security audits
- Generating marketing campaigns, SEO content, and launch plans
- Adapting agents to custom project conventions via CLAUDE.md
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare ClaudeThings
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is ClaudeThings free?
- ClaudeThings is a paid tool ($49 one-time per kit; $89 one-time for bundle (launch price)). No permanent free tier is offered.
- Is ClaudeThings open source?
- No — ClaudeThings is a closed-source tool. Source code is not publicly available.
- Can I self-host ClaudeThings?
- Yes. ClaudeThings supports self-hosting on your own infrastructure.
- What platforms does ClaudeThings support?
- ClaudeThings is available on: Node.js 18+ via npx.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Best ClaudeThings alternatives →
Curated lists that include this category
ClaudeThings delivers a pre-built agent team into any project via a single npx command, with no global install required. The kit ships in two parts — an engineering team of 58 agents and a marketing team of 31 agents — and both sides read a shared CLAUDE.md file that captures your stack, conventions, and brand voice. From there, the tech-lead agent plans features and delegates to specialists, the shipper agent gates releases, and marketing agents handle everything from positioning to email sequences, all from within Claude Code using slash commands like /api-scaffold, /test-coverage, /launch-plan, and /blog-post.
The defining architectural choice is context inheritance through CLAUDE.md. You fill it in once; every agent reads it before acting. That means a react-specialist and an seo-specialist are operating from the same project context — your component conventions inform the code, and your brand voice informs the copy, without you bridging the gap manually each session. Agents also update automatically when Anthropic ships a smarter Claude model, so the team improves without a paid upgrade or a template refresh cycle.
ClaudeThings fits teams who live in Claude Code and want to skip the scaffolding sprint — particularly solo founders or small teams building across the full stack who also need marketing output and do not want to context-switch between separate tools. The hard limit is the absence of an API: there is no way to trigger these agents from an external system, embed them in a CI/CD pipeline, or call them programmatically. Teams that need agents operating outside the Claude Code interface will need a separate orchestration layer alongside this kit.
Installation is handled by a one-liner from a private GitHub repo. Individual agents can be added à la carte — the vendor cites ‘claudethings add agent debugger’ as an example — so teams are not forced to absorb the full 89-agent surface area on day one. The one-time payment model covers lifetime updates, and no recurring subscription is required.