526 件 ・ 関連度順
概要と使いどころ
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
日本語の概要は準備中です。原文の説明を表示しています。
Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps. Invoke when user mentions abstraction levels, making concepts concrete, or explaining at different depths.
日本語の概要は準備中です。原文の説明を表示しています。
Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
日本語の概要は準備中です。原文の説明を表示しています。
Songwriting craft, AI music generation prompts (Suno focus), parody/adaptation techniques, phonetic tricks, and lessons learned. These are tools and ideas, not rules. Break any of them when the art calls for it.
日本語の概要は準備中です。原文の説明を表示しています。
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
日本語の概要は準備中です。原文の説明を表示しています。
Write strategy-oriented Product Requirements Documents (PRDs) for AI product managers. Use when: (1) drafting a new PRD or strategy doc, (2) structuring a feature proposal with strategy rationale, (3) writing requirement docs that emphasize "why" over "how", (4) turning raw product ideas into structured requirement documents. NOT for: purely technical specs, engineering tickets, or UI copy.
日本語の概要は準備中です。原文の説明を表示しています。
Research markets with sizing, segmentation, competitor mapping, pricing checks, and demand validation that turn fuzzy ideas into decision-ready evidence. Use when (1) you need TAM, SAM, SOM, whitespace, or category sizing; (2) you must compare competitors, pricing, positioning, or customer segments before acting; (3) the user asks whether a niche, launch, expansion, or go-to-market bet is actually worth pursuing.
日本語の概要は準備中です。原文の説明を表示しています。
Validate ideas, build strategy, and make decisions with proven frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Maxim 2D cartoon explainer video — engineered for learning retention and friendly brand affinity. Uses Dual Coding Theory + Cognitive Load Reduction + Ekman Universal Emotion to make complex ideas memorable and brands feel trustworthy-approachable.
日本語の概要は準備中です。原文の説明を表示しています。
Ingest raw sources into the structured wiki — "ingest", "add this to my wiki", new files in raw/, clippings, sources, ideas, nightly ingest. Produces pages with YAML frontmatter and a mandatory Counter-Arguments section.
日本語の概要は準備中です。原文の説明を表示しています。
Generate logo directions — "give me logo concepts for", "logo ideas for", "design a logo for". Emits 3 to 5 distinct directions as real editable SVG vector code, not raster mockups.
日本語の概要は準備中です。原文の説明を表示しています。
Visual whiteboard collaboration for Copilot CLI. Creates an interactive whiteboard that opens in your browser — draw, sketch, add sticky notes, then share everything back with Copilot. Copilot sees your drawings and text, and responds with analysis, suggestions, and ideas.
日本語の概要は準備中です。原文の説明を表示しています。
Generate project ideas via creative constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Socratic ideation and idea routing — think through ideas before committing to plans
日本語の概要は準備中です。原文の説明を表示しています。
Refines raw ideas through structured divergent and convergent thinking for ordinary non-command brainstorming, idea shaping, options comparison, and explicit IDEATE deepening routed by `aili-delivery-flow`; do not use as the top-level `/ideate` command owner or for existing-plan stress-test, review, or completion-claim checks.
日本語の概要は準備中です。原文の説明を表示しています。
Transform brain dumps into polished blog posts in Nick Nisi's voice. Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative with Nick's conversational, authentic, and thoughtful tone.
日本語の概要は準備中です。原文の説明を表示しています。
Launch background Claude sessions to explore and analyze business ideas. Say 'Idea: [description]' to trigger.
日本語の概要は準備中です。原文の説明を表示しています。
Search and browse Pinterest pins, get pin details, and send actual images to the user via Telegram/messaging. Use when the user wants to find inspiration, search for images/ideas, or browse Pinterest content. Sends images directly, not just links.
日本語の概要は準備中です。原文の説明を表示しています。
Expert landscape designer transforming yards through photo mapping, 3D visualization, seasonal planning, and deep plant knowledge. Specializes in fast-growing privacy screens (knows arborvitae pitfalls), architecture-appropriate design, outdoor living spaces, and realistic maintenance expectations. Activate on "landscape design", "yard design", "garden planning", "plant selection", "privacy screen", "outdoor living", "backyard makeover", "arborvitae", "hedge", "fast growing tree", "landscaping ideas". NOT for interior design (use interior-design-expert), hardscape construction (consult contractors), or lawn care chemicals (consult local experts).
日本語の概要は準備中です。原文の説明を表示しています。
### 1. The Fault/Error/Failure Hierarchy NOT for unrelated tasks outside this domain.
日本語の概要は準備中です。原文の説明を表示しています。
How to design contextual inputs for an always-on AI agent with episodic memory. Covers what data to feed the agent, how to structure observations and triggers, ambient context capture (screen, audio, calendar), context window budgeting, and retrieval strategies that keep the agent grounded in what's actually happening. Activate on: "what should the agent observe", "context inputs for agent", "ambient context capture", "agent triggers", "agent input design", "screenpipe integration", "context window budget", "what data to feed my agent", "/always-on-agent-inputs". NOT for: memory architecture and storage (use always-on-agent-architecture), application ideas (use always-on-agent-applications), safety concerns (use always-on-agent-safety).
日本語の概要は準備中です。原文の説明を表示しています。