tonone-ai contributor

Tonone Ai

Install a full virtual engineering and product org—hundreds of agent plugins or team bundles—in one Claude marketplace.

Overview

tonone-ai is a plugin marketplace for the Build phase that installs bundled engineering and product AI agent teams—up to 23 agents across 457 catalog plugins.

What is this marketplace?

  • 457 listed plugins spanning individual agents and installer bundles
  • Flagship tonone bundle: Engineering + Product—23 agents across 2 teams in one install
  • engineering-team installer: 15 Engineering Team agents (v0.6.1)
  • product-team installer: 8 Product Team agents (v0.6.1)
  • full-team bundle installer for all 23 agents at once
  • Marketplace metadata lists 457 plugins
  • tonone bundle: 23 agents, 2 teams (Engineering + Product)
  • engineering-team installer: 15 agents; product-team installer: 8 agents (bundle v0.6.1)

Compatible agents: Claude Code, Cursor, any compatible agent

Community signal: 47 GitHub stars.

What problem does it solve?

One general coding agent cannot cover PM, architecture, and implementation roles without you manually swapping prompts and context.

Who is it for?

Power users building SaaS or agent products who want a pre-built multi-agent roster from tonone.ai without assembling skills one-by-one.

Skip if: Beginners who want a single deploy or review plugin, or anyone who will drown in 457 listings without a narrow team bundle choice.

What do I get? / Deliverables

You install team or full-org bundles and route work to specialized agents for product and engineering tasks from one marketplace.

  • Installed set of tonone engineering and/or product agents via bundle plugins
  • Team-scale agent roster for Build-phase specs and implementation support
  • Repeatable installer paths for 8-, 15-, or 23-agent configurations

Plugins in this marketplace

457 plugins — install individually after you add the marketplace.

PluginVersion
TononeEngineering + Product team — 23 agents, 2 teams. All agents and skills in one install.1.0.0Engineering TeamInstall all 15 Engineering Team agents at once0.6.1Product TeamInstall all 8 Product Team agents at once0.6.1Full TeamInstall all 23 tonone agents at once — Engineering Team + Product Team0.6.1Legal TeamInstall all 10 Legal Team agents at once — contracts, compliance, IP, governance, regulatory1.2.0ApexEngineering lead — orchestrates the team, scopes work, controls depth and budget0.1.0ForgeInfrastructure engineer — cloud services, networking, IaC, cost optimization0.1.0RelayDevOps engineer — CI/CD, deployments, GitOps, developer experience0.1.0SpineBackend engineer — APIs, system design, performance, distributed systems0.1.0FluxData engineer — databases, migrations, pipelines, data modeling0.1.0WardenSecurity engineer — IAM, secrets, compliance, threat modeling0.1.0VigilObservability & reliability engineer — monitoring, alerting, SRE, incident response, SLOs0.1.0PrismFrontend & DX engineer — UI, internal tools, developer portals0.1.0CortexML/AI engineer — model training, MLOps, feature engineering, LLM integration0.1.0TouchMobile engineer — native iOS/Android, cross-platform, app stores, mobile performance0.1.0VoltEmbedded & IoT engineer — firmware, microcontrollers, edge computing, device protocols0.1.0AtlasKnowledge engineer — architecture docs, ADRs, API specs, system diagrams, onboarding0.1.0LensData analytics & BI engineer — dashboards, metrics design, reporting, data storytelling0.1.0ProofQA & testing engineer — test strategy, E2E suites, integration testing, test infrastructure, flaky test triage0.1.0PavePlatform engineer — developer experience, service catalogs, internal CLIs, golden paths, environment management0.1.0HelmHead of Product — product strategy, requirements, and engineering handoff via the Helm↔Apex interface0.1.0DraftUX designer — user flows, information architecture, wireframes, and interaction design0.1.0FormVisual designer — brand identity, color systems, typography, UI design, and design systems0.1.0EchoUser researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis0.1.0LumenProduct analyst — metrics frameworks, funnel analysis, OKRs, A/B test design, and retention analysis0.1.0SurgeGrowth engineer — acquisition channels, activation funnels, retention playbooks, and PLG strategy0.1.0CrestProduct strategist — roadmap planning, prioritization frameworks, competitive analysis, and market positioning0.1.0PitchProduct marketer — positioning, messaging, value proposition, GTM strategy, and launch copy0.1.0DealRevenue & sales engineer — B2B pipeline, deal strategy, pricing, sales playbooks, and enterprise closing0.9.9KeepCustomer success engineer — onboarding optimization, health scoring, expansion revenue, and churn prevention0.9.9InkContent marketing engineer — blog strategy, SEO, thought leadership, developer content, and content calendar0.9.9BuzzPR & community engineer — press pitches, social media, open source community, DevRel, and launch moments0.9.9Apex PlanPlan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.0.6.6Apex ReconEngineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.0.6.6Apex ReviewCross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.0.6.6Apex StatusCTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.0.6.6Apex TakeoverSystem takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".0.6.6Atlas AdrWrite an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".0.6.6Atlas ChangelogMaintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".0.6.6Atlas MapMap the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".0.6.6Atlas OnboardGenerate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".0.6.6Atlas PresentGenerate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".0.6.6Atlas ReconDocumentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".0.6.6Atlas ReportRender agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.0.6.6Cortex EvalEvaluate model performance — check for accuracy drops, data drift, and error patterns. Use when asked about "model accuracy dropped", "evaluate the model", "check for drift", or "model performance".0.6.6Cortex IntegrateDesign and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".0.6.6Cortex ModelBuild an ML pipeline — from data to trained model to serving endpoint. Use when asked to "build ML model", "train a model", "prediction pipeline", "classification", or "regression".0.6.6Cortex PromptBuild a production-ready prompt package — system prompt, few-shot examples, output format, edge case handling, eval criteria. Use when asked to "prompt engineering", "build a prompt", "write a system prompt", or "improve this prompt".0.6.6Cortex ReconML reconnaissance — inventory all models, pipelines, data sources, and monitoring. Use when asked "what ML do we have", "model inventory", or "ML assessment".0.6.6Crest CompeteCompetitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".0.6.6Crest NarrativeStrategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".0.6.6Crest OkrOKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".0.6.6Crest ReconStrategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.0.6.6Crest RoadmapBuild a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".0.6.6Draft Flow|0.6.6Draft IaInformation architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".0.6.6Draft Landing|0.6.6Draft Patterns|0.6.6Draft ReconUI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wireframe work.0.6.6Draft ReviewUsability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".0.6.6Draft WireframeText and Mermaid wireframes — produce screen-level layouts with content hierarchy, component placement, and interaction annotations. Use when asked to "wireframe this", "sketch the UI", "layout for this screen", "lo-fi mockup", "screen design", or "what should this page look like".0.6.6Echo FeedbackFeedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", "NPS analysis", "churn feedback synthesis", or "what's the feedback telling us".0.6.6Echo InterviewRun a user interview — produce an interview guide and synthesize the output into an actionable insight report. Use when asked to "run a user interview", "synthesize these interview notes", "what do users actually want", "build a persona from this feedback", "find the JTBD in these transcripts", or "analyze this interview data".0.6.6Echo JobsJobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD framework", or "why are users switching".0.6.6Echo ReconUser research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work.0.6.6Echo SegmentUser segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".0.6.6Flux HealthData quality and pipeline health check — freshness, schema drift, null rates, orphaned records, pipeline status. Use when asked about "data quality check", "pipeline health", "is our data fresh", or "schema drift".0.6.6Flux MigrateBuild zero-downtime database migrations — forward SQL, rollback SQL, deployment sequence. Use when asked to "write migration", "schema change", "add column", "rename table", "drop column", or "migrate safely".0.6.6Flux PipelineBuild a data pipeline — ETL/ELT with extraction, transformation, loading, error handling, and scheduling. Use when asked to "build ETL", "data pipeline", "move data from X to Y", or "sync data".0.6.6Flux QueryOptimize slow database queries — analyze execution plans, add indexes, rewrite queries. Use when asked about "slow query", "optimize SQL", "query performance", or "explain this query".0.6.6Flux ReconDatabase reconnaissance — full inventory of schema, migrations, data volume, backups, connection pooling, and query patterns. Use when asked to "assess this database", "understand the schema", or "database health check".0.6.6Flux SchemaDesign and build database schema — tables, columns, types, indexes, constraints, relationships. Given a domain description, output the schema and write the files. Use when asked to "design schema", "database design", "create tables", or "data model".0.6.6Forge AuditAudit existing infrastructure for security issues, waste, and misconfigurations. Use when asked to "audit my infra", "check cloud setup", "infra review", "are we wasting money", "security check on infra", or "review my terraform".0.6.6Forge CostAudit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".0.6.6Forge DiagnoseDiagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".0.6.6Forge InfraBuild production-grade infrastructure as code for a service or project. Use when asked to "set up infra", "provision infrastructure", "create cloud resources", "IaC for this project", "terraform for this", or "deploy this service".0.6.6Forge NetworkDesign and build networking infrastructure — VPCs, subnets, DNS, load balancers, firewall rules. Use when asked to "set up networking", "VPC design", "configure DNS", "load balancer setup", "network architecture", or "firewall rules".0.6.6Forge ReconInfrastructure reconnaissance — inventory all cloud resources, map connections, flag risks. Use when asked to "inventory our infra", "what infrastructure do we have", "map our cloud resources", "infra discovery", or "what's running in our cloud".0.6.6Form Audit|0.6.6Form Brand|0.6.6Form Component|0.6.6Form Deck|0.6.6Form Email|0.6.6Form Exam|0.6.6Form Logo|0.6.6Form Mobile|0.6.6Form Palette|0.6.6Form Social|0.6.6Form Style|0.6.6Form Tokens|0.6.6Form Web|0.6.6Helm ArbiterScope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".0.6.6Helm Brief|0.6.6Helm Handoff|0.6.6Helm Plan|0.6.6Helm ReconProduct landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.0.6.6Lens AuditReview existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".0.6.6Lens Chart|0.6.6Lens DashboardDesign and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".0.6.6Lens MetricsProduce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like. Given a product area, outputs the full metrics spec. Use when asked to "define KPIs", "metrics framework", "what should we measure", "north star metric", or "instrument this feature".0.6.6Lens ReconAnalytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".0.6.6Lens ReportBuild a reporting pipeline — scheduled reports with SQL queries, delivery via Slack or email, threshold alerts, and historical comparison. Use when asked for "automated reports", "scheduled report", "email digest", or "Slack alerts for metrics".0.6.6Lumen AbtestA/B test design — produce an experiment spec with hypothesis, primary metric, MDE, sample size, run time, and decision rule. Also determines when NOT to A/B test and what to do instead. Use when asked to "design an A/B test", "should we test this", "experiment design", "how do we know if this works", "what's the sample size", or "set up an experiment".0.6.6Lumen Funnel|0.6.6Lumen InstrumentInstrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools. Use when asked to "what should we track", "instrumentation plan", "set up analytics events", "analytics event schema", "tracking plan", or "instrument this feature".0.6.6Lumen MetricsMetrics architecture — produce a complete metrics plan given a product description. North Star, input metrics tree, instrumentation spec, action triggers, and counter-metrics. Use when asked to "design a metrics framework", "what should we measure", "build a metrics system", "define our KPIs", "what are our success metrics", "metrics strategy", or "what do we track".0.6.6Lumen ReconAnalytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.0.6.6Pave AuditAudit developer experience — measure onboarding time, build speed, deployment friction, and developer satisfaction. Use when asked to "DX audit", "developer experience review", "why is development slow", "onboarding assessment", or "DORA metrics".0.6.6Pave CatalogBuild a service catalog — schema, starter entries, and governance model. Produces what information to capture per service, how it's maintained, and where it lives. Use when asked to "service catalog", "what services do we have", "catalog our services", "service inventory", or "who owns what".0.6.6Pave EnvSet up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".0.6.6Pave GoldenDefine a golden path — the opinionated, supported way to do a common developer task (create a new service, set up an environment, deploy a feature). Produces concrete steps, templates, and tooling. Use when asked to "golden path", "create project template", "scaffold a new service", "how should we create services", or "standardize our setup".0.6.6Pave ReconPlatform reconnaissance — inventory all developer tooling, environments, build systems, and developer workflows for project takeover. Use when asked to "understand the dev setup", "developer tooling assessment", "platform assessment", or "how do developers work here".0.6.6Pitch CopyLanding page and marketing copy — write hero section, problem/solution blocks, proof points, and CTAs. Use when asked to "write landing page copy", "write the homepage", "marketing copy for this feature", "product page copy", "write the hero section", or "write copy for [surface]".0.6.6Pitch Landing|0.6.6Pitch LaunchProduce an actual launch plan with announcement copy, channel sequence, and day-1 checklist. Use when asked to "plan a launch", "GTM strategy", "how do we announce this", "launch plan for [feature]", "go-to-market", "write our Product Hunt post", or "how do we get people to notice this".0.6.6Pitch MessageMessaging framework — produce a full headline, subheadline, proof points, and CTA hierarchy for use across all surfaces. Use when asked to "write our messaging", "messaging framework", "what should our headline say", "copy hierarchy", "tagline and messaging", or "how do we talk about the product".0.6.6Pitch PositionProduce a complete positioning document using the Dunford framework — competitive alternatives, unique attributes, value, best-fit customer, market category, positioning statement, and tagline. Use when asked to "write our positioning", "define our value prop", "positioning statement", "what market are we in", "how do we position against X", "what's our tagline", or "write our messaging foundation".0.6.6Pitch ReconMarketing and messaging reconnaissance — read existing landing pages, copy, positioning docs, and marketing materials to understand the current messaging state. Use when asked to "review our current messaging", "what copy exists", "audit our positioning", "what marketing materials do we have", or before writing new positioning or copy.0.6.6Prism AuditFrontend audit — bundle size, dependencies, accessibility, performance, component quality. Use when asked for "frontend review", "performance audit", "accessibility check", or "bundle size".0.6.6Prism Chart|0.6.6Prism ComponentImplement a reusable, accessible, typed component from a design spec. Use when asked to "create a component", "build a widget", "implement this design", or "reusable UI element".0.6.6Prism DashboardBuild an internal dashboard with data tables, filters, detail views, and CRUD. Use when asked to build an "admin panel", "internal dashboard", "back office", or "data dashboard UI".0.6.6Prism ReconFrontend reconnaissance — map the component tree, routing, state management, build config, and assess quality. Use when asked to "understand this frontend", "frontend assessment", or "what's the UI built with".0.6.6Prism Stack|0.6.6Prism UiImplement a complete UI screen or feature from a Form visual spec. Use when asked to "build a page", "implement this screen", "build the frontend for this feature", or "create this UI".0.6.6Proof ApiBuild API test suites — endpoint testing, contract testing, load testing for REST/GraphQL/gRPC APIs. Use when asked to "test this API", "API tests", "endpoint testing", "contract tests", or "load test".0.6.6Proof AuditAudit test suite health — find flaky tests, slow tests, coverage gaps, and testing anti-patterns. Use when asked to "audit tests", "fix flaky tests", "why are tests slow", "test health", or "improve test suite".0.6.6Proof Design|0.6.6Proof E2eBuild E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".0.6.6Proof ReconTesting reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".0.6.6Proof StrategyProduce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".0.6.6Relay AuditAudit an existing CI/CD pipeline for slowness, security issues, and reliability gaps. Use when asked to "audit pipeline", "why is CI slow", "pipeline review", or "deployment review".0.6.6Relay DeploySet up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".0.6.6Relay DockerBuild production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".0.6.6Relay PipelineBuild a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".0.6.6Relay ReconMap the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Use when asked "how does this deploy", "map the pipeline", or "understand CI/CD".0.6.6Relay ShipEnd-to-end ship workflow — merge base, run tests, review diff, bump version, commit, push, create PR. Use when asked to "ship", "push to main", "create a PR", "get this merged", or "deploy this branch".0.6.6Spine ApiDesign and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".0.6.6Spine DesignProduce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".0.6.6Spine PerfFind and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".0.6.6Spine ReconBackend reconnaissance — map all routes, middleware, models, dependencies, auth, and assess code quality for project takeover. Use when asked to "understand this backend", "map the API", or "assess code quality".0.6.6Spine ReviewAPI and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".0.6.6Spine ServiceBuild a new production-ready service from scratch — config management, health checks, graceful shutdown, structured logging. Use when asked to "new service", "scaffold a backend", "bootstrap service", or "create microservice".0.6.6Surge Activation|0.6.6Surge ExperimentGrowth experiment design — structure a growth hypothesis, define metric, baseline, expected lift, and kill condition for a single experiment. Use when asked to "design a growth experiment", "test this growth idea", "experiment framework", "how do we test if this works", or "growth hypothesis".0.6.6Surge Landing|0.6.6Surge PlgPLG motion design — free tier definition, activation sequence, expansion trigger points, viral mechanic assessment. Given a product, output the PLG architecture and make the calls. Use when asked to "PLG strategy", "freemium model", "product-led growth plan", "self-serve motion", "how do we add a free tier", "upgrade triggers", or "viral loop design".0.6.6Surge ReconGrowth state reconnaissance — scan existing onboarding flows, acquisition channels, conversion funnels, and growth experiment logs to understand current growth state. Use when asked to "what's our growth state", "audit the funnel", "what growth experiments have we run", "acquisition channel inventory", or before designing new growth experiments.0.6.6Surge RetentionRetention diagnosis + intervention plan — analyze the retention curve, identify the primary drop-off point, and produce a specific intervention plan with expected impact. Use when asked to "improve retention", "why are users churning", "build a retention playbook", "reduce churn", "win-back campaign", or "users aren't coming back".0.6.6Touch AppProduce a complete mobile app architecture design — platform choice, navigation structure, state management, data layer, key screens. Use when asked to "build a mobile app", "new app", "create iOS/Android app", "app architecture", or "cross-platform app".0.6.6Touch AuditMobile audit — app size, startup time, crash reporting, store compliance, accessibility, offline behavior. Use when asked for "mobile review", "app store readiness", "mobile performance", or "crash analysis".0.6.6Touch FeatureProduce a mobile feature spec — user story, technical approach, component breakdown, platform-specific considerations, edge cases. Use when asked to "add a screen", "spec this feature", "mobile feature", "new tab", "push notifications", or "deep link".0.6.6Touch ReconMobile reconnaissance — understand the app's tech stack, architecture, dependencies, and health for takeover. Use when asked to "understand this app", "mobile assessment", or "app health".0.6.6Touch ReleaseSet up mobile release pipeline — Fastlane, code signing, CI, beta distribution, versioning. Use when asked about "app store setup", "release pipeline", "fastlane", "beta distribution", or "signing".0.6.6Touch Ui|0.6.6Vigil AlertWrite SLO-based alert rules with burn rate thresholds and paired runbooks. Outputs actual alert configs, not a strategy doc. Use when asked to "set up alerts", "create runbooks", "define SLOs", or "alerting strategy".0.6.6Vigil CheckVerify observability posture — audit monitoring coverage, find blind spots, prioritize gaps. Use when asked "is monitoring sufficient", "observability review", "are we covered", or "pre-launch monitoring check".0.6.6Vigil IncidentIncident response — diagnose production issues, find root cause, propose fix with rollback. Use when asked about "something is broken", "production issue", "why is this down", "incident", or "debug production".0.6.6Vigil InstrumentInstrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".0.6.6Vigil ReconObservability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".0.6.6Volt DriverBuild a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction. Use when asked to "write a driver", "I2C device", "BLE service", "MQTT client", or "sensor integration".0.6.6Volt FirmwareProduce a complete firmware architecture spec for a described device — layer diagram, module responsibilities, HAL interface definitions, key state machines, RTOS decision. Use when asked to "design firmware architecture", "plan embedded firmware", "architect an IoT device", "how should I structure this firmware", or given a device description and asked what the firmware should look like.0.6.6Volt OtaProduce a complete OTA update system design — partition layout, update flow, rollback conditions, validation checks, fleet management approach, failure modes and recovery. Use when asked about "OTA updates", "firmware updates over the air", "how do I update devices in the field", "OTA strategy", or "remote firmware update design".0.6.6Volt PowerPower management audit — analyze sleep modes, wake sources, power state machines, radio duty cycles, and battery life estimates. Use when asked to "audit power usage", "optimize battery life", "review power management", "why is my battery draining", "power budget analysis", or "sleep mode review".0.6.6Volt ReconFirmware reconnaissance for takeover — inventory the MCU, peripherals, RTOS, protocols, OTA, power management, and assess code quality with risk flags. Use when asked to "understand this firmware", "device inventory", or "embedded assessment".0.6.6Warden AuditFull security audit — secrets, dependencies, IAM, auth, injection, XSS, HTTPS, rate limiting, public storage. Use when asked for "security audit", "check for vulnerabilities", "security review", or "are we secure".0.6.6Warden HardenProduce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".0.6.6Warden IamBuild IAM from scratch — roles, policies, service accounts with least privilege. Use when asked to "set up IAM", "create roles", "service accounts", or "access control".0.6.6Warden ReconSecurity reconnaissance — full inventory of secrets management, IAM, dependencies, auth, encryption, audit logging, and compliance gaps. Use when asked about "security posture", "how secure is this", or "security assessment".0.6.6Warden ThreatProduce a threat model — assets, ranked threats, mitigations, accepted risks. Use when asked to "threat model this", "what could go wrong security-wise", "map our attack surface", or before designing any security-sensitive feature.0.6.6Tonone OnboardFirst-run onboarding tour — guided walkthrough of tonone's 23 agents, key skills, and worktree sessions. Two paths: expert (~90 sec) and newcomer (~8 min). Use when asked "how do I use tonone", "what can tonone do", "show me around", or "first steps".0.8.0ContributeContribute a discovery back to the upstream tonone repo — new skill, improved agent prompt, better routing rule. Use when you hit a gap, found a better pattern, or built something reusable that others would benefit from.0.1.0MintFinance engineer — P&L, runway, unit economics, fundraising, board reporting, and cap table management1.1.0FolkPeople engineer — org design, hiring pipelines, compensation frameworks, onboarding playbooks, performance management, and human-to-agent migration1.1.0KeelOperations engineer — process design, vendor management, legal ops, compliance (SOC2/GDPR), OKR execution, and cross-functional coordination1.1.0BraceSupport engineer — ticket workflow design, SLA architecture, knowledge base, escalation paths, and support operations at scale1.1.0BriefContract & Policy Drafter — NDA, MSA, employment agreements, SLAs, vendor contracts1.2.0ClauseContract Clause Analyst — redlining, risk scoring, negotiation playbooks1.2.0BindCompliance Framework Engineer — SOC2, GDPR, HIPAA, ISO 27001 gap analysis1.2.0FrameCorporate Governance Advisor — board resolutions, cap table, equity plan docs1.2.0ShieldRegulatory Risk Advisor — GDPR, CCPA, FTC, financial regulation, export controls1.2.0ScopeIP & Trademark Advisor — trademark clearance, patent landscape, OSS license compliance1.2.0AuditLegal Compliance Auditor — internal controls, legal risk register, audit trail1.2.0CiteLegal Researcher — case law synthesis, statute analysis, jurisdiction comparison1.2.0LodgeRegulatory Filing Advisor — DMCA, FTC disclosures, GDPR DPAs, government filings1.2.0TermsPrivacy & ToS Drafter — GDPR-compliant privacy policies, ToS, cookie policies, DPAs1.2.0Brief DraftDraft a contract or policy document from a description1.2.0Brief ReviewReview and redline a contract — risk and missing clauses1.2.0Brief ReconSurvey existing contracts and policy documents1.2.0Clause AnalyzeDeep clause-by-clause analysis with risk scores1.2.0Clause PlaybookGenerate negotiation playbook for a contract type1.2.0Clause ReconScan existing contracts for risk patterns1.2.0Bind GapCompliance gap analysis — SOC2, GDPR, HIPAA, ISO 270011.2.0Bind PolicyDraft compliance policies required by a framework1.2.0Bind ReconSurvey existing compliance artifacts and certifications1.2.0Frame BoardDraft board resolutions and corporate consent documents1.2.0Frame EquityDraft equity plan documents and option grant agreements1.2.0Frame ReconSurvey corporate governance artifacts and flag gaps1.2.0Shield AssessRegulatory exposure assessment for a product or geography1.2.0Shield RespondDraft regulatory response letters and regulator comms1.2.0Shield ReconMap product data flows and identify regulatory triggers1.2.0Scope TrademarkTrademark clearance research and filing preparation1.2.0Scope OssOpen source license compliance audit — GPL, LGPL, AGPL risks1.2.0Scope ReconSurvey IP assets, license obligations, and assignment gaps1.2.0Audit LegalFull legal compliance audit and risk register1.2.0Audit ControlsInternal legal controls review — approval workflows, doc governance1.2.0Audit ReconAssess legal artifact completeness and audit readiness1.2.0Cite ResearchLegal research — case law, statutes, regulatory guidance1.2.0Cite CompareJurisdiction comparison for a legal requirement or clause1.2.0Cite ReconIdentify open legal questions and research gaps1.2.0Lodge FilingPrepare regulatory filing, disclosure notice, or government submission1.2.0Lodge DmcaDraft DMCA takedown notice or counter-notice1.2.0Lodge ReconIdentify required regulatory filings and their status1.2.0Terms PrivacyDraft GDPR-compliant privacy policy for the product1.2.0Terms TosDraft Terms of Service for the product1.2.0Terms ReconCheck privacy policy and ToS for completeness and compliance1.2.0Design TeamDesign Team bundle — 10 agents: Hue, Grid, Glyph, Move, Wire, Mark, Cut, Axe, Tone, Copy1.3.0HueColor Systems Designer — Color palette design — semantic tokens, dark/light mode, WCAG contrast1.3.0Hue PaletteDesign a color palette with semantic tokens for a brand or product1.3.0Hue TokenAudit or refactor a design token system for color1.3.0Hue ReconAudit existing color usage in a codebase1.3.0GridLayout Systems Designer — Layout system design — spacing scales, responsive grids, layout primitives1.3.0Grid LayoutDesign a layout system — spacing scale, grid columns, and layout primitives1.3.0Grid ResponsiveAudit or redesign responsive behavior of a layout1.3.0Grid ReconAudit existing layout patterns in a codebase1.3.0GlyphTypography Designer — Typography system design — font pairing, type scale, hierarchy tokens1.3.0Glyph PairSelect and pair fonts for a product1.3.0Glyph ScaleDesign a type scale and hierarchy1.3.0Glyph ReconAudit existing typography in a codebase1.3.0MoveMotion Designer — Motion design — animation principles, transition systems, micro-interaction specs1.3.0Move AnimateDesign an animation spec for a component or interaction1.3.0Move SystemDesign a motion system for a product1.3.0Move ReconAudit existing animations in a codebase1.3.0WirePrototyping Engineer — Prototyping and handoff — interactive flow docs, component specs, developer handoff1.3.0Wire PrototypeDocument a prototype or user flow1.3.0Wire SpecWrite a developer handoff spec for a component or feature1.3.0Wire ReconAudit existing design documentation1.3.0MarkBrand Designer — Brand identity design — logo usage rules, brand guidelines, visual identity systems1.3.0Mark BrandWrite brand guidelines — logo usage, color, typography, voice1.3.0Mark AssetDesign an asset library structure — naming, formats, delivery specs1.3.0Mark ReconAudit existing brand assets and usage1.3.0CutIllustration & Icon Designer — Illustration and icon design — custom assets, icon systems, SVG optimization1.3.0Cut IconDesign an icon system spec or audit existing icons1.3.0Cut IllustrateSpec or critique custom illustrations1.3.0Cut ReconAudit existing icons and illustrations in a codebase1.3.0AxeAccessibility Engineer — Accessibility engineering — WCAG audits, keyboard nav, screen reader testing, ARIA1.3.0Axe AuditRun a WCAG accessibility audit1.3.0Axe FixWrite accessibility fixes for specific WCAG failures1.3.0Axe ReconSurvey a codebase for accessibility debt1.3.0ToneDesign Token Engineer — Design token engineering — token architecture, theming systems, style-dictionary pipelines1.3.0Tone TokenDesign or refactor a design token architecture1.3.0Tone ThemeBuild or fix a theming system1.3.0Tone ReconAudit existing token usage in a codebase1.3.0CopyContent Designer — UX writing and content design — microcopy, error messages, onboarding, UI content strategy1.3.0Copy WriteWrite UX copy for a feature, flow, or component1.3.0Copy AuditAudit UX copy in a product or codebase1.3.0Copy ReconSurvey all user-facing strings in a codebase1.3.0Data Science TeamData Science Team bundle — 10 agents: Cast, Feat, Fit, Score, Drift, Vect, Tune, Plot, Clean, Eval1.4.0CastForecasting Engineer — Time series forecasting — demand prediction, trend analysis, seasonal decomposition1.4.0Cast ForecastBuild a forecasting model for a time series1.4.0Cast ValidateValidate and benchmark a forecasting model1.4.0Cast ReconSurvey existing forecasting code or models1.4.0FeatFeature Engineer — Feature engineering — transformations, encodings, feature stores, pipeline design1.4.0Feat EngineerDesign a feature engineering pipeline for a ML problem1.4.0Feat StoreDesign or audit a feature store1.4.0Feat ReconAudit feature engineering code for leakage and quality issues1.4.0FitModel Training Engineer — Model training — algorithm selection, hyperparameter tuning, training infrastructure1.4.0Fit TrainDesign a model training pipeline1.4.0Fit TuneDesign a hyperparameter tuning strategy1.4.0Fit ReconAudit existing model training code1.4.0ScoreModel Evaluation Engineer — Model evaluation — metrics design, statistical significance, model comparison1.4.0Score EvalDesign an evaluation framework for a ML model1.4.0Score CompareCompare two or more models statistically1.4.0Score ReconAudit existing model evaluation code1.4.0DriftML Monitoring Engineer — ML monitoring — data drift, concept drift, model degradation, production ML health1.4.0Drift MonitorDesign a drift monitoring system for a production ML model1.4.0Drift AlertDesign drift alerts and escalation1.4.0Drift ReconAudit existing ML monitoring1.4.0VectEmbeddings & Vector Search Engineer — Embeddings and vector search — semantic search, RAG pipelines, vector database design1.4.0Vect EmbedDesign an embedding pipeline1.4.0Vect SearchDesign a vector search or RAG system1.4.0Vect ReconAudit existing vector search or RAG implementation1.4.0TuneLLM Fine-tuning Engineer — LLM fine-tuning — PEFT/LoRA, RLHF, instruction tuning, prompt optimization1.4.0Tune FinetuneDesign a fine-tuning pipeline1.4.0Tune PromptSystematically optimize prompts for a task1.4.0Tune ReconAudit existing fine-tuning or prompt engineering work1.4.0PlotData Visualization Engineer — Data visualization — chart design, visualization libraries, exploratory analysis1.4.0Plot ChartDesign or critique a data visualization1.4.0Plot EdaDesign an exploratory data analysis workflow1.4.0Plot ReconAudit existing visualizations in a codebase or notebook1.4.0CleanData Quality Engineer — Data quality — deduplication, validation, outlier detection, ETL pipeline design1.4.0Clean ValidateDesign a data validation pipeline1.4.0Clean TransformDesign a data cleaning and transformation pipeline1.4.0Clean ReconAudit existing data cleaning code1.4.0EvalExperiment Design Engineer — Experiment design — A/B testing, statistical power, experiment tracking, causal inference1.4.0Eval DesignDesign an A/B test1.4.0Eval AnalyzeAnalyze A/B test results1.4.0Eval ReconAudit existing experimentation infrastructure1.4.0Secops TeamSecurity Operations Team bundle — 10 agents: Red, Blue, Hunt, Patch, Chain, Sast, Siem, Resp, Zero, Phish1.5.0RedOffensive Security Engineer — Red team operations — penetration testing, attack simulation, vulnerability exploitation1.5.0Red PentestDesign a penetration testing plan — scope, methodology, and rules of engagement1.5.0Red ReportWrite a penetration test finding report with CVSS scores and remediation1.5.0Red ReconDesign a reconnaissance plan — OSINT and attack surface mapping1.5.0BlueDefensive Security Engineer — Blue team operations — SOC design, detection engineering, hardening playbooks1.5.0Blue DetectDesign detection rules for a threat — SIEM queries and MITRE ATT&CK mapping1.5.0Blue HardenWrite a hardening playbook — CIS benchmark mapping and implementation steps1.5.0Blue ReconAudit existing security controls and detection coverage1.5.0HuntThreat Hunter — Threat hunting — hypothesis-driven hunting, compromise assessment, IOC analysis1.5.0Hunt AssessDesign a compromise assessment — hunting scope and evidence collection1.5.0Hunt IocAnalyze indicators of compromise — enrichment and attribution1.5.0Hunt ReconDesign a threat hunting program — maturity assessment and playbook library1.5.0PatchVulnerability Management Engineer — Vulnerability management — CVE triage, CVSS prioritization, patching cadence, SLA design1.5.0Patch TriageTriage CVEs — CVSS + EPSS + KEV scoring and prioritization1.5.0Patch PlanDesign a vulnerability management program — SLAs and asset tiers1.5.0Patch ReconAudit existing vulnerability management for SLA gaps1.5.0ChainSupply Chain Security Engineer — Supply chain security — SBOM generation, dependency scanning, third-party risk, license compliance1.5.0Chain SbomDesign an SBOM generation pipeline for CI/CD1.5.0Chain ScanDesign a dependency scanning program — CVE detection and license checks1.5.0Chain ReconAudit existing dependency security and supply chain gaps1.5.0SastApplication Security Engineer — Application security — SAST/DAST scanning, code security review, secure SDLC design1.5.0Sast ScanDesign a SAST/DAST scanning pipeline — tooling and CI integration1.5.0Sast FixAnalyze and fix a SAST finding with secure code alternative1.5.0Sast ReconAudit application security tooling for OWASP Top 10 coverage1.5.0SiemDetection & SIEM Engineer — SIEM engineering — log pipeline design, detection rule development, alert tuning1.5.0Siem RuleWrite SIEM detection rules in SIGMA format with MITRE mapping1.5.0Siem AlertTune a SIEM alert to reduce false positives1.5.0Siem ReconAudit existing SIEM deployment — log coverage and rule quality1.5.0RespIncident Response Engineer — Incident response — playbook design, containment procedures, DFIR, post-incident review1.5.0Resp PlaybookWrite an incident response playbook for a threat scenario1.5.0Resp ContainDesign containment procedures for an active incident1.5.0Resp ReconAudit existing incident response capability and playbook coverage1.5.0ZeroZero Trust Architect — Zero trust architecture — network segmentation, identity-based access, microsegmentation design1.5.0Zero DesignDesign a zero trust architecture — phased roadmap and segmentation1.5.0Zero AuditAudit an environment against zero trust principles1.5.0Zero ReconSurvey network and identity controls for zero trust readiness1.5.0PhishSecurity Awareness Engineer — Security awareness — phishing simulation design, security training programs, social engineering assessment1.5.0Phish AssessDesign a phishing simulation program — scenarios and measurement1.5.0Phish TrainDesign a security awareness training curriculum1.5.0Phish ReconAudit existing security awareness program — coverage and effectiveness1.5.0Devx TeamDeveloper Experience Team bundle — 10 agents: Guide, Sample, Mock, Schema, Port, Change, Onboard, Bench, Compat, Gate1.6.0GuideAPI Documentation Engineer — API and SDK documentation — reference docs, guides, and documentation architecture1.6.0Guide WriteWrite API reference documentation for an endpoint or SDK method1.6.0Guide AuditAudit existing API documentation for completeness and accuracy1.6.0Guide ReconSurvey documentation coverage across an API or SDK1.6.0SampleCode Sample Engineer — Code samples and tutorials — working examples, quickstarts, and language-specific guides1.6.0Sample WriteWrite a working code sample or tutorial for an API feature1.6.0Sample ReviewReview existing code samples for correctness and developer experience1.6.0Sample ReconSurvey existing code samples — coverage, language parity, and freshness1.6.0MockAPI Mocking & Contract Engineer — API mocking — mock server design, contract testing, API simulation1.6.0Mock DesignDesign a mock server for an API1.6.0Mock ContractDesign a consumer-driven contract testing setup1.6.0Mock ReconAudit existing mocks for contract drift and missing error cases1.6.0SchemaAPI Schema Engineer — API schema design — OpenAPI, GraphQL, gRPC schema quality and design standards1.6.0Schema DesignDesign an API schema — OpenAPI, GraphQL, or gRPC proto1.6.0Schema ReviewReview an API schema for consistency and completeness1.6.0Schema ReconAudit existing API schemas for inconsistencies and coverage gaps1.6.0PortSDK Design Engineer — SDK design — multi-language SDK architecture, idiomatic patterns, cross-language consistency1.6.0Port DesignDesign an SDK architecture for an API1.6.0Port ReviewReview an existing SDK for idiomatic quality and consistency1.6.0Port ReconAudit multi-language SDK coverage and consistency1.6.0ChangeChangelog & Release Communication Engineer — Changelog and release communication — breaking change docs, deprecation notices, migration guides1.6.0Change WriteWrite a changelog entry or release notes for an API version1.6.0Change PolicyDesign an API versioning and deprecation policy1.6.0Change ReconAudit existing changelog and deprecation practices1.6.0OnboardDeveloper Onboarding Engineer — Developer onboarding — quickstart design, time-to-first-call optimization, onboarding funnel audit1.6.0Onboard QuickstartWrite a developer quickstart — minimal steps to first successful API call1.6.0Onboard AuditAudit the developer onboarding experience and measure TTFC1.6.0Onboard ReconSurvey existing onboarding docs and developer portal1.6.0BenchAPI Performance Engineer — API performance benchmarking — latency profiling, throughput testing, regression detection1.6.0Bench ProfileDesign a performance benchmark for an API1.6.0Bench CompareCompare API performance across versions for regression detection1.6.0Bench ReconAudit existing performance testing for gaps and stale baselines1.6.0CompatBackwards Compatibility Engineer — Backwards compatibility — breaking change detection, deprecation management, semver discipline1.6.0Compat AuditAudit a proposed API change for breaking changes1.6.0Compat PolicyDesign an API compatibility and deprecation policy1.6.0Compat ReconAudit existing API for breaking change risks and missing controls1.6.0GateAPI Quality Gate Engineer — API quality gates — linting, style enforcement, breaking change CI, and API governance1.6.0Gate LintDesign an API linting ruleset with style rules and severity levels1.6.0Gate CiIntegrate API quality gates into CI1.6.0Gate ReconAudit existing API quality controls and CI gates1.6.0Infra Specialist TeamInfrastructure Specialist Team — 10 agents: Kube, Terra, Finop, Serv, Edge, Cache, Queue, Mesh, Multi, Chaos1.7.0KubeInfrastructure Specialist Team — Kube: Kubernetes cluster design — RBAC, networking, operators, workload configuration1.7.0Kube DesignKube skill: kube-design1.7.0Kube RbacKube skill: kube-rbac1.7.0Kube ReconKube skill: kube-recon1.7.0TerraInfrastructure Specialist Team — Terra: Terraform and IaC — module design, state management, drift detection, and IaC best practices1.7.0Terra DriftTerra skill: terra-drift1.7.0Terra ModuleTerra skill: terra-module1.7.0Terra ReconTerra skill: terra-recon1.7.0FinopInfrastructure Specialist Team — Finop: Cloud cost optimization — FinOps practices, rightsizing, reservation strategy, cost attribution1.7.0Finop AuditFinop skill: finop-audit1.7.0Finop ReconFinop skill: finop-recon1.7.0Finop ReserveFinop skill: finop-reserve1.7.0ServInfrastructure Specialist Team — Serv: Serverless architecture — Lambda/Cloud Functions/Cloud Run design, cold start optimization, event patterns1.7.0Serv ColdServ skill: serv-cold1.7.0Serv DesignServ skill: serv-design1.7.0Serv ReconServ skill: serv-recon1.7.0EdgeInfrastructure Specialist Team — Edge: Edge computing and CDN — global distribution, cache strategy, edge functions, latency optimization1.7.0Edge CdnEdge skill: edge-cdn1.7.0Edge ReconEdge skill: edge-recon1.7.0Edge RouteEdge skill: edge-route1.7.0CacheInfrastructure Specialist Team — Cache: Caching strategy — Redis/Memcached design, cache invalidation, eviction policies, application caching patterns1.7.0Cache DesignCache skill: cache-design1.7.0Cache EvictCache skill: cache-evict1.7.0Cache ReconCache skill: cache-recon1.7.0QueueInfrastructure Specialist Team — Queue: Message queuing and streaming — Kafka, SQS, RabbitMQ design, consumer group strategy, dead letter queues1.7.0Queue DesignQueue skill: queue-design1.7.0Queue ReconQueue skill: queue-recon1.7.0Queue ScaleQueue skill: queue-scale1.7.0MeshInfrastructure Specialist Team — Mesh: Service mesh design — Istio/Linkerd/Envoy, mTLS, traffic management, observability integration1.7.0Mesh DesignMesh skill: mesh-design1.7.0Mesh ObserveMesh skill: mesh-observe1.7.0Mesh ReconMesh skill: mesh-recon1.7.0MultiInfrastructure Specialist Team — Multi: Multi-cloud architecture — provider selection, portability strategy, lock-in avoidance, workload placement1.7.0Multi DesignMulti skill: multi-design1.7.0Multi PortMulti skill: multi-port1.7.0Multi ReconMulti skill: multi-recon1.7.0ChaosInfrastructure Specialist Team — Chaos: Chaos engineering — failure injection design, game days, resilience testing, blast radius control1.7.0Chaos DesignChaos skill: chaos-design1.7.0Chaos GameChaos skill: chaos-game1.7.0Chaos ReconChaos skill: chaos-recon1.7.0Ai Ops TeamAI Operations Team — 9 agents: Deploy, Eval, Trace, Guard, Budget, Token, Prompt, Embed, Rank1.8.0DeployAI Operations Team — Deploy: Model serving, inference APIs, blue/green deploys, rollback, and canary releases for production ML.1.8.0Deploy ServeDesign and configure model serving infrastructure — endpoint scaling, batching, GPU allocation.1.8.0Deploy CanaryPlan and execute canary releases for model updates — traffic splitting, rollback triggers, success metrics.1.8.0Deploy ReconAudit current model deployment topology — serving config, latency profile, version inventory.1.8.0TraceAI Operations Team — Trace: LLM tracing, span capture, prompt/completion logging, cost attribution, and AI system debugging.1.8.0Trace InstrumentInstrument LLM calls with tracing — span structure, token counts, latency, model metadata.1.8.0Trace DebugDebug AI system behavior using traces — prompt reconstruction, output comparison, failure attribution.1.8.0Trace ReconAudit LLM observability coverage — trace gaps, logging completeness, cost attribution accuracy.1.8.0GuardAI Operations Team — Guard: Input/output safety filters, PII detection, content moderation, and AI policy enforcement at runtime.1.8.0Guard DesignDesign guardrail layers — input classifiers, output validators, PII scrubbers, policy rule engines.1.8.0Guard AuditAudit guardrail coverage — bypass vectors, false positive rates, policy gap analysis, red-team scenarios.1.8.0Guard ReconMap current AI safety controls — filter inventory, coverage gaps, latency impact, incident history.1.8.0BudgetAI Operations Team — Budget: LLM spend tracking, model cost optimization, budget alerts, and token efficiency audits across AI workloads.1.8.0Budget AuditAudit AI spend — per-model cost breakdown, top consumers, waste identification, optimization levers.1.8.0Budget OptimizeDesign cost reduction strategies — model tiering, prompt compression, caching, batch inference.1.8.0Budget ReconMap AI cost topology — billing attribution, team-level spend, forecast vs actuals, alert gaps.1.8.0TokenAI Operations Team — Token: Context window optimization, token counting, truncation strategies, and chunking patterns for LLM efficiency.1.8.0Token BudgetDesign token budgets — system/user/assistant allocation, overflow handling, context compression.1.8.0Token ChunkDesign chunking strategies — semantic splitting, overlap tuning, retrieval-aware chunk sizing.1.8.0Token ReconAudit token usage patterns — avg context size, waste, truncation frequency, budget adherence.1.8.0PromptAI Operations Team — Prompt: System prompt design, few-shot libraries, chain-of-thought patterns, and prompt versioning for production LLM applications.1.8.0Prompt DesignDesign production prompts — system prompt architecture, instruction clarity, few-shot selection.1.8.0Prompt VersionBuild prompt versioning systems — storage, A/B testing, regression tracking, rollback.1.8.0Prompt ReconAudit prompt library — duplication, quality, coverage gaps, version drift, eval alignment.1.8.0EmbedAI Operations Team — Embed: Embedding model selection, vector pipeline design, similarity search, and production index management.1.8.0Embed DesignDesign embedding pipelines — model selection, batching, normalization, index refresh strategy.1.8.0Embed SearchOptimize similarity search — ANN index tuning, hybrid search, reranking, query expansion.1.8.0Embed ReconAudit embedding infrastructure — model drift, index freshness, query latency, coverage gaps.1.8.0RankAI Operations Team — Rank: Retrieval reranking, relevance scoring, learning-to-rank pipelines, and result quality evaluation for search and RAG.1.8.0Rank DesignDesign ranking pipelines — reranker selection, score fusion, cross-encoder patterns, latency trade-offs.1.8.0Rank EvalBuild ranking evaluation — NDCG/MRR measurement, human relevance labeling, offline eval harness.1.8.0Rank ReconAudit ranking quality — metric trends, failure modes, dataset coverage, reranker performance.1.8.0Eval HarnessDesign eval harnesses — task schemas, metrics, dataset versioning, eval-as-code patterns.1.8.0Eval RegressBuild automated regression suites — golden sets, threshold alerting, CI integration for model changes.1.8.0EvalsAI Operations Team — Evals: Eval harness design, benchmark suites, automated regression, human eval orchestration.1.8.0

Recommended Marketplaces

Journey fit

Coordinating many role-specific agents (PM, eng, QA-style) maps to Build where product and implementation decisions stack up. PM subphase is the shelf for orchestration, specs, and multi-role agent teamwork rather than a single integration task.

How it compares

Multi-agent team marketplace, not a single DevOps deploy skill or diff-review UI plugin.

Common Questions / FAQ

Who is Tonone Ai for?

Solo builders and small teams using Claude Code who want installer bundles for engineering and product agent squads instead of one generic assistant.

When should I use Tonone Ai?

Use it in Build when you are executing features and need PM plus engineering agent roles—or install full-team early if you standardize on tonone’s 23-agent workflow.

How do I add Tonone Ai to my agent?

Add the Tonone Ai Claude marketplace, then install tonone, engineering-team, product-team, or full-team bundle plugins from the catalog and follow each plugin’s agent invocation docs on tonone.ai.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.