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".
The English summary is being prepared. Showing the original description.
Design a consumer-driven contract testing setup — Pact configuration and CI integration. Use when asked to "set up contract testing", "configure Pact", or "add consumer-driven contracts".
The English summary is being prepared. Showing the original description.
Design a motion system for a product — duration tokens, easing curves, and animation principles. Use when asked to "design a motion system", "define duration and easing tokens", or "document animation principles".
The English summary is being prepared. Showing the original description.
Design a multi-cloud or cloud portability strategy — provider selection, workload placement, and lock-in management. Use when asked "should we go multi-cloud", "design for cloud portability", or "where should this workload run".
The English summary is being prepared. Showing the original description.
Survey pending and required regulatory filings. Use when asked "what filings are due", "survey our regulatory filings", or "are we behind on filings".
The English summary is being prepared. Showing the original description.
Survey existing cloud architecture for lock-in depth and portability gaps. Use when asked to "survey our cloud lock-in", "find portability gaps", or "how cloud-agnostic are we".
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Customer segmentation model builder — tiers customers by ARR, health, and expansion potential; defines CS motion per tier; maps resource allocation. Use when asked to "segment our customers", "define our CS tiers", "how should we allocate CS resources", "build a customer segmentation model", or "who gets high-touch vs. digital".
The English summary is being prepared. Showing the original description.
Survey existing onboarding docs and developer portal — find gaps and structural issues. Use when asked to "survey our onboarding docs", "find developer portal gaps", or "review our onboarding structure".
The English summary is being prepared. Showing the original description.
Calculate and extend runway — current cash, burn rate, runway months, and the levers available to extend it. Use when asked to "how long is our runway", "when do we run out of money", or "what cuts extend runway by 6 months".
The English summary is being prepared. Showing the original description.
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".
The English summary is being prepared. Showing the original description.
Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like. Given a product area, outputs the full metrics spec. Use when asked to "define KPIs", "metrics framework", "what should we measure", "north star metric", or "instrument this feature".
The English summary is being prepared. Showing the original description.
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".
The English summary is being prepared. Showing the original description.
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".
The English summary is being prepared. Showing the original description.
Design service mesh observability — distributed tracing, service-level metrics, and dashboards. Use when asked to "add service mesh observability", "set up distributed tracing in the mesh", or "build service-level dashboards".
The English summary is being prepared. Showing the original description.
Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.
The English summary is being prepared. Showing the original description.
Design an animation spec for a component or interaction — timing, easing, and keyframes. Use when asked to "animate this component", "spec the transition", or "define easing and timing for this interaction".
The English summary is being prepared. Showing the original description.
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".
The English summary is being prepared. Showing the original description.
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".
The English summary is being prepared. Showing the original description.
Use when asked to analyze a funnel, find where users drop off, diagnose low conversion or activation rates, design a metrics framework, set up OKRs, or measure whether a feature is working. Examples: "analyze our funnel", "why is activation low", "where are users dropping off", "design OKRs for this quarter", "is this feature working", "set up metrics for this launch".
The English summary is being prepared. Showing the original description.
A/B test design — produce an experiment spec with hypothesis, primary metric, MDE, sample size, run time, and decision rule. Also determines when NOT to A/B test and what to do instead. Use when asked to "design an A/B test", "should we test this", "experiment design", "how do we know if this works", "what's the sample size", or "set up an experiment".
The English summary is being prepared. Showing the original description.
Design a service mesh deployment — technology selection, mTLS policy, and traffic management config. Use when asked "should we use a service mesh", "Istio or Linkerd", or "design our mTLS policy".
The English summary is being prepared. Showing the original description.
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".
The English summary is being prepared. Showing the original description.
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".
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)