「your」の検索結果

Builds your north star metric, a metric tree with owned input metrics and guardrails, and a review cadence, as a one-page metrics spec you can paste into a doc. Use it when you ask 'what should our north star be', 'which metric should this team goal on', 'our dashboard is a mess', 'how do we measure AI productivity', 'activation metric', 'OKR metrics', 'vanity metrics', or 'metrics review cadence'. Draws on 254 insights from 118 Lenny's Podcast guests incl. Sarah Tavel, Crystal Widjaja and Jessica Lachs.

日本語の概要は準備中です。原文の説明を表示しています。

Builds a product strategy and stress-tests your moat, then writes a one-page strategy doc (diagnosis, where to play, how to win, guiding policy, coherent actions, moat verdicts). Use for 'we need a product strategy', 'is our moat real', 'do we have a competitive advantage', 'where should we play', 'defensibility', 'should we expand into X', 'our roadmap has no strategy', or 'write a product vision'. Draws on 909 insights from 236 Lenny's Podcast guests incl. Roger Martin, Richard Rumelt and Hamilton Helmer.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnoses why your product team ships slowly and produces a velocity plan with a baseline, a bottleneck map, the top 3 interventions and a stop-doing list. Use it when you say 'we're too slow', 'how do we ship faster', 'projects keep slipping', 'too many meetings', 'approvals take forever', 'our releases are scary', 'velocity', 'cycle time', 'we hired more people and nothing got faster' or 'AI made coding fast but we still ship slowly'. Draws on 226 Lenny's Podcast guests including Farhan Thawar, Nicole Forsgren and Melissa Perri.

日本語の概要は準備中です。原文の説明を表示しています。

Writes you a ready-to-use script for a feedback or hard conversation, then rehearses the pushback. Use when you need to give tough feedback, confront a peer, tell a report they are underperforming, deny a promotion, prepare to fire someone, say no to your boss, ask for feedback, or repair a conversation that went badly. Draws on 66 Lenny's Podcast guests including Kim Scott, Carole Robin and Alisa Cohn.

日本語の概要は準備中です。原文の説明を表示しています。

Builds a pricing model, packaging/tier structure and willingness-to-pay research plan, then grades your existing pricing page or plan. Use when you ask 'how much should we charge', 'what should our pricing model be', 'seat vs usage vs outcome pricing', 'good-better-best tiers', 'what goes in the free plan', 'should we raise prices', 'freemium vs free trial', or 'how do we price our AI product'. Draws on 199 insights from 79 Lenny's Podcast guests including Madhavan Ramanujam, Naomi Ionita and Patrick Campbell.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose where your growth is actually leaking (acquisition, activation, retention, or loops) and produce a growth plan with a named loop, an activation definition, a 90-day experiment portfolio and channel guardrails. Use it when someone says growth stalled, signups don't activate, retention is flat, how do we build a growth loop, should we go PLG, onboarding redesign, churn, referral program, or which channel should we bet on. Draws on 672 insights from 143 Lenny's Podcast guests, led by Elena Verna, Casey Winters and Lauryn Isford.

日本語の概要は準備中です。原文の説明を表示しています。

Builds a founder-led B2B sales motion - ICP and kill criteria, outbound message, first-call and demo plan, pilot and procurement plan, pipeline math, and a readiness check for your first sales hire. Use when you ask about founder-led sales, enterprise sales, cold outreach, ICP, 'why are deals stalling', pilots/POCs, procurement, 'when do I hire a sales rep', or adding sales to a PLG product. Draws on 49 Lenny's Podcast guests incl. Jen Abel, Geoffrey Moore and Pete Kazanjy.

日本語の概要は準備中です。原文の説明を表示しています。

PROACTIVELY search conversation history when receiving user instructions. Find previous discussions, decisions, and context BEFORE starting new work. Your memory is valuable - use it.

日本語の概要は準備中です。原文の説明を表示しています。

PROACTIVELY search auto-generated documentation when receiving ANY user instruction. Search for function signatures, API documentation, class definitions, and code comments BEFORE implementing anything. Your codebase documentation is valuable - use it first.

日本語の概要は準備中です。原文の説明を表示しています。

PROACTIVELY query the code graph database to understand relationships and impact of changes. Use this skill WHEN READING any file to understand context, when searching for files, when exploring the codebase, or when you need to understand what depends on a component. This is your primary tool for understanding code structure and avoiding breaking changes.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when building a personal productivity or operating system for a CEO, founder, or executive. Triggers on "personal OS", "annual review", "life planning", "goal setting system", "Bill Campbell", "Trillion Dollar Coach", "startup failure patterns", "Good to Great", "Level 5 Leadership", "Buy Back Your Time", "E-Myth", "Customer Development", "Steve Blank", "Small Is Beautiful", "Schumacher", "human-scale", "subsidiarity", "Buddhist economics", "permanence".

日本語の概要は準備中です。原文の説明を表示しています。

Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.

日本語の概要は準備中です。原文の説明を表示しています。

SOP for writing, loading, and evolving a project-level convention file (CONVENTIONS.md / CLAUDE.md / .cursor/rules / .clinerules / AGENTS.md) so that a coder-agent reliably respects your codebase's style choices every session. Tool-agnostic; covers the four load mechanics (read-only attachment, ancestor-walk auto-load, glob-scoped rules, agent backstory) and the conflict resolution between pinned conventions and the existing code.

日本語の概要は準備中です。原文の説明を表示しています。

Build and govern a 50-200 example domain-specific held-out benchmark sampled from real traffic. Distinct from public benchmarks (MMLU/HumanEval/GSM8K via lm-evaluation-harness) which measure GENERAL capability. Only a held-out domain set predicts whether THIS system works on YOUR data. Collect real examples, label, hold out (never train/prompt on it), size 50-200, version it, refresh on drift.

日本語の概要は準備中です。原文の説明を表示しています。

Enhancement-overlay skill — the DECISION + WIRING layer for LM observability that the single-backend skills [[langsmith]], [[phoenix]], [[mlflow]] do NOT cover. Each of those installs one backend; none of them help you DECIDE which backend fits your stack/scale/budget, nor give you a one-line autolog that turns it on fast. Use when starting any LM project, before the first deploy, or the moment someone asks "why did it do that?" and there are no traces to answer with. The skill picks a backend by stack (LangSmith for LangChain/LangGraph; Phoenix for OSS/local OpenTelemetry; MLflow for ML-shops already on MLflow; Langfuse for self-host), wires one-line autolog, verifies traces land, and adds eval hooks — instrumenting BEFORE you need it. Cross-links the first-debug-move skill [[agentsop-prompt-history-inspect]]. Do NOT activate to re-teach a backend you already chose (defer to its own skill), or for non-LM ML experiment tracking with no LLM calls (that is plain MLflow).

日本語の概要は準備中です。原文の説明を表示しています。

Project-kickoff rubric for the self-host vs managed-cloud decision — when is running your own inference engine / LLM platform worth the ops cost vs paying per-token for a managed API? Decide on two axes — VOLUME (a cost-crossover slider) and COMPLIANCE (a hard gate). Use at kickoff when choosing where to run inference, or when cost / data-residency pressure forces a re-evaluation.

日本語の概要は準備中です。原文の説明を表示しています。

Map your security posture against the NIST Cybersecurity Framework 2.0 (Govern, Identify, Protect, Detect, Respond, Recover). Produce a gap analysis, current/target tier assessment, and roadmap in the governance language that boards, auditors, and CISOs actually use. Use when the user mentions 'NIST CSF,' 'CSF 2.0,' 'cybersecurity framework,' 'security posture,' 'governance mapping,' 'CSF gap analysis,' 'CSF tiers,' 'cybersecurity maturity,' 'security roadmap,' 'CISO report,' 'board reporting,' 'security program,' or needs to translate technical findings into governance language.

日本語の概要は準備中です。原文の説明を表示しています。

Research a specific CVE or vulnerability disclosure end-to-end — what version is affected, is your code reachable, is there a public PoC, is there a patch, what's the exposure window, what's the mitigation if you can't patch immediately. Use when the user mentions 'CVE,' 'vulnerability research,' 'is this CVE relevant,' 'zero-day,' 'CISA KEV,' 'GitHub Security Advisory,' 'reachability analysis,' 'patch analysis,' 'exploit availability,' 'EPSS,' 'CVSS,' or 'should we drop everything and patch this.'

日本語の概要は準備中です。原文の説明を表示しています。

Interactive project setup — detects your project, configures metaswarm, writes project-local files

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

日本語の概要は準備中です。原文の説明を表示しています。

Assist with core product management activities including writing PRDs, analyzing features, synthesizing user research, planning roadmaps, and communicating product decisions. Use when you need help with PM documentation, analysis, or planning workflows that integrate with your codebase.

日本語の概要は準備中です。原文の説明を表示しています。

Personalize COG for your workflow - creates profile, interests, and watchlist files with guided setup (run this first!)

日本語の概要は準備中です。原文の説明を表示しています。

Intelligent pattern selection for Fabric CLI. Automatically selects the right pattern from 242+ specialized prompts based on your intent - threat modeling, analysis, summarization, content creation, extraction, and more. USE WHEN processing content, analyzing data, creating summaries, threat modeling, or transforming text.

日本語の概要は準備中です。原文の説明を表示しています。

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.

日本語の概要は準備中です。原文の説明を表示しています。