All authors
Claude Skills by tonone-ai
github.com/tonone-ai918 skills5 installs963 views
- Terra ModuleDesign a Terraform module structure — inputs, outputs, resource organization, and versioning. Use when asked to "design a Terraform module", "structure our IaC", or "set up module versioning".Votes: 0GitHub stars: 71
- Terra ReconAudit existing Terraform code — find state issues, security gaps, and module quality problems. Use when asked to "audit our Terraform", "find state management issues", or "check IaC security gaps".Votes: 0GitHub stars: 71
- Token BudgetDesign token budgets — system/user/assistant allocation, overflow handling, context compression. Use when asked "we are blowing the context window", "design a token budget", or "handle context overflow".Votes: 0GitHub stars: 71
- Token ChunkDesign chunking strategies — semantic splitting, overlap tuning, retrieval-aware chunk sizing. Use when asked "how should we chunk documents", "what chunk size for retrieval", or "set up semantic splitting".Votes: 0GitHub stars: 71
- Token ReconAudit token usage patterns — avg context size, waste, truncation frequency, budget adherence. Use when asked to "audit our token usage", "how often do we truncate", or "find context waste".Votes: 0GitHub stars: 71
- Tone ReconAudit existing token usage in a codebase — find literal values, missing tokens, and pipeline gaps. Use when asked to "audit our design tokens", "find hardcoded values in the CSS", or "check our token pipeline".Votes: 0GitHub stars: 71
- Tone ThemeBuild or fix a theming system — dark mode, multi-brand, or white-label token swap. Use when asked to "add dark mode", "set up multi-brand theming", or "white-label the UI".Votes: 0GitHub stars: 71
- Tone TokenDesign or refactor a design token architecture — naming, tiers, and coverage. Use when asked to "design a token architecture", "fix token naming", or "refactor our tokens".Votes: 0GitHub stars: 71
- Trace DebugDebug AI system behavior using traces — prompt reconstruction, output comparison, failure attribution. Use when asked "why did the model output this", "debug this LLM failure", or "reconstruct the prompt".Votes: 0GitHub stars: 71
- Trace InstrumentInstrument LLM calls with tracing — span structure, token counts, latency, model metadata. Use when asked to "add tracing to our LLM calls", "log prompts and completions", or "instrument token counts".Votes: 0GitHub stars: 71
- Trace ReconAudit LLM observability coverage — trace gaps, logging completeness, cost attribution accuracy. Use when asked to "audit our LLM observability", "find trace coverage gaps", or "check cost attribution accuracy".Votes: 0GitHub stars: 71
- Tune FinetuneDesign a fine-tuning pipeline — PEFT config, dataset format, training loop, and evaluation. Use when asked to "fine-tune a model", "set up a LoRA config", or "should we fine-tune or prompt".Votes: 0GitHub stars: 71
- Tune PromptSystematically optimize prompts for a task — few-shot, chain-of-thought, structured output. Use when asked to "optimize this prompt", "add chain-of-thought", or "improve structured output".Votes: 0GitHub stars: 71
- Tune ReconAudit existing fine-tuning or prompt engineering work — find quality gaps and optimization opportunities. Use when asked to "audit our fine-tuning work", "find prompt engineering gaps", or "look for optimization opportunities".Votes: 0GitHub stars: 71
- Vect EmbedDesign an embedding pipeline — model selection, chunking, and indexing strategy. Use when asked to "build an embedding pipeline", "design chunking and indexing", or "which embedding model should we use".Votes: 0GitHub stars: 71
- Vect ReconAudit existing vector search or RAG implementation — find quality gaps and performance issues. Use when asked to "audit our RAG system", "why is retrieval bad", or "find vector search quality gaps".Votes: 0GitHub stars: 71
- Vect SearchDesign a vector search or RAG system — retrieval strategy, reranking, and database selection. Use when asked to "build a RAG system", "design vector search", or "which vector database should we use".Votes: 0GitHub stars: 71
- Wire PrototypeDocument a prototype or user flow — screens, states, transitions, and annotations. Use when asked to "document this prototype", "map the screens and states", or "annotate this flow".Votes: 0GitHub stars: 71
- Wire ReconAudit existing design documentation — find gaps in specs, missing states, and handoff debt. Use when asked to "audit our design docs", "find missing component states", or "assess handoff debt".Votes: 0GitHub stars: 71
- Wire SpecWrite 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".Votes: 0GitHub stars: 71
- Zero AuditAudit an existing environment against zero trust principles — find implicit trust and over-privileged access. Use when asked to "audit against zero trust", "find implicit trust", or "find over-privileged access".Votes: 0GitHub stars: 71
- Zero DesignDesign a zero trust architecture — phased roadmap, identity pillar, and network segmentation. Use when asked to "design a zero trust architecture", "build a zero trust roadmap", or "plan network microsegmentation".Votes: 0GitHub stars: 71
- Zero ReconSurvey existing network and identity controls for zero trust readiness. Use when asked "are we ready for zero trust", "survey our identity controls", or "assess our network segmentation".Votes: 0GitHub stars: 71
- Proof 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".Votes: 0GitHub stars: 71
- Proof DesignDesign QA audit — red flags, severity classification, visual quality scorecard. Use when asked to "QA the design", "check visual quality", "design review before launch", "visual bugs", "design audit", or "does this look right".Votes: 0GitHub stars: 71
- Proof 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".Votes: 0GitHub stars: 71
- Proof 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".Votes: 0GitHub stars: 71
- Relay 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".Votes: 0GitHub stars: 71
- Relay 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".Votes: 0GitHub stars: 71
- Relay 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".Votes: 0GitHub stars: 71
- Relay PipelineBuild a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".Votes: 0GitHub stars: 71
- Relay 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".Votes: 0GitHub stars: 71
- Relay 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".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
- 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
- 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