When the user wants to plan, run, or read A/B tests, or asks a judgement call on one: is the result real, can we stop, which version won, is this worth testing at all: sample size, duration, significance, hypotheses, and experiment backlogs. For tracking setup, see analytics. For page-level conversion fixes, see cro.

OpenInference semantic conventions and instrumentation for Phoenix AI observability. Use when implementing LLM tracing, creating custom spans, or deploying to production.

Creates and manages isolated cloud sandboxes (secure code execution environments with dedicated runtimes) on the Daytona platform. Use when a task needs an isolated runtime, sandbox, secure compute, or Daytona SDK/API/CLI operations. Covers Python, TypeScript, Java, Go, and Ruby SDKs.

Use when reviewing actual translation quality (correctness, naturalness, consistency) for multi-language sites — checking for literal phrasing, broken placeholders, untranslated leftovers, and terminology drift. NOT a substitute for professional translator sign-off on launch-critical copy, NOT a key-parity check.

Use when auditing third-party scripts, resources (analytics, fonts, chat widgets), and their data access — checking SRI coverage, CSP allowlist alignment, and vendor data leakage risks. NOT a full penetration test or server-side dependency-vulnerability scan, NOT a standalone GDPR/consent-banner completeness check.

Use when comparing real-user field performance data (CrUX/RUM) against lab Lighthouse data to find divergences where pages score well in the lab but are slow for real users. NOT a replacement for the Lighthouse/lab baseline, NOT for setting up RUM/analytics from scratch, NOT for synthetic load/stress testing.

Specify one component — props, states, variants, accessibility, and usage rules. Use when defining a library component. For the reusable doc scaffold use `documentation-template`; for a problem-solution pattern use `pattern-library`.

Define motion tokens — durations, easing vocabulary, and reduced-motion handling — for consistency product-wide. Use when standardising motion across a system. For crafting one specific animation, use `animation-principles` (interaction-design).

Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use `ux-writing` (designer-toolkit).

Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use `a-b-test-design` (prototyping-testing).

Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use `summarize-interview`.

Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches.

Deprecated alias. This skill was renamed to `deepline-scoring`. Use when a user or script still invokes `/niche-signal-discovery`: immediately load and follow the `deepline-scoring` skill instead. Triggers: ICP analysis, niche signals, won vs lost analysis, differential signals, signal discovery, ICP signal report, account scoring signals, lead scoring, first-party signals, buyer signals.

乔布斯的视角：产品判断与评审、取舍决策、对人对事的直接反馈。说「用乔布斯的视角」「乔布斯会怎么看」「切换到乔布斯」「让乔布斯评一下」时使用；不在一般性问题上自动触发。

Deploy and manage MCP servers on Manufact Cloud with the mcp-use CLI, including authentication, projects, environments, deployments, domains, organizations, publishing checks, and YAML alerts.

Review pull requests or a cross-repository work package in an interactive browser Cockpit, with evidence-backed stories, Qodo findings, local reviewer notes and marks, refresh/resume and HTML export. Use for reviewing PRs together or opening the review cockpit. Use qodo-review for local diffs, qodo-review-resolver for stored finding dispositions, and qodo-review-notes for authoring reviewer context.

Understand how code works, how a change was done before, and which repos are coupled — to answer a question, plan a code change, debug a regression, or scope a fix, using Qodo managed tools through MCP or the CLI. Use when a task needs to understand a codebase, its history, or how its repos relate — especially for a repo you don't have checked out or work spanning repos — "how does X work", "where is X defined", "who changed X", "explain this service", "plan the change for X", "what would changing X affect", "which repos depend on X", "why did X regress / when did it break", "has this been fixed before", "how did we solve X".

Discover, configure, and manage Qodo Review Standards using managed tools through MCP or the CLI. Use to set up a skills/plugin repository for reviews, map review skills to target repositories, change skill scope or rules/steering mode, capture a convention as a rule, edit or deactivate rules, or triage suggestions. For reading and applying rules use qodo-get-rules; installing local coding-agent skills uses qodo-setup.

Discover, configure, and manage Qodo Review Standards using managed tools through MCP or the CLI. Use to set up a skills/plugin repository for reviews, map review skills to target repositories, change skill scope or rules/steering mode, capture a convention as a rule, edit or deactivate rules, or triage suggestions. For reading and applying rules use qodo-get-rules; installing local coding-agent skills uses qodo-setup.

Use when about to claim a Zipper change is done, fixed, or passing, especially for CLI behavior, Load File formats, Production Sets, or output bytes, to gather real-artifact evidence before the claim.