「should」の検索結果

Use when you need to apply Java concurrency best practices — including thread safety fundamentals, ExecutorService thread pool management, concurrent design patterns like Producer-Consumer, asynchronous programming with CompletableFuture, immutability and safe publication, deadlock avoidance, virtual threads, structured concurrency, scoped values, backpressure, cancellation discipline, and observability for concurrent systems. This should trigger for requests such as Review Java code for concurrency; Review Java code for thread safety; Fix race conditions in Java concurrency code; Choose ExecutorService or virtual threads in Java; Improve synchronization and shared mutable state handling; Apply structured concurrency for related Java subtasks. Part of Plinth Toolkit

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

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

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

Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a consultative, question-driven approach that adds only what you actually need. This should trigger for requests such as Add Maven dependencies; Add JSpecify nullness dependencies; Add Error Prone NullAway dependencies; Add VAVR functional dependencies; Add ArchUnit architecture testing dependencies; Add JavaMoney dependencies. Part of Plinth Toolkit

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

Use when a problem or issue needs explicit framing before deeper analysis begins — establishing the Problem statement, Current state, Desired state, Stakeholders, and Success criteria. This should trigger when an issue's Problem Framing point of view needs evaluation, or when a maintainer directly asks to frame a problem before root-cause analysis, design, or planning begins. Part of Plinth Toolkit

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

Turns a product or startup idea into a ranked list of riskiest assumptions, the cheapest test for each, pass/kill thresholds, and a go/pivot/kill readout, before anyone builds. Use when someone says "validate my idea", "is this worth building", "what's the riskiest assumption", "design an MVP", "fake door", "smoke test", "will people pay", "pre-sell", "customer discovery plan" or "should we build this". Draws on 82 Lenny's Podcast guests incl. Mike Maples Jr., Eric Ries and Jake Knapp.

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

Runs a product quality review on a journey, feature, landing page, onboarding flow, or AI/agent surface and returns a friction log, a scored critical-journey review, and a taste bar your team can calibrate against. Use when someone asks is this good enough to ship, how polished should it be, why do users bounce, what is our quality bar, how do we build taste, or to review a design, prototype, onboarding, or checkout. Draws on 264 insights from 100 Lenny's Podcast guests incl. Katie Dill, Dylan Field and Stewart Butterfield.

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

Decide which AI features to build, delay, shelve or kill, and whether each one gets better as models improve. Produces an AI Bet Memo (feature-by-feature verdicts, retest triggers, scaffolding ledger, moat and safety check) from a roadmap or idea list. Use for 'AI strategy', 'AI roadmap', 'what should we build with AI', 'will the next model make this obsolete', 'build vs wait for the model', 'will OpenAI/Anthropic build this', 'agent or chatbot', 'is this feature worth shipping'. Draws on 118 Lenny's Podcast guests incl. Nick Turley, Kevin Weil and Dianne Penn.

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

Turns a pile of ideas, requests and goals into a confidence-scored roadmap plus a goals/OKR set the team can actually follow. Use when someone says 'prioritize', 'what should we build next', 'roadmap', 'now next later', 'ICE or RICE', 'write our OKRs', 'quarterly planning', 'too many priorities' or 'sales keeps changing the plan'. Draws on 133 Lenny's Podcast guests including Itamar Gilad, Christina Wodtke and Janna Bastow.

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

Diagnoses product-market fit from survey, usage and pipeline data and returns a scored verdict with the next moves. Use when you ask 'do we have product-market fit', 'is our PMF survey good enough', 'what does 35% very disappointed mean', 'should we scale yet', 'why is growth stalling', or need a Sean Ellis survey, retention check, or PMF level read. Draws on 137 insights from 66 Lenny's Podcast guests incl. Sean Ellis, Todd Jackson and Rahul Vohra.

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

Turns a career question into a decision brief the PM can act on this week - a career plan, a promotion case, a stay-or-leave verdict, a job-search system, or an offer-negotiation script. Use when someone says 'how do I get promoted', 'should I leave my job', 'job search', 'I got laid off', 'negotiate my offer', 'career plan', 'IC or manager', 'next role', 'am I stuck', 'how do I stay relevant with AI' or 'how do I break into PM'. Draws on 188 Lenny's Podcast guests including Phyl Terry, Nikhyl Singhal and Deb Liu.

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

Designs customer interviews and turns the transcripts into decisions. Produces an interview guide plus a synthesis (forces of progress, jobs, pathways, opportunities) you can paste into a doc. Use for 'customer interviews', 'discovery calls', 'JTBD', 'switch interview', 'who should I talk to', 'how many interviews', 'synthesize these transcripts', or 'why do customers churn/buy'. Draws on 140 Lenny's Podcast guests incl. Teresa Torres, Bob Moesta and Judd Antin.

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

Apply timeless marketing and business principles to any problem. Use when someone needs strategic thinking, wants to evaluate a marketing decision, needs a framework for a tough choice, or mentions "first principles," "should I do X," "what would work here," or wants to think through a marketing problem systematically.

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

Generate content ideas rooted in positioning. Use when someone needs "content ideas," "what should I post," "blog topics," "LinkedIn ideas," or is stuck on what to create.

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

Jira Cloud integration for issue management and search. This skill should be used when working with Jira tickets, searching issues with JQL, creating or updating issues, adding comments, or transitioning issue status. Covers REST API v3 and Jira Query Language.

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

n8n workflow automation patterns and API integration. This skill should be used when creating n8n workflows, using webhooks, managing workflows via REST API, or integrating n8n with MCP servers. Covers workflow JSON structure, node patterns, and automation best practices.

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

This skill should be used when demonstrating skill structure and format. Provides example patterns for creating new skills.

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

This skill should be used when the user requests Mac automation via AppleScript, including: Mail operations, Reminders/Calendar management, Safari control, Finder operations, system controls (volume, brightness, notifications, app launching), third-party apps (development tools, task management, media players), or mentions "AppleScript" or "automate Mac".

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

This skill should be used when someone wants to articulate, explore, or document their personal worldview, values, or philosophy. Triggers on "articulate my values", "figure out what I believe", "document my philosophy", "write a manifesto", "define my leadership philosophy", "explore my beliefs". Surfaces beliefs through systematic interrogation, identifies tensions, and generates narrative outputs.

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

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 Claude's capabilities with specialized knowledge, workflows, or tool integrations.

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

This skill should be used when verifying documentation claims against codebase reality. Triggers on "audit docs", "verify documentation", "check docs", "docs accurate", "documentation drift", "before release", "after refactor", "docs don't match". Uses two-pass extraction with pattern expansion for comprehensive detection.

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

This skill should be used as the entry gate for build/create/implement requests. Triggers on "build X", "create Y", "implement Z", "add feature", "try both approaches", "not sure which approach". Offers brainstorm-together or omakase (chef's choice parallel exploration) options. Detects indecision during brainstorming to offer parallel exploration.

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

This skill should be used when moving from design to implementation. Triggers on "let's build", "implement this", "looks good let's code", "ready to implement". Presents options for parallel agent competition (cookoff), single subagent, or local implementation. Each agent creates own plan from shared design for genuine variation.

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

This skill should be used when working with Firebase projects, including initializing projects, adding Cloud Functions or Firestore collections, debugging emulator issues, or reviewing Firebase code. Triggers on "firebase", "firestore", "cloud functions", "emulator", "firebase auth", "deploy to firebase", "firestore rules".

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

This skill should be used when adding features to existing Firebase projects. Triggers on "add function", "create endpoint", "new tool", "add api", "new collection", "implement", "build feature". Guides TDD workflow with test-first development, security rules, and emulator verification.

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