When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC application", "Techstars", "accelerator", or "apply to programs".
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to plan, prioritize, or structure a content program -- including identifying content pillars, mapping content to the buyer journey, choosing content types, or building an editorial calendar.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
site:competitor.com/blog), and input from sales/support teams.seo-technical -- when content pillars need keyword research and on-page optimization to ranksocial-content -- when content needs to be adapted and distributed across social platformsemail-marketing -- when content is distributed through newsletters or used in nurture sequencesExample 1: New content program
"We're a seed-stage B2B SaaS for engineering teams. No content yet. Where do we start?"
Good output: Identifies 3-4 content pillars using the four identification methods. Recommends starting with 2 comparison pages (capture existing demand), 3 use-case articles (bottom-funnel), and 1 thought leadership piece per month. Includes a scored backlog of 15 content ideas with priorities and a 90-day calendar. Distribution plan emphasizes LinkedIn, Hacker News, and relevant communities.
Example 2: Content audit
"We have 40 blog posts but they barely get traffic. What should we do?"
Good output: Asks for top-performing vs. underperforming posts, identifies content gaps using the buyer journey map, recommends which posts to update/consolidate/kill, proposes hub-and-spoke restructuring around 3 pillar topics, and provides a 60-day optimization calendar alternating between updating old content and publishing new gap-filling pieces.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC application", "Techstars", "accelerator", or "apply to programs".
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis. Also activate for "design the system", "how should I architect this", "monolith vs microservices", or architecture decision records.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores, design save plays, or create win-back campaigns.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".
日本語の概要は準備中です。原文の説明を表示しています。
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this". Also activate when reviewing a pull request or diff.
日本語の概要は準備中です。原文の説明を表示しています。