tonone-ai

Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".

Product 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.

Design a threat hunting program — maturity assessment, hunting calendar, and playbook library. Use when asked to "build a threat hunting program", "assess our hunting maturity", or "create a hunt playbook library".

Operational efficiency audit — identify waste, redundancy, and friction across processes, tools, and team workflows. Use when asked to "audit our operations for waste", "where are we inefficient", "what tools are we paying for but not using", or "reduce operational overhead".

Draft or review legal ops documents — NDA, MSA, SaaS agreement review checklist, vendor contract terms. Use when asked to "review this contract", "draft an NDA", "what should I look for in this agreement", or "build our contract review process".

Operations reconnaissance — audit process documentation, vendor contracts, compliance posture, OKR health, and cross-functional friction points to understand where operations is the bottleneck. Use when asked to "audit our operations", "where are we slow", "what processes are broken", or "before designing a compliance program".

Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", or "rescue this account".

Customer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.

Audit an existing Kubernetes cluster — find misconfigurations, security gaps, and resource issues. Use when asked to "audit our Kubernetes cluster", "find K8s misconfigurations", or "check cluster security gaps".

Review 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".

Use when asked to select chart types for analytics dashboards, choose BI visualizations, or design data displays. Examples: "best chart for sales data", "dashboard visualization for metrics", "analytics chart selection"

Analytics 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".

Draft DMCA takedown notice or counter-notice. Use when asked to "file a DMCA takedown", "respond to a DMCA notice", or "draft a counter-notice".

Design an asset library structure — naming conventions, formats, and delivery specs. Use when asked to "organize our brand assets", "define asset naming conventions", or "spec logo delivery formats".

Write brand guidelines — logo usage, color, typography, voice, and visual principles. Use when asked to "write brand guidelines", "define logo usage rules", or "document our visual identity".

Audit existing brand assets and usage — find inconsistencies, off-brand applications, and gaps. Use when asked to "audit our brand assets", "find off-brand usage", or "check brand consistency".

Audit existing service mesh configuration — find mTLS gaps, traffic policy issues, and observability holes. Use when asked to "audit our service mesh", "find mTLS gaps", or "review traffic policy issues".

Produce board financial package — monthly or quarterly financial update with P&L, cash position, key metrics, and variance vs plan. Use when asked to "prepare board materials", "write the financial section of the board deck", or "what metrics does the board care about".

Build or audit a financial model — 3-statement model (P&L, cash flow, balance sheet), scenario analysis, and sensitivity tables. Use when asked to "build a financial model", "model our growth scenarios", or "what happens to runway if we hire 5 people".

Prepare fundraising financial materials — investor model, data room financial docs, cap table, and use-of-funds narrative. Use when asked to "prepare for Series A", "build our investor model", or "what financials do investors want".

Financial reconnaissance — audit current P&L, burn rate, runway, unit economics, and financial health to understand where the constraint is. Use when asked to "audit our finances", "what is our runway", "are our unit economics healthy", or "before building a financial model".

Audit existing mocks and test doubles — find contract drift, missing error cases, and stale fixtures. Use when asked to "audit our mocks", "find stale test fixtures", or "check for contract drift".

Audit existing animations in a codebase — find inconsistencies, missing reduced-motion support, and performance issues. Use when asked to "audit our animations", "check reduced-motion support", or "our animations are janky".

Assess and improve cloud portability — identify lock-in, prioritize abstraction, and design migration paths. Use when asked "how locked in are we", "reduce vendor lock-in", or "plan a cloud migration".

Design a vulnerability management program — SLAs, asset tiers, escalation, and metrics. Use when asked to "design a patching program", "set vulnerability SLAs", or "define our patch cadence".

Audit 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".

Platform 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".

Landing 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]".

Design or critique a data visualization — chart type selection, encoding, and clarity. Use when asked "what chart should I use", "critique this visualization", or "design this chart".

Audit existing visualizations in a codebase or notebook — find misleading charts and quality issues. Use when asked to "audit our charts", "find misleading visualizations", or "review chart quality".

Audit multi-language SDK coverage — find missing languages, inconsistencies, and maintenance gaps. Use when asked to "audit our SDK coverage", "find missing language SDKs", or "review SDK maintenance gaps".

Design an SBOM generation pipeline — format, tooling, and integration into CI/CD. Use when asked to "generate an SBOM", "build an SBOM pipeline", or "add CycloneDX to CI".

Design a dependency scanning program — CVE detection, license checks, and CI gates. Use when asked to "scan our dependencies", "set up CVE detection", or "add a dependency CI gate".

Design a game day — simulated failure scenario, runbook, and post-event review. Use when asked to "run a game day", "plan a failure drill", or "simulate an outage".

Survey open legal questions and research gaps in the project. Use when asked "what legal questions are open", "where are our research gaps", or "list unresolved legal issues".

Audit UX copy in a product or codebase — find passive errors, generic labels, missing states. Use when asked to "audit our UX copy", "our error messages are bad", or "review the microcopy".

Survey all user-facing strings in a codebase — map coverage and find gaps. Use when asked "what user-facing strings do we have", "map our copy coverage", or "find hardcoded strings".

Write UX copy for a feature, flow, or component — buttons, errors, empty states, tooltips. Use when asked to "write the copy for this flow", "word this error message", or "write empty state copy".

Close a specific deal — diagnose why a deal is stalling, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", or "help me get to yes".

Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".

Use when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this".

User 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.

Audit existing CDN and edge configuration — find cache misses, missing headers, and performance gaps. Use when asked to "audit our CDN", "why is our cache hit rate low", or "find edge config gaps".

Design an edge routing and geo-distribution strategy — latency routing, failover, and edge logic. Use when asked to "geo-route our traffic", "reduce global latency", or "design edge failover".

Audit existing experimentation infrastructure and past experiments for methodology issues. Use when asked to "audit our experiments", "is our experimentation sound", or "review past test methodology".

Audit feature engineering code for leakage, quality issues, and pipeline correctness. Use when asked to "audit our feature pipeline", "is there data leakage", or "find feature quality issues".

Design or audit a feature store — serving, freshness, and sharing across models. Use when asked "do we need a feature store", "design a feature store", or "share features across models".

Optimize slow database queries — analyze execution plans, add indexes, rewrite queries. Use when asked about "slow query", "optimize SQL", "query performance", or "explain this query".

Database 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".

People reconnaissance - audit org design, hiring pipeline, comp structure, onboarding, and performance systems to understand what is working and where the constraint is. Use when asked to "audit our people ops", "what is broken in our hiring", "review our org structure", or "before designing a comp framework".

Audit 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".

Audit existing icons and illustrations in a codebase — find inconsistencies, unoptimized SVGs, and accessibility gaps. Use when asked to "audit our icons and illustrations", "find unoptimized SVGs", or "find inconsistent assets".

Jobs-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".

Audit existing model training code — find reproducibility issues, data leakage, and missing best practices. Use when asked to "audit our training code", "is our training reproducible", or "check for training data leakage".

Design a model training pipeline — algorithm selection, cross-validation, and serialization. Use when asked to "train a model for this", "design a training pipeline", or "which algorithm should we use".

Design compensation framework - salary bands, equity philosophy, offer templates, and total comp benchmarking. Use when asked to "design our comp bands", "how much equity should we give", "is our comp competitive", or "write an offer template".

Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".

Design performance management system - review cycles, calibration process, career ladder, and PIP framework. Use when asked to "build a performance review process", "design career levels", "how do we handle underperformers", or "run a review cycle".

Use when asked to design a pitch deck, presentation, or slide set. Examples: "design a pitch deck", "create a sales deck", "make a conference presentation", "build an investor deck", "help me present this to the board", "create slides for X".

Theory-backed design audit — names the principle violated, cites the source, shows the fix. Use when asked to "evaluate design quality", "check if this follows design principles", "theory check", "design exam", "audit against best practices", or "what's wrong with this design".

Use when asked to create a logo, design a brand mark, generate a logo concept, or produce any logo asset. Examples: "create a logo for X", "design a brand mark", "make me a logo", "generate logo concepts", "logo for our product".

Design an API linting ruleset — style rules, severity levels, and custom organization conventions. Use when asked to "design an API lint ruleset", "enforce API style", or "write Spectral rules".

Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".

Audit existing color usage in a codebase — find inconsistencies, hardcoded values, and contrast failures. Use when asked to "audit our color usage", "find hardcoded hex values", or "check for contrast failures".

Audit or refactor a design token system for color — naming, structure, and coverage. Use when asked to "refactor our color tokens", "fix color token naming", or "improve token coverage for color".

Content brief generator — takes a topic or keyword and produces a complete content brief with target keyword, search intent, recommended structure, internal link targets, word count, CTA, and competitive gap analysis. Use when asked to "write a content brief", "brief this blog post", "plan this article", or "what should we cover for [keyword]".

Content marketing reconnaissance — audit current content, SEO health, competitor content gaps, and content distribution. Use when asked to "audit our content", "what's our SEO state", "where are the content gaps", or before designing a content strategy.

Design or audit Kubernetes RBAC — roles, bindings, service accounts, and least-privilege model. Use when asked to "audit Kubernetes RBAC", "apply least privilege in K8s", or "review service account permissions".

Audit and improve unit economics — LTV, CAC, payback period, gross margin, contribution margin. Use when asked to "are our unit economics good", "what is our LTV/CAC", or "how do we improve gross margin".

Build 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".

Build 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".

Build ranking evaluation — NDCG/MRR measurement, human relevance labeling, offline eval harness. Use when asked to "measure ranking quality", "compute NDCG for our search", or "set up human relevance labeling".

Design a reconnaissance plan — OSINT, attack surface mapping, and enumeration methodology. Use when asked to "map our attack surface", "run OSINT on our org", or "build an enumeration plan".

Design a SAST/DAST scanning pipeline — tooling selection, CI integration, and triage workflow. Use when asked to "set up SAST in CI", "add DAST scanning", or "build a security scanning pipeline".

Open source license compliance audit — flag GPL, LGPL, AGPL, copyleft risks. Use when asked to "check our open source licenses", "do we have GPL risk", or "run an OSS license audit".

Diagnose and optimize Lambda/serverless cold start performance. Use when asked to "fix Lambda cold starts", "our functions are slow to start", or "reduce cold start latency".

Write SIEM detection rules for a threat or TTP — SIGMA format, MITRE mapping, and test cases. Use when asked to "write a SIGMA rule", "build a detection rule for this TTP", or "map a SIEM rule to MITRE".

Design 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".

PLG 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".

Draft Terms of Service for the described product. Use when asked to "write Terms of Service", "draft our ToS", or "write a user agreement".

Produce 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".

Write a developer handoff spec for a component or feature — states, tokens, edge cases. Use when asked to "write a handoff spec", "spec this component for engineering", or "document component states".

Engineering 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.

Reach ANY tonone specialist on demand, even ones not installed in this session's roster — no restart needed. Use when asked "which agent handles this", "reach a specialist we didn't install", "route this to the right agent", or whenever a scoped apex-profile roster is missing the right hat for the job.

Spawn-count analytics for the tonone roster — which agents this project actually uses, from local session transcripts. Use when "which agents do we actually use", "show tonone stats", "prune the roster", or before running apex-profile.

Survey existing compliance artifacts — policies, audits, certifications. Use when asked "what compliance docs do we have", "survey our policies", or "inventory our compliance artifacts".

Audit existing security controls and detection coverage — find gaps against MITRE ATT&CK. Use when asked to "audit our detection coverage", "where are our security control gaps", or "check our MITRE coverage".

Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".

PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.

Survey existing forecasting code or models in a codebase — find gaps, stale models, and missing validation. Use when asked "what forecasting models do we have", "audit our forecasts", or "find stale models".

Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".

Use when asked to design a landing page, marketing website, or any web presence intended to convert or inform. Examples: "design a landing page for X", "create a marketing site", "we need a homepage", "design our website", "build a page for our launch".

Analyze indicators of compromise — enrichment, attribution, and response recommendations. Use when asked to "analyze these IOCs", "enrich these indicators", or "what is this hash".

Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to "write a case study", "document a customer success story", "create social proof content", or "write about how [customer] uses the product".

Write a blog post or article — research the keyword, draft the post, and produce publish-ready content with SEO optimization. Use when asked to "write a blog post", "write about [topic]", "draft an article", or "write a tutorial".

Design and run OKR program — company objectives, team key results, cascade design, and quarterly review cadence. Use when asked to "design our OKRs", "are our OKRs good", "cascade goals to teams", or "run a quarterly OKR review".

Quarterly Business Review template generator — takes account info (ARR tier, adoption metrics, goals) and produces a complete QBR deck outline and talking points. Use when asked to "prepare a QBR", "build a quarterly review", "write our QBR agenda", or "create QBR talking points for this account".

Set 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".

Design an exploratory data analysis workflow for a dataset. Use when asked to "explore this dataset", "run an EDA", or "what is in this data".

Implement 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".