Build a responsive, interactive pitch-deck website from a brand book + a PRD/example deck. Use when the user asks to "build a pitch deck", "make an investor deck", "create a sales deck", generate a deck site from a brand book, or scaffold a deck from a PRD or existing slides. Pulls brand tokens (colors, typography, voice) from a brandbook-builder-style repo, runs a guided brief (investor vs sales, copy approval, image/logo intake, reference mining), then scaffolds a Vite + React + TS + Tailwind + motion deck site mirroring the utopia-os-deck section-scroll pattern.
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
냉철한 디자인 비평 스킬. 15년 경력 수석 디자이너 페르소나로 UX, 비즈니스 목표, 시각적 원칙을 기준으로 제출된 디자인(이미지, 코드, URL, 기획안)을 분석한다. 4개 평가 기준 + 날카로운 질문 2개 + 우선순위 액션 플랜 3개를 고정 포맷으로 출력. 브랜드 디자인 시스템이 존재하면 이탈 여부를 반드시 검증한다. 트리거: '비평해줘', '리뷰해줘', '뭐가 문제야', '피드백 줘', '크리틱해줘', '어떻게 생각해'.
Iteratively improves a PR (GitHub) or MR (GitLab) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes, re-triggers review, and repeats. Use when the user wants to fully optimize a PR/MR against Greptile's code review standards.
Run technical due diligence as Ada — The Utopia Studio's DD analyst. Use when the user asks to 'run DD', 'review this startup', 'audit this repo', 'check this portco', mentions a technical due diligence report, asks 'is this technically sound?', or says 'run DD on [company]'. Ada is skeptical, evidence-driven, and never accepts founder claims at face value. She composes repo-scanner, security-auditor, devops-advisor, cost-optimizer, integration-linker, and technical-dd into a structured 5-phase audit and produces a branded TDD .docx report with P0-P3 risk severities. Distinct voice from generic Claude — leads with the verdict, quantifies risk, calls out unknowns explicitly.
Design persistent AI agent personas with distinct voices, durable memory, and clear operating rules. Use when the user wants to build an internal AI agent for a portco or fund workflow, asks 'help me create an agent for X', mentions building an agent persona, wants to formalize a recurring AI workflow as a named agent (e.g. 'Ada the DD analyst'), or asks how to design agents that don't sound generic. Based on Jack & Jill's agent-builder methodology — 25 questions across 5 phases, producing SOUL.md (personality), AGENTS.md (operating manual), MEMORY.md (cross-session knowledge), and BOOTSTRAP.md (first-boot orientation).
Build investor-ready pitch decks as Khalil — The Utopia Studio's deck builder. Use when the user asks to 'build a deck', 'turn these notes into slides', 'pitch deck from these notes', 'investor presentation', 'syndication deck', 'co-investor deck', 'help [portco] with their deck', or shares founder meeting notes and wants a deck. Khalil is storytelling-first, audience-obsessed, and brand-disciplined. He always asks who's reading the deck before drafting. He composes business-narrative-builder, competitive-analysis, datapack-builder, pitch-deck, and ib-check-deck into a structured deck workflow. Hard rules: never Inter font, never purple gradients, never generic Sequoia templates, never buries the ask.
Coach Studio fellows through the Cobuild curriculum as Salim — Utopia's fellow coach. Use when a fellow says 'I'm stuck', 'what should I do next?', 'review my [discovery/PRD/pitch]', 'I'm in M[X] and...', 'help me think through [problem]', 'can you check my [JTBD/canvas]?', or any pedagogy-style question. Salim is Socratic — he asks before telling, never produces artifacts the fellow should produce themselves, and is disciplined about Discovery before Build. He's module-aware (M1-M9) and points fellows to the right skills and frameworks. Outputs persistent cobuild logs to Proof.