seungwonme
37 verified skills
metamedium
This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "관점 전환", "perspective shift", "다른 방법 없을까", "같은 방식이 안 먹혀", "diminishing returns". Applies Alan Kay's metamedium concept to surface form-level alternatives. For requirement clarification use vague; for strategy blind spots use unknown.
development
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
development
tdd
Test-Driven Development following Kent Beck's TDD and Tidy First principles. Use when implementing features with test-first approach, following Red-Green-Refactor cycle, or separating structural changes from behavioral changes in commits.
development
google-calendar
Google 캘린더 일정 조회/생성/수정/삭제. "오늘 일정", "이번 주 일정", "미팅 추가해줘" 요청에 사용. 여러 계정(work, personal) 통합 조회 지원.
development
notion
Notion workspace automation — search, create, update, and organize pages. Routes to the appropriate sub-skill. Trigger on "notion", "노션", "회의 준비", "meeting prep", "지식 정리", "문서화", "리서치", "스펙 구현", "spec to tasks". Sub-skills — meeting-intelligence (meeting prep with pre-read + agenda, "회의 준비", "미팅 자료"), knowledge-capture (conversation to structured docs, "노션에 저장", "문서화해줘", "위키에 추가"), research-documentation (search + synthesize + report, "노션 검색", "조사해줘", "리서치 정리"), spec-to-implementation (spec breakdown into tasks, "스펙 구현", "태스크 분해", "구현 계획").
tools
research-documentation
Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Trigger on "노션 검색", "조사해줘", "리서치 정리". For meeting prep use meeting-intelligence; for saving knowledge use knowledge-capture; for spec breakdown use spec-to-implementation.
documentation
session-analyzer
This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants to verify that a skill executed correctly in a past session. Post-hoc analysis of Claude Code sessions to validate skill/agent/hook behavior against SKILL.md specifications.
development
youtube
유튜브 채널 운영 전문가. 콘텐츠 기획부터 제목/썸네일, 영상 제작, 채널 관리, 수익화, 영상 요약까지 전 영역 지원. Routes to the appropriate sub-skill. Trigger on "유튜브", "YouTube", "영상 기획", "콘텐츠 기획", "아웃라이어", "알고리즘", "썸네일", "제목 공식", "클릭률", "영상 제작", "원고", "인트로", "편집", "채널 브랜딩", "댓글 관리", "수익화", "키 콘텐츠", "풀링 콘텐츠", "객단가", "유튜브 정리", "영상 요약", "transcript 번역", "YouTube digest", "영상 퀴즈". Sub-skills — 기획 (콘텐츠 기획, 알고리즘 전략, 아웃라이어 제작, 시청자 풀 분석), 썸네일 (제목/썸네일 제작, 19가지 제목 공식, A/B 테스트), 제작 (원고 작성, 인트로 구성, 편집 기법, 시청자 참여 유도), 채널 (채널 브랜딩, 이미지 관리, 댓글 관리), 수익화 (키/풀링 콘텐츠, 상품 판매 전략, 객단가 최적화), 요약 (YouTube 영상 분석, transcript 추출/번역, 퀴즈, Deep Research).
research
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
tools
기획
유튜브 콘텐츠 기획 및 알고리즘 전문가. 영상 주제 기획, 아웃라이어 전략, 시청자 풀 분석, 알고리즘 치트키가 필요할 때 사용.
tools
agent-council
Collect and synthesize opinions from multiple AI agents. Use when users say "summon the council", "ask other AIs", or want multiple AI perspectives on a question.
testing
clarify
Clarify ambiguity in user requests, strategies, or approaches. Routes to the appropriate sub-skill. Trigger on "clarify", "명확히", "뭘 원하는 건지", "뭘 놓치고 있지", "blind spots", "관점 전환", "다른 방법 없을까", "/clarify". Sub-skills — vague (requirement clarification, "요구사항 정리", "spec this out"), unknown (strategy blind spots with Known/Unknown quadrants, "4분면 분석", "assumption check", "가정 점검"), metamedium (content vs form reframing, "내용 vs 형식", "diminishing returns", "형식을 바꿔볼까").
testing
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
development
skills/dev
--- name: dev description: Developer workflow tools for technical research, decision-making, and development practices. Routes to the appropriate sub-skill. Trigger on "기술 의사결정", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "뭐 쓸지 고민", "트레이드오프", "개발자 반응", "커뮤니티 의견", "리서치해줘", "모범 사례", "developer reactions", "tech decision", "tech research", "git convention", "커밋 메시지", "브랜치", "TDD", "테스트 주도", "Red-Green-Refactor", "vibe coding", "AI 개발". Sub-skills — tech-research (기술 리서치 & 의사결정: scan/research/decisio
tools
frontend
Frontend development best practices and tools. Routes to the appropriate sub-skill. Trigger on "React", "Next.js", "프론트엔드", "컴포넌트", "deploy", "배포", "UI 디자인", "UI 리뷰", "성능 최적화", "React Native", "모바일 앱", "풀스택", "FSD", "Feature-Sliced Design", "Playwright", "E2E 테스트", "랜딩페이지", "웹 디자인", "인터페이스 디자인", "frontend design". Sub-skills — react-best-practices (React/Next.js performance optimization), composition-patterns (React composition and component architecture), react-native-skills (React Native/Expo mobile best practices), frontend-design (distinctive, production-grade frontend interface design with bold aesthetics), vercel-deploy-claimable (Vercel deployment), nextjs-fullstack (Next.js 15 fullstack with FSD architecture, ShadCN, Jotai, Playwright, "풀스택 개발", "FSD 구조", "E2E 테스트").
tools
gemini-cli
Use Gemini CLI for large codebase analysis when context limits are exceeded. Use `gemini -p` with @ syntax to include files/directories when analyzing entire codebases, comparing multiple large files, understanding project-wide patterns, or verifying implementation across files exceeding 100KB total.
tools
gmail
This skill should be used when the user asks to "check email", "read emails", "send email", "reply to email", "search inbox", or manages Gmail. Supports multi-account Gmail integration for reading, searching, sending, and label management.
testing
history-insight
This skill should be used when user wants to access, capture, or reference Claude Code session history. Trigger when user says "capture session", "save session history", or references past/current conversation as a source - whether for saving, extracting, summarizing, or reviewing. This includes any mention of "what we discussed", "today's work", "session history", or when user treats the conversation itself as source material (e.g., "from our conversation").
development
interactive-review
Interactive markdown review with web UI. Use when user says 'review this', 'check this plan', '피드백', '검토해줘', 'review', or specifies a file path to review. Opens a browser-based review interface with checkboxes and inline comments.
development
kakaotalk
This skill should be used when the user asks to "카톡 보내줘", "카카오톡 메시지", "KakaoTalk message", "채팅 읽어줘", "~에게 메시지 보내줘", or needs to send/read messages via KakaoTalk on macOS.
tools
knowledge-capture
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking. Trigger on "노션에 저장", "문서화해줘", "위키에 추가". For meeting prep use meeting-intelligence; for research reports use research-documentation; for spec breakdown use spec-to-implementation.
development
meeting-intelligence
Prepares meeting materials by gathering context from Notion, enriching with Claude research, and creating both an internal pre-read and external agenda saved to Notion. Trigger on "회의 준비", "미팅 자료", "meeting prep". For saving knowledge to Notion use knowledge-capture; for research reports use research-documentation; for spec breakdown use spec-to-implementation.
documentation
nextjs-fullstack
Next.js fullstack development guidelines for React 19 and Next.js 15+. Use when building Next.js applications with Feature-Sliced Design, TailwindCSS v4, ShadCN, Jotai, React Query, and Supabase integration. Covers file naming, component architecture, testing with Vitest/Playwright, UI/UX design patterns, and Toss frontend principles.
development
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
development
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
development
session-wrap
Session wrap-up with multi-agent analysis. Use when the user says 'wrap', '/wrap', 'session wrap', 'end session', 'what should I commit', or wants to analyze completed work before ending a coding session. Suggests documentation updates, automation opportunities, and follow-up tasks.
tools
spec-to-implementation
Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking. Trigger on "스펙 구현", "태스크 분해", "구현 계획". For meeting prep use meeting-intelligence; for saving knowledge use knowledge-capture; for research reports use research-documentation.
development
tech-research
기술 리서치 및 의사결정 통합 스킬. 커뮤니티 의견 스캔, 구현 전 리서치, 기술 의사결정을 모드별로 제공. "개발자 반응", "커뮤니티 의견", "리서치해줘", "모범 사례", "A vs B", "비교 분석", "뭐 쓸지", "기술 의사결정" 요청에 사용. 3가지 모드 — scan (커뮤니티 의견만), research (구현 전 리서치), decision (기술 의사결정 분석).
testing
unknown
This skill should be used when the user provides a strategy, plan, or decision document and wants to surface hidden assumptions and blind spots using the Known/Unknown 4-quadrant framework. Trigger on "known unknown", "4분면 분석", "blind spots", "뭘 놓치고 있지", "뭘 모르는지 모르겠어", "전략 점검", "전략 분석", "assumption check", "가정 점검", "quadrant analysis", "what am I missing". Strategy-level blind spot analysis with hypothesis-driven questioning. For requirement clarification use vague; for content-vs-form reframing use metamedium.
development
vague
This skill should be used when the user's request or requirement is ambiguous and needs iterative questioning to become actionable. Trigger on "clarify requirements", "refine requirements", "요구사항 명확히", "요구사항 정리", "뭘 원하는 건지", "make this clearer", "spec this out", "scope this", "/clarify". Turns vague inputs into concrete specs. For strategy blind spots use unknown; for content-vs-form reframing use metamedium.
content-media
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
development
vibe-coding
AI-assisted development workflow with TDD, context management, and incremental implementation. Use when developing features with AI assistance, managing code context for AI tools, implementing features step-by-step, or when encountering repeated errors needing web search for resolution.
tools
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
development
supabase-dev
Supabase development guidelines for Next.js applications. Use when working with Supabase Auth SSR, database migrations, RLS policies, database functions, Edge Functions, or declarative schema management. Covers @supabase/ssr patterns, PostgreSQL best practices, and Deno-based Edge Functions.
development
git-convention
Git convention for branch naming, commit messages, and issue labels based on GitFlow and Conventional Commits. Use when creating branches, writing commit messages, or setting up issue labels.
tools
spec
Spec-driven development: interview the user in depth to produce a comprehensive technical spec. Use when the user says "spec", "스펙", "스펙 작성", "기능 정의", "요구사항 정리", "interview me", "spec this out", "feature spec", or wants to define a feature/project before implementation. Also triggers when a SPEC.md file is referenced.
development
karpathy-guidelines
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
development