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 build a LinkedIn authority system, create social content strategy, define content pillars, write posts, or establish thought leadership positioning. Activate on "LinkedIn strategy," "content pillars," "what should I post," or "build my personal brand."
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
From startup-context or the user:
A critical gate: positioning clarity must come first. An unfocused content system produces unfocused results. If the user cannot articulate who they serve and why they are different, address that before building pillars.
"Being remembered by the right 500 people when they need what you do — that pays your bills." This is not about going viral. It is about consistent, positioned content that makes you the obvious choice when your audience has a need.
Reject any pillar that fails even one of these tests:
The first 1-2 lines determine whether anyone reads the rest:
After 30 days, analyze which pillars generated: comments, DMs, profile views, and impressions. Adjust content ratios based on what actually resonated, not what you assumed would work.
One viral post means nothing without a consistent presence. Show up regularly with positioned content and compounding does the rest. Post 3-5 times per week on LinkedIn.
content-strategy — when social content is part of a broader content ecosystememail-marketing — when social content drives newsletter signups or email content is repurposed for sociallaunch-strategy — when social content is part of a coordinated product launchExample 1: Founder needs a LinkedIn system
"I'm the CEO of a dev tools startup. I post occasionally but have no strategy."
Good output: Confirms positioning ("I help engineering teams ship faster by catching API failures before customers do"). Defines 3 pillars: engineering leadership lessons (70%), building-in-public product updates (20%), founder journey (10%). Provides a 4-week calendar with real dates, each entry having a pillar, format, and hook. Writes 5 complete posts for week 1. Includes a daily 20-minute engagement routine targeting CTO and VP Engineering posts.
Example 2: Founder stuck on what to post
"I know I should post on LinkedIn but I stare at a blank page every time."
Good output (Quick mode): Identifies 3 pillars from a brief conversation. Provides 5 starter hooks with the first lines already written. Gives a 1-week plan with one post per day, each mapped to a pillar and format. Focus is on eliminating the blank-page problem and building the habit.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.