메뉴
Set up or update the Growth Engine memory folder and builder profile. Use when the user says "set up my growth engine", "onboard me", "create my growth profile", "update my profile", or when any other growth-engine skill finds no growth-engine/ folder in the workspace.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build or refine a truthful, memorable personal brand positioning system — positioning statements, bios, content pillars, proof-asset plan, anti-positioning. Use when the user says "work on my positioning", "personal brand", "rewrite my bios", "what should I be known for", or "is my positioning still right".
Improve the Growth Engine itself — review which advice worked and which didn't, interview the user about friction, and update the playbook that every other skill obeys. Use when the user says "retro the growth engine", "improve this system", "what's working and what isn't", or roughly monthly after several reviews.
Run an accountability review of the user's growth system — score follow-through on past commitments, kill stale bets, check the proof-asset pipeline and learning roadmap, flag drift from goals. Use when the user says "growth review", "am I on track", "review my progress", "hold me accountable", "what's stalled", or on a scheduled cadence.
Deep-research a niche and turn it into a living markdown knowledge base (market map, personas, pain points, tools, datasets, project ideas, content angles). Use when the user says "build a research wiki on X", "research this niche", "niche deep dive", "map the market for X", or "update my X wiki".
Discover, verify, rank, and package emerging opportunities for software, AI workflows, tools, directories, automations, or small online businesses. Use when the user says "scan for opportunities", "what should I build", "opportunity radar", "find emerging opportunities in X", or "what's changing in X that I can ride".
| name | growth-setup |
| description | Set up or update the Growth Engine memory folder and builder profile. Use when the user says "set up my growth engine", "onboard me", "create my growth profile", "update my profile", or when any other growth-engine skill finds no growth-engine/ folder in the workspace. |
Create (or refresh) the persistent state that powers every Growth Engine skill: a growth-engine/ folder in the user's workspace containing their builder profile and memory files.
Look for growth-engine/ at the workspace root. If it exists, read profile.md and switch to update mode: confirm what's stale, interview only for gaps, and preserve history.
Run the interview in references/interview-guide.md. It must establish three things above all: who the user is, what they want their branding to be, and what they want to stand out as — plus goals, constraints, tone, and anti-positioning. This works for any user: developer, writer, artist, freelancer, shop owner.
Don't make the user type what can be discovered, and verify what they claimed:
Create the files exactly as specified in references/state-schema.md. Present the drafted profile.md to the user for correction before finalizing. Never invent achievements — anything unverified stays marked inferred.
Tell the user which skills to run next (typically opportunity-radar or brand-positioning) and offer to schedule a recurring growth-review.
growth-engine/playbook.md first if it exists and obey its directives.