메뉴
Used when the founder needs to triage user feedback, bugs, complaints, or emails without losing focus. Trigger phrases: 'user feedback', 'customer said', 'triage this bug', 'reply to this user'
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
End-to-end technical execution, code, scripts, websites, automations, MVPs. Use for any request to build, fix, code, deploy, or automate anything.
Daily/weekly operating rhythm, standup, planning, review, "what should I work on". Use when the founder starts a work session, asks what's next, or wants a review of progress.
Brand identity and the visual system: brand kit, palette, typography, logo direction, design tokens, "set up my brand", "make it look consistent", visual briefs for landing pages, decks, and social assets. Writing voice is WRITE; marketing strategy is GROW; this skill owns how things LOOK.
Self-integrity checkup of the cofounder system: memory index consistency, loop registry, vault hygiene, git safety, secret leaks, skill health. Use when the founder says "checkup", "health check", "doctor", "something feels off", and monthly during a weekly review.
Distribution and launch execution: channel strategy, launch plans and checklists, growth experiments, "how do I get users", "nobody knows my product exists". Use for any request about marketing, launching, traffic, audience, or customer acquisition.
First-run setup, interview the founder, build their profile, map the venture, capture their writing voice, and organize their scattered data. Run automatically when memory/founder-profile.md does not exist, or when the founder says "onboard", "set up", or "start over".
| name | support |
| description | Used when the founder needs to triage user feedback, bugs, complaints, or emails without losing focus. Trigger phrases: 'user feedback', 'customer said', 'triage this bug', 'reply to this user' |
Solo founders lose days to context-switching into customer support. This skill handles the noise, distills the signal, and drafts the reply so the founder can get back to work.
When the founder pastes a user email, tweet, or bug report: Read the feedback and categorize it into exactly ONE of the following buckets:
memory/open-loops.md with a strict owner and due date.vault/feedback/feature-requests.md (create if missing) and check if other users have requested it. Do NOT immediately build it unless the founder explicitly overrides.Using the memory/voice.md file (to ensure it sounds like the founder, not a generic AI):