「should」の検索結果

Applies the Bullseye Framework from Traction by Gabriel Weinberg and Justin Mares. Use when choosing growth channels, testing customer acquisition strategies, or deciding where to spend marketing effort. Covers all 19 traction channels with selection methodology, testing protocol, and phase-matched channel advice. Triggers include 'how do we get customers', 'which marketing channel should we use', 'we have a product but no users', 'our growth has stalled', 'should we do content marketing or paid ads', 'how do we test traction channels', 'what channels work at our stage'. NOT for product development (use Lean Startup), not for positioning/messaging (use Obviously Awesome), not for pricing (use Monetizing Innovation), not for enterprise sales methodology (use SPIN Selling).

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

Define a brand's verbal identity — tone, voice, writing style, vocabulary, and messaging rules. Use when the user says "brand voice", "tone of voice", "how should we write", "writing guidelines", "copy style guide", "brand language", "verbal identity", "how should the brand sound", "tone guide", "our copy doesn't sound right", "copywriter guidelines", "voice and tone", or when onboarding a copywriter or content team. Also use when the user has a brand strategy and wants to define how the brand communicates.

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

139 proven marketing ideas organized by category with implementation guidance. Use when asked for marketing ideas, growth strategies, campaign brainstorms, or "what should I do to grow." Trigger phrases: "marketing ideas", "growth ideas", "how to grow", "marketing strategies", "campaign ideas", "promote my product", "marketing brainstorm", "growth tactics", "what should I try", "marketing playbook".

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

This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".

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

Use when an editor or videographer needs production direction — beat-by-beat storyboard, footage to shoot, b-roll, text overlays, music and pacing, transitions, CTA end frame, and per-channel export specs. This is the EDIT instruction, not the spoken script. Trigger on 'video brief', 'editor brief', 'storyboard', 'brief for the video editor', 'how should this video be cut', 'we have the footage and no direction'. Also use when raw clips exist and nobody knows what the final should look like. Not for — the words said on camera, see `04-script-video-global`; briefing a creator to film their own, see `06-ugc-egc-brief-global`; resizing a finished video, see `50-asset-resize-global`.

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

Use when a price has to be set or changed — value-based pricing, anchoring, charm pricing, decoy tiers, good-better-best packaging, discount policy, and margin math, with currency psychology for US, EU, SEA, and LATAM plus dropshipping markup and BE-ROAS. Trigger on 'pricing strategy', 'how much should I charge', 'should I raise prices', 'price tiers', 'customers say it is too expensive', 'dropshipping markup'. Also use when the product is not selling and the user suspects price is the reason. Not for — bonuses, guarantee, and value stack around the price, see `31-offer-design-global`; persuasion beyond price, see `16-marketing-psychology-global`; ad budget math, see `10-reverse-kpi-global`.

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

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

This skill should be used when the user asks to "audit claude permissions", "audit permissions", "review local claude settings", "promote permissions to global", "clean up claude settings", "find permission patterns", or wants to identify project-local Claude Code permissions that should be added to global configuration.

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

Use when Java design, refactoring, or implementation tradeoffs should be evaluated with Kent Beck's simple design rules, including passes the tests, reveals intention, has no duplication, and has the fewest elements. This should trigger for requests such as Apply simple design rules; Review this design with Beck's rules; Choose between these refactoring options; Keep this Java design simple. Part of Plinth Toolkit

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

Use when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then making the intended behavior change once the design supports it. This should trigger for requests such as Apply two-step change; Make this risky change safer; Refactor before changing behavior; Separate preparation from behavior change. Part of Plinth Toolkit

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

Use when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests green. This should trigger for requests such as Apply TDD; Use test-driven development; Drive this Java change with tests; Write the failing test first; Red-green-refactor this feature. Part of Plinth Toolkit

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

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 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.

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

Designs, sanity-checks and reads out product experiments (A/B tests, holdouts, pre/post, geo and incrementality tests) and produces an experiment brief plus a readout with a ship / hold / replicate call. Use when you ask 'should we A/B test this', 'how long should the test run', 'is this result real', 'sample size', 'stat sig', 'SRM', 'holdout', 'our win rate is low', or need to grade an existing test plan or readout. Draws on 191 insights from 71 Lenny's Podcast guests, led by Ronny Kohavi, Ramesh Johari and Archie Abrams.

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

Turns a hard product or career decision into a one-page decision memo with the eigenquestion, options, pre-mortem with kill criteria, reversibility rating, a named decider and a review date. Use when you ask 'how should we decide', 'should we build or kill this', 'one-way door or two-way door', 'run a pre-mortem', 'we keep going in circles', 'quit or pivot', or want to grade a decision doc. Draws on 396 insights from 177 Lenny's Podcast guests, led by Annie Duke, Shreyas Doshi and Shishir Mehrotra.

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

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.

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

Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".

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

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Inspect a Core UI or code surface for a small number of justified motion opportunities and explicitly identify what should remain static. Use when asked what should animate, where motion would improve feedback or comprehension, how to make an interface feel more alive without over-animating it, or whether a proposed animation is worth adding. Read-only; do not use to review or fix existing motion code or to implement animations.

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

This skill should be used when the user needs to calculate consumption tax (消費税) or determine their tax method (2割特例, 簡易課税, or 本則課税). Trigger phrases include: "消費税を計算", "消費税の申告", "消費税申告書", "2割特例", "簡易課税", "本則課税", "課税売上", "消費税額", "インボイス", "みなし仕入率", "課税仕入".

This skill should be used when the user needs to perform year-end closing adjustments (決算整理), review financial statements (決算書), compute depreciation, or review their trial balance. Trigger phrases include: "決算", "決算整理", "決算書を作る", "減価償却", "試算表", "残高試算表", "損益計算書", "貸借対照表", "BS", "PL", "期末処理", "棚卸し", "未払計上", "前払処理".

This skill should be used when the user asks to determine what tax filings they need, wants to know if they must file a tax return (確定申告), asks about consumption tax obligations (消費税), or needs help understanding their filing requirements. Trigger phrases include: "確定申告が必要か", "申告の種類", "消費税の届出", "課税事業者かどうか", "何を申告すればいい", "申告要否", "税金の申告", "住民税の申告".

This skill should be used when the user needs to know what documents to collect for their tax filing, wants a checklist of required documents, or asks where to obtain specific tax documents. Trigger phrases include: "必要書類", "書類を集める", "何を準備すればいい", "源泉徴収票はどこで", "書類チェックリスト", "確定申告に必要なもの", "書類収集", "準備するもの".