2,877 件 ・ 関連度順
概要と使いどころ
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
日本語の概要は準備中です。原文の説明を表示しています。
Write a detailed component specification including props, states, variants, accessibility requirements, and usage guidelines.
日本語の概要は準備中です。原文の説明を表示しています。
Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.
日本語の概要は準備中です。原文の説明を表示しています。
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.
日本語の概要は準備中です。原文の説明を表示しています。
Translate skills from one industry to another, identify transferable skills
日本語の概要は準備中です。原文の説明を表示しています。
Design click/first-click tests to evaluate navigation and information findability.
日本語の概要は準備中です。原文の説明を表示しています。
Craft portfolio-ready case studies that tell the story of a design project.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.
日本語の概要は準備中です。原文の説明を表示しています。
Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for GEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience. Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about", "blog topics", "content pillars", "blog ideation".
日本語の概要は準備中です。原文の説明を表示しています。
Write a comprehensive design brief that defines the problem space, constraints, audience, and success criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Full-lifecycle blog engine with 30 sub-skills, 12 content templates, 5-category 100-point scoring, and 5 specialized agents. Routes user requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI-citation optimization, FLOW framework prompts, topic-cluster execution, and multilingual publishing. Optimized for Google rankings (December 2025 Core Update, E-E-A-T) and AI citations (GEO/AEO). Supports any platform (WordPress, Next.js MDX, Hugo, Ghost, Astro, Jekyll, 11ty, Gatsby, HTML). Use when user says "blog", "write a blog", "blog post", "blog strategy", "content brief", "editorial calendar", "blog audit", "blog optimization", "topic cluster", "multilingual blog", "FLOW framework", or any /blog subcommand. Sub-skill descriptions cover narrower triggers.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a fully structured, project-specific CLAUDE.md by scanning the repo for signal files (package.json, Makefile, .github/workflows/, .env.example, etc.), inferring stack, commands, architecture, and conventions, then asking at most 3 targeted questions for what cannot be inferred. Use whenever the user says 'create a CLAUDE.md', 'my CLAUDE.md is blank', 'generate project context', 'initialize CLAUDE.md', 'set up Claude context for this repo', 'fill in my CLAUDE.md', or any variation where someone needs their project context documented for Claude. If a CLAUDE.md already exists with content, runs a diff-and-merge flow before writing.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Write new blog articles from scratch optimized for Google rankings and AI citations. Generates full articles with template selection, answer-first formatting, Key Takeaways summary box, information gain markers, citation capsules, sourced statistics, Pixabay/Unsplash images, built-in SVG chart generation, FAQ schema, internal linking zones, and proper heading hierarchy. Supports MDX, markdown, and HTML output. Use when user says "write blog", "new blog post", "create article", "write about", "draft blog", "generate blog post".
日本語の概要は準備中です。原文の説明を表示しています。
Create QA checklists for verifying design implementation accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
Build a comprehensive color system with palette generation, semantic mapping, and accessibility compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Define what content a product needs, how it should be structured, and who owns it.
日本語の概要は準備中です。原文の説明を表示しています。
Critique a screen's typography — scale usage, readability, consistency, and token compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.
日本語の概要は準備中です。原文の説明を表示しています。
Critique a screen's information density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure.
日本語の概要は準備中です。原文の説明を表示しています。
Critique a screen's composition — balance, whitespace, rhythm, and gestalt principles.
日本語の概要は準備中です。原文の説明を表示しています。
Write clear design rationale connecting decisions to user needs, business goals, and principles.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct a structured competitive analysis comparing UX patterns, features, strengths, and gaps across rival products.
日本語の概要は準備中です。原文の説明を表示しています。