「claude-skills」の検索結果

Navigate a new leadership role using Michael Watkins' First 90 Days 30/60/90 framework. Use when someone says "I just started a new role", "I'm starting as a new manager", "I joined a new company as a leader", "I was just promoted", "how do I onboard as a leader", "what should I do in my first 30 days", "I inherited a team", "I need a 90 day plan", or "I'm new to this team". Also trigger when someone describes feeling overwhelmed in a new leadership role, unsure where to start, or tempted to make changes too quickly before they've listened. Applies to first-time managers, leaders joining new companies, and leaders moving into new functions or teams within the same company.

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

Review marketing KPIs and produce an executive summary with insights, anomalies, and recommended actions using the Storytelling with Data framework (Cole Nussbaumer Knaflic). Every review starts with a Big Idea - one sentence capturing the insight, its implication, and why it matters. Use when the user asks for a KPI review, monthly metrics review, marketing dashboard review, "review last month's numbers", quarterly review, performance review, or wants to analyze marketing data. Reads kpis.md and any uploaded data files. For planning a campaign against these numbers, see campaign-brief. For the post-campaign learning loop, see retro. For setting the baseline itself, see brand-context.

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

Deliver feedback using Kim Scott's Radical Candor framework - care personally while challenging directly. Use when a leader needs to give difficult feedback, says "I need to tell someone something hard", "how do I give feedback without hurting them", "I've been avoiding a conversation", "my direct report isn't performing", "someone on my team has a blind spot", "I keep sugarcoating things", or "how do I be honest without being a jerk". Also trigger when someone describes being too nice (ruinous empathy) or too harsh (obnoxious aggression), or when they describe avoiding a conversation they know they need to have.

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

Use when the user says "write my pitch", "help me tell my startup story", "craft my investor narrative", "why now slide", "what's our secret", "how do I explain what we do", "make my pitch compelling", "pitch deck story", "elevator pitch", "why will we win", "contrarian insight", or wants to build a persuasive, coherent narrative around their startup for investors, press, or recruiting.

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

Write a high-performing LinkedIn post in the user's brand voice using Hook-Story-Offer (Russell Brunson) and the Curiosity Gap hook method (George Loewenstein). Every post starts by selecting a named hook formula - specific number + surprising result, contrarian statement, personal confession, direct challenge, or before/after. Use when the user asks for a LinkedIn post, LinkedIn update, LinkedIn content, "post for LinkedIn", thought-leadership post, founder post, or short professional social content. Reads brand voice and ICP from knowledge/ so output sounds like the company, not generic AI. For long-form opinion pieces, see thought-leadership-writer. For the monthly posting plan, see social-calendar. For turning one asset into many posts, see content-repurposer.

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

Diagnose why a landing page, homepage, pricing page, or signup form is not converting, and produce a ranked fix list with a test plan. Runs a structured audit across motivation, value clarity, friction, anxiety, and CTA hierarchy rather than giving generic design opinions. Use when the user says "why isn't this page converting", "improve our conversion rate", "CRO", "conversion audit", "this page isn't working", "high traffic low signups", "people bounce", "review our landing page", or shares a URL and asks what is wrong with it. For rewriting the words only, see copy-review. For writing a new page from scratch, see landing-page-writer. For the statistics of running the test afterwards, see growth-experiment.

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

Write a product positioning document. Use when the user says "write a positioning doc", "positioning statement", "how should we position this product", "positioning for [product]", "we need to differentiate from competitors", "product positioning and messaging", "positioning workshop", "help me define our position in the market", or wants to establish how a product should be perceived relative to competitors. For customer-facing message wording, see messaging-framework. For the competitive research behind it, see competitor-analyst. For storing it in the knowledge base, see brand-context.

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

Write recurring newsletter issues with a consistent format and POV using the Curiosity Gap (George Loewenstein) and David Perell's Online Writing framework. Different from one-off emails (use /content-writer or /email-nurture). Use when the user asks for a newsletter, weekly/monthly newsletter, "write this week's issue", recurring email, Substack issue, internal newsletter, or any periodic publication with subscribers. Reads brand voice and content library from knowledge/. For a nurture or lifecycle sequence, see email-nurture. For long-form thought leadership, see thought-leadership-writer. For the monthly plan, see social-calendar.

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

Use when the user says "write my investor update", "monthly update for investors", "quarterly investor email", "investor communication", "LP update", "board update", "shareholder update", "what do I tell my investors this month", "how do I write a good investor update", or wants to communicate progress, metrics, and needs to existing investors or board members on a recurring basis.

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

Use when the user says "write a cold email to investors", "investor outreach email", "how do I cold email a VC", "fundraising cold outreach", "email to angel investor", "reach out to investors", "get a meeting with investors", "intro email for fundraising", "follow up with investor", "warm intro email", or wants to draft any outbound investor communication to generate a first meeting or advance a fundraising conversation.

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

Use when the user says "run customer discovery", "help me interview customers", "write customer interview questions", "validate my assumption", "talk to users", "synthesize customer interviews", "what are my customers saying", "user research for my startup", "mom test interview", "are we solving a real problem", or wants to extract real insight from conversations with potential or existing customers.

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

Build branded PowerPoint decks (.pptx) for pitches, internal updates, sales decks, customer QBRs, board updates, conference talks using the Pyramid Principle and SCQA framework (Barbara Minto, The Minto Pyramid Principle). Every deck starts with the answer - conclusion on slide 2, evidence after. Slide titles are conclusions, not topics. Use when the user asks for a deck, presentation, slides, pitch deck, sales deck, board deck, QBR, "make slides for X", or "build a presentation". Uses templates/ for brand assets. Generates structured slide content with speaker notes. For the narrative content of the deck, see thought-leadership-writer or campaign-brief. For a case study slide, see case-study-writer.

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

Use when the user says "map out our business model", "business model canvas", "how does our business work", "what are our key resources", "define our value proposition", "revenue model design", "cost structure", "who are our key partners", "lean canvas", "business model design", "how do we make money", or wants to document, stress-test, or redesign how [your startup] creates, delivers, and captures value.

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

Write unit and integration tests. Use when the user says "write tests for this", "add test coverage", "how do I test this", "TDD", "red green refactor", "unit test this function", "test this module", "I need tests for", or has code that lacks tests - even if they don't explicitly say "write tests".

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

Document and prioritize technical debt. Use when the user says "tech debt", "legacy code", "this code is a mess", "refactoring plan", "we need to clean this up", "paying down debt", "this is hard to change", "how do we fix this codebase", or has code that's difficult to understand or modify - even if they don't explicitly say "technical debt".

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

Write a clear pull request description. Use when the user says "write a PR description", "PR template", "pull request description", "how do I describe this change", "commit message for this", "document this change", "open a PR for", or is about to merge code and needs to communicate what changed and why - even if they don't explicitly say "PR description".

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

Debug a bug or unexpected behavior systematically. Use when the user says "there's a bug", "this isn't working", "I'm getting an error", "help me debug", "why is this failing", "unexpected behavior", "test is failing", "something is broken", or describes behavior that doesn't match expectations - even if they don't say "debug".

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

Review code for quality, bugs, and design issues. Use when the user says "review this code", "do a code review", "check this PR", "review this diff", "is this code good", "what's wrong with this code", "code quality check", or pastes code and wants feedback - even if they don't explicitly say "code review".

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

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

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

Write an operational runbook. Use when the user says "write a runbook", "on-call documentation", "how to operate this service", "alert runbook", "troubleshooting guide for ops", "what to do when this alert fires", "operational procedures", or needs to document how to run, troubleshoot, or respond to a service - even if they don't explicitly say "runbook".

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

Write a blameless postmortem after an incident. Use when the user says "postmortem", "post-incident review", "PIR", "what happened in that incident", "incident review", "blameless postmortem", "5 whys", "how do we prevent this again", or needs to document learnings from a production incident - even if they don't explicitly say "postmortem".

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

Run a structured incident response. Use when the user says "we have an incident", "production is down", "service is degraded", "on-call response", "p0 incident", "something is broken in prod", "help me manage this incident", "incident commander", or there is an active production issue requiring coordinated response - even if they don't explicitly say "incident response".

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

Run a pre and post-deployment checklist. Use when the user says "deploy to production", "deployment checklist", "release checklist", "pre-deploy checks", "is this ready to deploy", "deployment readiness", "reduce deployment risk", "change management", or is about to ship code to production and wants to reduce failure risk - even if they don't explicitly say "deployment checklist".

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

Write marketing content in the user's brand voice using PAS (Problem-Agitate-Solution) and AIDA (Attention-Interest-Desire-Action) copywriting frameworks. Use when the user asks to write a LinkedIn post, blog article, email, ad copy, landing page section, social post, newsletter, or any short-to-medium form marketing content. Reads brand voice and ICP from knowledge/ so the output sounds like the company, not like generic AI. For improving copy that already exists, see copy-review. For a landing page specifically, see landing-page-writer. For a LinkedIn post, see linkedin-post. For long-form POV, see thought-leadership-writer.

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