All authors
Claude Skills by tonone-ai
github.com/tonone-ai918 skills5 installs963 views
- RelayDevOps engineer — CI/CD pipelines, deployments, GitOps, Docker, and developer experience.Votes: 0GitHub stars: 71
- Spine 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".Votes: 0GitHub stars: 71
- Spine 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".Votes: 0GitHub stars: 71
- Spine 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".Votes: 0GitHub stars: 71
- Spine 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".Votes: 0GitHub stars: 71
- Spine 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".Votes: 0GitHub stars: 71
- Spine 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".Votes: 0GitHub stars: 71
- SpineBackend engineer — APIs, system design, performance, distributed systems, and service scaffolding.Votes: 0GitHub stars: 71
- Surge ActivationUse when asked to improve activation, map the growth funnel, identify growth levers, design a referral program, build a retention playbook, develop a PLG strategy, or find where to invest in growth. Examples: "how do we grow faster", "improve our activation rate", "design a referral program", "build a retention playbook", "what are our best growth levers", "map our growth funnel".Votes: 0GitHub stars: 71
- Surge 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".Votes: 0GitHub stars: 71
- Surge LandingUse when asked to design growth-optimized landing pages, activation funnel layouts, or experiment-friendly page structures. Examples: "growth-optimized landing", "activation funnel layout", "A/B testable page"Votes: 0GitHub stars: 71
- Surge 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".Votes: 0GitHub stars: 71
- Surge 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.Votes: 0GitHub stars: 71
- Surge 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".Votes: 0GitHub stars: 71
- SurgeGrowth engineer — acquisition channels, activation funnels, retention playbooks, and PLG strategy.Votes: 0GitHub stars: 71
- Tonone OnboardFirst-run onboarding — detect what kind of project this is, recommend a four-agent roster instead of all 100, and print the one-line install command. Use when asked "how do I use tonone", "which agents do I need", "what can tonone do", "show me around", or "first steps".Votes: 0GitHub stars: 71
- Touch 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".Votes: 0GitHub stars: 71
- Touch 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".Votes: 0GitHub stars: 71
- Touch 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".Votes: 0GitHub stars: 71
- Touch 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".Votes: 0GitHub stars: 71
- Touch 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".Votes: 0GitHub stars: 71
- Touch UiUse 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"Votes: 0GitHub stars: 71
- TouchMobile engineer — native iOS/Android, cross-platform, app stores, mobile performance.Votes: 0GitHub stars: 71
- Vigil 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".Votes: 0GitHub stars: 71
- Vigil 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".Votes: 0GitHub stars: 71
- Vigil 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".Votes: 0GitHub stars: 71
- Vigil 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".Votes: 0GitHub stars: 71
- Vigil ReconObservability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".Votes: 0GitHub stars: 71
- VigilObservability and reliability engineer — SLOs, alerting, instrumentation, and incident response.Votes: 0GitHub stars: 71
- Volt 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".Votes: 0GitHub stars: 71
- Volt 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.Votes: 0GitHub stars: 71
- Volt 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".Votes: 0GitHub stars: 71
- Volt 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".Votes: 0GitHub stars: 71
- Volt 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".Votes: 0GitHub stars: 71
- VoltEmbedded and IoT engineer — firmware, microcontrollers, OTA updates, device protocols.Votes: 0GitHub stars: 71
- Warden 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".Votes: 0GitHub stars: 71
- Warden 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".Votes: 0GitHub stars: 71
- Warden 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".Votes: 0GitHub stars: 71
- Warden 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".Votes: 0GitHub stars: 71
- Warden ScanAutomated SAST + dependency vulnerability scan. Runs Semgrep (code vulnerabilities) and pip-audit (CVE-matched dependencies) and writes a structured JSON report. Use when asked to "scan for vulnerabilities", "run a security scan", "check for CVEs", or "audit dependencies".Votes: 0GitHub stars: 71
- Warden 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.Votes: 0GitHub stars: 71
- WardenSecurity engineer — IAM, secrets, threat modeling, hardening, auth, and supply chain security.Votes: 0GitHub stars: 71
- Apex PlanPlan 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.Votes: 0GitHub stars: 71
- Apex 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.Votes: 0GitHub stars: 71
- Apex 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.Votes: 0GitHub stars: 71
- Apex 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.Votes: 0GitHub stars: 71
- Apex 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".Votes: 0GitHub stars: 71
- Atlas 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".Votes: 0GitHub stars: 71
- Atlas 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".Votes: 0GitHub stars: 71
- Atlas 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".Votes: 0GitHub stars: 71