dotfiles

Use when GenOS 작업에서 얻은 재사용 가능한 지식(플랫폼 패턴·함정·고객사 결정)을 개인 Obsidian vault(Projects/GenonAI)에 기록할 가치가 생겼거나, GenOS 작업 맥락에서 사용자가 "지식 캡처", "vault에 정리/기록", "MOC", "읽는 순서", "field note", "/genos-knowledge-capture"를 요청할 때 사용. Do NOT use for: GenOS와 무관한 노트, 웹 리서치 기반 일반 개념 노트, 단순 진행상황·세션 상태.

Use when user says "wiki compile", "위키 컴파일", "raw 정리", "지식 컴파일", "소스 컴파일", or wants to compile raw sources into a structured wiki. Do NOT use for individual note creation (use obsidian-note) or vault maintenance (use vault-linter).

Use when user says "vault lint", "노트 점검", "vault 정리", "orphan notes", "링크 점검", or wants to check Obsidian vault health. Do NOT use for individual note creation (use obsidian-note) or tag management (use til-tagger).

Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts. Use when user says "다이어그램", "diagram", "excalidraw", "시각화", "아키텍처 그려". Do NOT use for Mermaid diagrams or draw.io.

Use when user mentions "Obsidian", "옵시디언", "write as note", "save to notes", "노트로 저장", or /obsidian-note command. Do NOT use for TIL (use til), YouTube notes (use youtube-summarizer), GenOS 작업 지식 캡처 (use genos-knowledge-capture), or deep/team/multi-angle note research (use agentic-notes).

Use when the user asks to create an Obsidian note with an agent team, deep research, strict verification, multiple angles, or phrases like "팀으로 조사해서 노트", "깊게 조사해서 옵시디언 노트", "/agentic-notes", "--team", "--verify strict", or "--deep". Do NOT use for a simple one-shot Obsidian note; use obsidian-note instead.

Use when user says "commit and push", "커밋하고 푸시", "올려줘", "저장하고 올려". Do NOT use for commit-only (use git-commit) or push-only (use git-push).

Use when user wants to commit changes, says "commit", "커밋", "커밋해줘", "변경사항 저장". Do NOT use for pushing (use git-push) or commit-and-push (use git-commit-and-push).

Review Codex CLI changelog updates against the user's Codex and dotfiles configuration, then recommend which new features are worth adopting. Use when the user mentions "codex 변경사항", "codex changelog", "codex 업데이트 검토", "codex release notes", "codex 버전", "최근 codex 릴리스", gives a Codex CLI version range like 0.136.0..0.137.0, or asks what is worth adopting from Codex updates. Do NOT use for Claude Code changelogs, OpenAI SDK/API model changelogs, or general release-note reading without a dotfiles cross-reference.

Use when user asks to write a blog post, tech article, tutorial, or "블로그 글 써줘". Do NOT use for TIL (use til), Obsidian notes (use obsidian-note), or code documentation.

Use when user mentions "TIL", "write TIL", "TIL 작성", "learning note", or /til command. Do NOT use for Obsidian notes (use obsidian-note) or blog posts (use tech-blog-writer).

Use when user provides a URL and asks to "translate", "번역", "한국어로", "Korean translation". Do NOT use for YouTube videos (use youtube-summarizer), original content (use tech-blog-writer), or Obsidian notes (use obsidian-note).

Review Claude Code CLI changelog updates against the user's dotfiles configuration and recommend which new features are worth adopting. Make sure to use this skill whenever the user mentions "claude code 변경사항", "체인지로그 검토", "claude code 업데이트 검토", "release notes 검토", "버전 X 추가할거", "최근 릴리스 뭐있나", "claude code changelog review", references CHANGELOG.md or anchor URLs like

Use when writing tests, setting up pytest, implementing TDD, creating fixtures, or mocking dependencies. Do NOT use for general patterns (use python-patterns) or style config (use python-code-style).

Use when writing tests, adding features TDD-style, or setting up test infrastructure for Spring Boot. Do NOT use for JPA/Testcontainers testing (use jpa-patterns), general TDD (use superpowers test-driven-development), or verification (use springboot-verification).

Use when making architectural decisions, choosing between frameworks/libraries/databases, deciding on data models, or recording any decision that would be expensive to reverse. Do NOT use for code documentation (comments belong in code), daily notes (use obsidian-note), or TIL (use til).

Use when designing API endpoints, reviewing API contracts, adding pagination/filtering, or planning versioning strategy. Do NOT use for API consumption, client-side HTTP, or GraphQL.

Provides concrete 6-step triage checklist (Reproduce → Localize → Reduce → Fix → Guard → Verify) with git bisect workflow, error-specific patterns (test/build/runtime), and regression test templates. Use when a bug is confirmed and you need actionable steps, not methodology. Pairs with superpowers:systematic-debugging for the hypothesis-driven investigation phase. Do NOT use for feature implementation or code review.

Use before opening PRs, after major refactoring, or pre-deployment for Spring Boot verification. Do NOT use for writing tests (use springboot-tdd), security implementation (use springboot-security), or general patterns (use springboot-patterns).

Use when user provides YouTube URL/link, mentions "youtube summarize", "유튜브 요약", "video summary", "transcript to note". Do NOT use for web article translation (use translate-article), regular Obsidian notes (use obsidian-note), or TIL (use til).

Use when user says "research", "리서치", "조사해줘", "wiki에서 찾아", "연구해줘", or wants to ask questions against their knowledge base and have answers automatically filed back. Do NOT use for individual note creation (use obsidian-note) or article translation (use translate-article).

Use when user says "TIL 태그", "태그 업데이트", "tag TIL", "새 TIL 태그", or when Wiki has untagged files. Do NOT use for general Obsidian note tagging.

Use when user says "learning summary", "what I learned today", "오늘 뭐 배웠지", "session summary", "학습 정리", or wants to extract learnings from current session. Do NOT use for session handoff (use session-handoff), development work logs (use devlog), or direct TIL/note creation (use til or obsidian-note).

Use when writing or refactoring Go code, designing packages, implementing concurrency, using generics, or building HTTP services. Do NOT use for database optimization (use sql-optimization-patterns), API design (use api-design), or CI/CD (use github-actions).

Use when writing Java 21+ code, refactoring to modern idioms, choosing records vs classes, using virtual threads, or applying pattern matching. Do NOT use for JPA (use jpa-patterns) or SQL optimization (use sql-optimization-patterns).

Use when designing JPA entities, writing JPQL/Criteria queries, resolving N+1 problems, configuring HikariCP, or choosing ID generation strategies. Do NOT use for raw SQL optimization (use sql-optimization-patterns).

Use when writing or refactoring Kotlin code, implementing coroutines/Flow, designing DSLs, or integrating Kotlin with Spring Boot. Do NOT use for JPA (use jpa-patterns), SQL optimization (use sql-optimization-patterns), or Java patterns (use java-modern-patterns).

Use when configuring ruff/mypy/pyright, setting up formatting, writing docstrings, or establishing coding standards. Do NOT use for general patterns (use python-patterns) or testing (use python-testing).

Use when writing, reviewing, or refactoring Python code, designing data classes, implementing decorators, or choosing concurrency patterns. Do NOT use for linter/formatter config (use python-code-style) or testing (use python-testing).

Use when writing or refactoring React/Next.js components, implementing data fetching, optimizing bundle size, or improving render performance. Do NOT use for general JavaScript or non-React frameworks.

Use when building Spring Boot services, configuring profiles, implementing caching/async, setting up Actuator/Micrometer, or creating REST clients. Do NOT use for JPA (use jpa-patterns), API design (use api-design), security (use springboot-security), testing (use springboot-tdd), or Kotlin (use kotlin-patterns).

Use when configuring Spring Security, implementing JWT/OAuth2 auth, adding role-based access control, or hardening Spring Boot APIs. Do NOT use for general patterns (use springboot-patterns), JPA (use jpa-patterns), or testing (use springboot-tdd).

Use when debugging slow queries, designing indexes, analyzing EXPLAIN output, resolving N+1 problems, or tuning database performance. Do NOT use for basic SQL, simple CRUD, or JPA entity design (use jpa-patterns).

Use when user wants to create a new Skill, validate SKILL.md structure, or reference Anthropic skill design guide. Do NOT use for eval-based improvement or benchmark testing (use skill-creator plugin).

Use when user mentions "agent team", "에이전트 팀", "team spawn", "create team", "팀 구성", "팀 만들어", "병렬로 검토/조사/개발". Do NOT use for single subagent dispatch (use superpowers:dispatching-parallel-agents).

Use when user says "devlog", "작업 로그", "work log", "오늘 작업 기록". Supports /devlog, /devlog [title], /devlog --summary. Do NOT use for git commits (use git-commit), session handoff (use session-handoff), or TIL (use til).

Use when looking up API references, library documentation, CLI commands, or checking version-specific behavior for any developer technology. Prefer this when documentation accuracy matters or model knowledge may be outdated.

Use when user says "push", "push to remote", "푸시해줘", or wants to send committed changes to remote. Do NOT use for commit creation (use git-commit) or commit-and-push (use git-commit-and-push).

Use when user shares a GitHub Actions URL, mentions "CI failed", "빌드 실패", "workflow error", "Actions 실패", "파이프라인 실패", or wants to debug CI/CD issues. Do NOT use for creating workflow YAML, deploying, or non-GitHub CI.

Use when user says "init harness", "하네스 초기화", "하네스 설정", "init rules", "프로젝트 룰 설정", "rules 초기화", "프로젝트 룰", "프로젝트 설정". Do NOT use for skill creation (use skill-guide) or Serena (use init-serena).