tonone-ai

Analyze and fix a SAST finding — root cause, exploitability, and secure code alternative. Use when asked to "fix this SAST finding", "is this vulnerability exploitable", or "what is the secure alternative to this code".

Use when asked about mobile UI guidelines, touch targets, platform-specific UI rules, or mobile interaction patterns. Examples: "iOS touch targets", "Android UI guidelines", "mobile form design"

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

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth 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.

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

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

Run a WCAG accessibility audit against a component, page, or full product. Use when asked to "run an accessibility audit", "is this WCAG compliant", or "check a11y on this page".

Survey a codebase for accessibility debt — missing ARIA, broken keyboard patterns, and contrast issues. Use when asked "how accessible is our codebase", "find accessibility debt", or "where are our a11y gaps".

Design SLA framework -- response time targets, resolution time targets, tier definitions, and breach escalation process. Use when asked to "define our SLAs", "what response times should we commit to", "build a support tier structure", or "set up SLA monitoring".

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

Content Marketing engineer — blog strategy, SEO, thought leadership, developer content, case studies, and content calendar. Use when asked to "write a blog post", "plan our SEO", "build a content calendar", or "write a case study".

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

PR & Community engineer — press pitches, social media, open source community, DevRel, and coordinated launch moments. Use when asked to "write a press release", "plan a launch", "build a community", "draft a HN or Twitter post", or "get media coverage".

Revenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing. Use when asked to "price this deal", "build a sales playbook", "close an enterprise deal", or "manage the B2B pipeline".

User researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis. Use when asked to "run user interviews", "build personas", "synthesize feedback", or "find the job-to-be-done".

Data engineer — databases, migrations, pipelines, schema design, and query optimization. Use when asked to "design a schema", "write a migration", "build a data pipeline", or "optimize this query".

Visual designer — brand identity, color systems, typography, design tokens, and UI design. Use when asked to "design our brand", "pick colors and fonts", "build a design system", or "design a logo".

Head of product — orchestrate the product team, write briefs, plan initiatives, hand off to Apex. Use when asked to "write a product brief", "plan the roadmap", "decide what to build", or hand off requirements to engineering.

Customer Success engineer — onboarding optimization, health scoring, expansion revenue, churn prevention, and NRR growth. Use when asked to "improve onboarding", "score account health", "prevent churn", or "grow NRR".

Analytics and BI engineer — dashboards, metrics design, reporting pipelines, and data storytelling. Use when asked to "build a dashboard", "design a metric", "write a report", or "audit our analytics".

Platform engineer — developer experience, golden paths, service catalogs, and local dev environments. Use when asked to "improve dev experience", "build a golden path", "audit the service catalog", or "fix local dev setup".

Embedded and IoT engineer — firmware, microcontrollers, OTA updates, device protocols. Use when asked to "write firmware", "design OTA updates", "pick a microcontroller", or "implement a device protocol".

Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports. Use when asked to "write an ADR", "map the architecture", "document this decision", "onboarding docs", or "what changed".

Product strategist — roadmaps, competitive analysis, OKRs, strategic narratives. Use when asked to "build a roadmap", "analyze competitors", "write a strategy memo", "prioritize features", or "set OKRs".

UX designer — user flows, information architecture, wireframes, and interaction design. Use when asked to "design a user flow", "map the IA", "wireframe this screen", or "review UX before shipping".

Infrastructure engineer — cloud services, IaC, networking, cost optimization. Use when asked to "provision infra", "write Terraform", "cut cloud costs", or "design the network".

Product analyst — metrics architecture, funnel analysis, A/B test design, retention, and growth measurement. Use when asked to "design an A/B test", "analyze the funnel", "define a north star metric", or "measure retention".

Product marketer — positioning, messaging, value prop, GTM strategy, and launch copy. Use when asked to "write launch copy", "position this product", "build a GTM plan", or "write messaging".

Frontend engineer — UI components, dashboards, design system implementation, and frontend audits. Use when asked to "build this UI component", "audit the frontend", "implement the design system", or "build a dashboard".

QA and testing engineer — test strategy, E2E suites, API tests, flaky test triage, coverage. Use when asked to "write E2E tests", "design a test strategy", "triage flaky tests", or "check test coverage".

DevOps engineer — CI/CD pipelines, deployments, GitOps, Docker, and developer experience. Use when asked to "set up CI/CD", "fix the deploy pipeline", "containerize this", or "improve GitOps".

Backend engineer — APIs, system design, performance, distributed systems, and service scaffolding. Use when asked to "design this API", "review backend code", "scaffold a service", or "fix a performance issue".

Growth engineer — acquisition channels, activation funnels, retention playbooks, and PLG strategy. Use when asked to "design an activation funnel", "plan a growth experiment", "build a PLG loop", or "improve retention".

Mobile engineer — native iOS/Android, cross-platform, app stores, mobile performance. Use when asked to "build a mobile feature", "fix app store issues", "audit mobile performance", or "release the app".

Observability and reliability engineer — SLOs, alerting, instrumentation, and incident response. Use when asked to "set up alerting", "define SLOs", "write a runbook", or "review incident response".

ML/AI engineer — LLM integrations, prompt engineering, model pipelines, evals, RAG. Use when asked to "add AI to this", "integrate an LLM", "build a RAG pipeline", "evaluate model accuracy", or "improve this prompt".

Security engineer — IAM, secrets, threat modeling, hardening, auth, and supply chain security. Use when asked to "review IAM", "harden this system", "manage secrets", or "audit supply chain security".

Write accessibility fixes for specific WCAG failures — ARIA, focus management, keyboard patterns. Use when asked to "fix this accessibility issue", "add ARIA labels", or "make this keyboard navigable".

Hacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with technical depth, no outbound links, predicted reception analysis, and comment-response templates for likely pushback. Use when asked to "write an HN post", "craft a Show HN", "prepare our Hacker News launch", or "help me post on HN".

Integrate API quality gates into CI — linting, breaking change detection, and coverage checks. Use when asked to "add API checks to CI", "detect breaking changes in CI", or "set up an API quality gate".

SEO strategy and keyword research — build topic clusters, keyword gap analysis, on-page audit, and prioritized SEO roadmap. Use when asked to "improve our SEO", "do keyword research", "build a topic cluster", or "why aren't we ranking".

Run a compliance gap analysis against SOC2, GDPR, HIPAA, or ISO 27001. Use when asked "are we SOC2 ready", "run a GDPR gap analysis", or "what is missing for ISO 27001".

Build or audit knowledge base -- article structure, coverage gaps, deflection rate, and maintenance process. Use when asked to "build a knowledge base", "what docs are missing", "improve our self-serve rate", or "audit our help center".

Design an icon system spec or audit existing icons for consistency and accessibility. Use when asked to "design an icon system", "audit our icons", or "are our icons consistent".

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

Design a CDN configuration — caching rules, TTLs, and origin shield setup. Use when asked to "configure the CDN", "set cache headers", or "set up an origin shield".

Design a hyperparameter tuning strategy for a model — search space, method, and budget. Use when asked to "tune hyperparameters", "define a search space", or "set a tuning budget".