Explore skills

Structure effective collaboration patterns between product and engineering for discovery, estimation, and trade-off decisions. Use this skill when product-engineering collaboration is creating friction or misalignment.

Use when the user is explicitly inside the Claws Temple Bounty 2.0 workflow, names Claws Temple / 龙虾圣殿 / Claws Temple Bounty 2.0, or is already continuing this branded five-task path. This skill packages the five-step journey that sends an Agent into the wild to make friends. Do not use for generic numbered tasks, generic bounty requests, or unrelated partner-matching requests outside this brand c

Ensure product decisions are aligned with the revenue model, pricing strategy, and commercial goals. Use this skill when a team needs to check or strengthen alignment between product direction and revenue outcomes.

Structure the trade-off decision between addressing technical debt and delivering new product value. Use this skill when a team needs to make explicit, principled decisions about when and how to invest in technical debt reduction.

Evaluate the current pricing model against customer behavior, competitive context, and business goals to identify structural improvements. Use this skill when pricing may be limiting growth or not capturing full value.

Frame a return-on-investment analysis for a product initiative to support investment decisions. Use this skill when a team needs to quantify the expected return on a product investment relative to its cost.

Synthesize large volumes of customer feedback into structured themes and actionable product signals. Use this skill when feedback has been collected and needs to be organized into patterns that inform product decisions.

After fixing a bug, find and rate other instances of the same pattern in the codebase. Two modes: described, or inferred from a recent fix with self-validation. Triggers: "run bug-echo", "echo this fix", "scan for similar bugs", "find other instances", "after-fix scan".

Recommend what to do after an experiment based on the result quality, effect size, and business context. Use this skill when the user has a completed experiment and needs a practical product decision such as roll out, rerun, iterate, segment-rollout, or reject.

This skill is used for session handoff or to provide a structured end-of-session summary before clearing context. It generates a chat-only handoff detailing decisions, changes, key files, running state, verification steps, deferrals, and open questions for seamless agent continuation.

Identify and map the compounding growth loops embedded in a product. Use this skill when a team wants to understand what mechanisms drive self-reinforcing growth and how to strengthen them.

Audit the current state of product processes to identify bottlenecks, inconsistencies, and improvement opportunities. Use this skill when a product team wants to understand where their operating model is breaking down.