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 wants to write an email to an investor — cold outreach, warm intro request, follow-up after a meeting, monthly investor update, or thank-you note. Also activates for "intro email", "investor email", "follow up with VC", or "investor update".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
From startup-context: company one-liner, stage, key traction metrics, fundraising status, and any notable social proof (investors, customers, press).
From the user: email type, recipient (investor name and firm), prior relationship context, and desired outcome (meeting, intro, materials review).
.agents/startup-context.md.**To:** [Investor Name]
**Subject:** [Subject line]
[Email body]
For investor updates, output a longer structured email with sections (see type 4 below).
Goal: Get a 30-minute meeting. Length: 5-7 sentences, under 150 words.
[Specific hook] — [Company Name] (e.g., "$40K MRR in 6 months, AI contract review — Lexara").Goal: Make it effortless for your connector to intro you. Two parts:
Goal: Maintain momentum, deliver materials, set next steps. Length: 4-8 sentences.
Goal: Keep current and prospective investors informed. Length: 300-500 words.
Goal: Maintain the relationship. Length: 3-5 sentences.
pitch-deck — the email drives the meeting; the deck carries the meetinginvestor-research — research determines who to email and what personalization to useExample prompt: "Write a cold email to Sarah Chen at Greylock. We're an AI code review startup with $55K MRR."
Good output:
Subject: $55K MRR — AI code review, 4 enterprise customers — CodeLens
Hi Sarah,
Your investment in Developer Infrastructure at Greylock — particularly the thesis in your "Next Wave of DevTools" post — is why I wanted to reach out to you specifically.
I'm the CEO of CodeLens. We automate code review for enterprise engineering teams using LLMs, catching security vulnerabilities and logic errors that slip past existing tools.
We launched 5 months ago: $55K MRR, 4 enterprise customers (two Fortune 500), growing 30% MoM. We're raising a $3M seed round.
Would you have 30 minutes this week or next?
Example prompt: "Help me write this month's investor update."
Good output approach: Pull metrics from startup context, ask the founder for this month's highlights and challenges, then produce the structured update. Flag any missing or stale KPIs.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。