tonone-ai

Summary

Engineering + Product Teams — 23 Claude Code agents covering engineering and product functions

457 plugins · page 11 of 12

#PluginStars

401terra-moduleTerra skill: terra-module50402terra-reconTerra skill: terra-recon50403tokenAI Operations Team — Token: Context window optimization, token counting, truncation strategies, and chunking patterns for LLM efficiency.50404token-budgetDesign token budgets — system/user/assistant allocation, overflow handling, context compression.50405token-chunkDesign chunking strategies — semantic splitting, overlap tuning, retrieval-aware chunk sizing.50406token-reconAudit token usage patterns — avg context size, waste, truncation frequency, budget adherence.50407toneDesign Token Engineer — Design token engineering — token architecture, theming systems, style-dictionary pipelines50408tone-reconAudit existing token usage in a codebase50409tone-themeBuild or fix a theming system50410tone-tokenDesign or refactor a design token architecture50411tononeEngineering + Product team — 23 agents, 2 teams. All agents and skills in one install.50412tonone-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".50413touchMobile engineer — native iOS/Android, cross-platform, app stores, mobile performance50414touch-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".50415touch-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".50416touch-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".50417touch-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".50418touch-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".50419touch-ui|50420traceAI Operations Team — Trace: LLM tracing, span capture, prompt/completion logging, cost attribution, and AI system debugging.50421trace-debugDebug AI system behavior using traces — prompt reconstruction, output comparison, failure attribution.50422trace-instrumentInstrument LLM calls with tracing — span structure, token counts, latency, model metadata.50423trace-reconAudit LLM observability coverage — trace gaps, logging completeness, cost attribution accuracy.50424tuneLLM Fine-tuning Engineer — LLM fine-tuning — PEFT/LoRA, RLHF, instruction tuning, prompt optimization50425tune-finetuneDesign a fine-tuning pipeline50426tune-promptSystematically optimize prompts for a task50427tune-reconAudit existing fine-tuning or prompt engineering work50428vectEmbeddings & Vector Search Engineer — Embeddings and vector search — semantic search, RAG pipelines, vector database design50429vect-embedDesign an embedding pipeline50430vect-reconAudit existing vector search or RAG implementation50431vect-searchDesign a vector search or RAG system50432vigilObservability & reliability engineer — monitoring, alerting, SRE, incident response, SLOs50433vigil-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".50434vigil-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".50435vigil-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".50436vigil-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".50437vigil-reconObservability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".50438voltEmbedded & IoT engineer — firmware, microcontrollers, edge computing, device protocols50439volt-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".50440volt-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.50