hamsurang

Use when the user wants to learn a technical topic through structured, multi-session tutoring with prerequisite tracking and knowledge graphs. Activates on "I want to learn X", "teach me X", "let's study X", or resuming a previous learning session. Do NOT activate for quick reference lookups or one-off coding questions — only for sustained learning goals.

Use when the user mentions 'hamsurang presentation', 'hamsurang PPT', 'hamsurang slide', '함수랑 발표', '함수랑 슬라이드', '함수랑 PPT', 'hamsurang 발표', or any presentation request in a Hamsurang (함수랑산악회) context — even if they don't explicitly say 'slide'.

Use when the user wants to manage velog.io blog posts from the terminal. Activates when the user mentions velog, wants to publish a blog post, list their velog posts, create or edit articles, manage drafts, or check trending posts on velog.io. Also use when the user writes markdown content and wants to publish it as a blog post, or when they ask about their velog account status. Even if they just say "post this to my blog" or "publish this", consider activating if velog-cli is installed.

Use when the user explicitly requests their personal vault notes as conversational context. Activates on "이전에 정리한 거 있어?", "내 노트 참고해서 답해줘", "check my notes about", "I wrote something about this before", "what do my notes say about". Do NOT trigger for vault management (creating, moving, editing, searching notes) — those belong to the obsidian skill. Do NOT trigger for generic Obsidian or Zettelkasten questions.

Use when the user mentions Obsidian, vault, daily notes, wikilinks, frontmatter, backlinks, graph view, or obsidian-cli. Activates for searching, creating, editing, moving notes in an Obsidian vault, managing YAML frontmatter, setting up Zettelkasten vault structure, or syncing vaults via Obsidian Headless (ob CLI). Also trigger on Korean phrases like "노트 만들어줘", "vault 동기화", or "frontmatter 수정해줘". Do NOT trigger for generic Markdown editing (README, docs) or other note apps (Notion, Bear). Do NOT activate when the user wants to use vault notes as conversational context (e.g., "내 노트 참고해서 답해줘", "check my notes about X", "이전에 정리한 거 있어?") — that belongs to the obsidian-brain skill.

Use when the user asks questions about a GitHub repository's architecture, API, or internals, or mentions deepwiki-cli or DeepWiki. Activates when the user needs to understand a codebase they haven't cloned locally, or asks how a library or framework works. Do NOT activate for local codebases already accessible on disk or private repositories.

Use when working with GitHub from the command line using the gh CLI tool. Trigger on "create PR", "open pull request", "list issues", "check CI", "merge PR", "review PR", "create issue", "release", "gh auth", "clone repo", "fork repo", "close issue", "view workflow run", or any GitHub operation from the terminal. Do NOT trigger for GitHub web UI actions or direct REST API calls without gh.

Use when the user wants to contribute to an open-source library, says "analyze this library for contribution", "I want to contribute to X", "help me contribute to", "contribution readiness", or "기여하고 싶다". Do NOT activate for general "how does X work" questions (use deepwiki-cli instead).

Use when extracting a Code Complete study chapter page from Notion ("산출물" database) into a 3-Zone YAML file — including initial pulls, re-extraction after Notion updates, mapping unknown block types, troubleshooting parse failures, or verifying member opinion preservation. Also use when the 9-section Notion template layout needs to be translated into structured data agents can consume.

Use when computing Code Complete study-level aggregates — verdict distribution across chapters, voting averages per chapter and per member, highest/lowest rated chapters, best discussion curation, Devil's Advocate collection, member activity counts. Also use when regenerating the /appendix dashboard after new chapter YAMLs arrive.

Use when reordering, bridging, or restructuring Code Complete chapter content for reader flow — deciding where to place Verdict badge, voting bar, member opinions, or FE checklist, writing transition sentences between sections, or detecting when a chapter should break from the default render order. Also use when validating that human_only fields were preserved byte-for-byte after editing.

Use when user wants to publish, update, or re-run Code Complete 2 study artifacts from Notion to Docusaurus — including phrases like "산출물 퍼블리싱", "Notion에서 Docusaurus", "챕터 업데이트", "재실행", "일부 장만 다시", "부록만 재생성", "대시보드 업데이트", "새 주차 반영", "편집 스타일 바꿔". Covers initial run, partial re-run, dashboard-only refresh, and feedback-driven iteration on previously generated MDX.

Use when translating Code Complete's Java/C++ examples into 2026 React/TypeScript Before-After pairs, or when mapping FE checklist items to specific ESLint / typescript-eslint / react-hooks / jsx-a11y rules. Also use when original code has no FE equivalent (pointers, manual memory management) and a "principle only, no code" fallback is needed. Do not use when content belongs to human_only zone.

Use when creating, modifying, or importing custom MDX React components for Code Complete chapter pages — Verdict badge, MemberOpinion callout with emoji, VotingBar, DevilsAdvocate quote, BestPickCallout, VerdictDistribution chart, BestDiscussions list. Also use when a new visual element is needed in a chapter page beyond these seven, or when component props need to align with YAML human_only zone keys.

Use when converting a finalized 3-Zone chapter YAML (plus optional dashboard.yml) into Docusaurus MDX files — generating frontmatter with authors/ai_assisted/source metadata, importing custom components, placing components in the editor-specified render_order, writing the /appendix dashboard page, and preserving backups of previously written MDX. Also use when deciding which part-XX/ folder a chapter belongs to.

Use when scanning Docusaurus MDX files for AI-generated writing symptoms in Korean — cliché openers ("이제부터는", "자 그럼"), overly polite indirections, empty meta-sentences, bullet-point fragmentation, pronoun overuse, emotional filler adjectives, needless analogies. Only scan ai_editable zones indicated by frontmatter ai_assisted list. Do not scan human_only component props (MemberOpinion, DevilsAdvocate, BestPickCallout, VotingBar).

Generate complete React Hook Form code from natural language field definitions. Use when the user wants to scaffold a typed form with validation and error handling.

React Hook Form installation, setup, and hook usage guide. Use when the user asks how to install, configure, or use react-hook-form in their project.

Recommend the right React Hook Form API or pattern for your use case. Use when the user asks which hook, component, or pattern to use for a specific form requirement.

Bump vite-task git dependency to the latest main commit. Use when you need to update the vite-task crates (fspy, vite_glob, vite_path, vite_str, vite_task, vite_workspace) in vite-plus.

클로드코드에서 실행되는 포켓몬을 키우는 컴패니언 시스템. 세션 시작 시 파트너 포켓몬을 자동으로 보여주고, 코드 작성 활동에 따라 경험치가 쌓여 포켓몬이 진화하며, 업적 달성 시 새 포켓몬이 합류합니다. 언제나 이 스킬을 사용하세요. 대화 시작 시에도 자동으로 파트너 포켓몬 상태를 보여주세요. 포켓몬등의 키워드를 말했을 떄 사용해라.