toby-plugins

Use this skill whenever the user wants to back up or restore their global Claude Code configuration under ~/.claude — global CLAUDE.md, settings.json, user-level commands/skills/subagents, installed plugin marketplaces, and install manifests. Trigger on "claude backup", "backup claude", "backup my claude config", "snapshot claude", "restore claude", "claude 백업", "클로드 백업", "claude 복구", "claude 복원", "설정 백업", "글로벌 설정 백업", "내 claude 설정 저장", "claude 설정 복원", "plugin 백업", "설치된 플러그인 백업", "백업으로 되돌려", "이전 백업으로 복원", "원래 상태로 되돌려", "backup ~/.claude", "restore my plugins", "migrate claude to another machine". Also trigger when the user is about to do something risky to their global Claude config (big settings edit, plugin overhaul, reinstalling Claude Code) and mentions wanting a snapshot/checkpoint first, or when they mention losing plugins and wanting the previous state back. Do NOT trigger for project-level backups, git stashes, or generic "backup my repo" — this skill is specifically for the ~/.claude user directory.

This skill should be used when the user asks to "create a prd", "write prd for", "plan this feature", "write requirements", "spec out a feature", "product requirements document", "feature spec", "define user stories", "PRD 작성", "PRD 만들어", "PRD 써줘", "요구사항 문서", "기능 명세", "기능 정의서", "프로덕트 요구사항", "스펙 문서 만들어", "유저 스토리 작성", or needs guidance on structured feature planning and requirements documentation. Do NOT trigger for ad-hoc TODO lists, design docs (use a separate design-doc workflow), or sprint-planning tickets — this skill produces a single PRD per feature.

Use this skill to control the cmux terminal app from Claude Code. Trigger on "cmux", "open browser pane", "split pane", "browser split", "open in browser", "cmux browser", "cmux notify", "cmux split", "새 pane 열어", "브라우저 열어", "알림 보내", "사이드바", "workspace 만들어", "pane 분할", "browser automation", "cmux에서", "cmux로", "cmux 사용해서". Also trigger when the user wants to open a URL alongside their terminal, send notifications when a task completes, manage terminal panes programmatically, automate browser interactions from the CLI, or set sidebar status/progress for build scripts. Do NOT trigger for general tmux commands — cmux is a different app. If cmux is not detected (no socket, no CLI), inform the user and skip.

Use this skill to delegate tasks to OpenAI Codex CLI running in the background. Trigger on "delegate to codex", "send to codex", "ask codex to", "run with codex", "have codex do", "codex에게", "codex로", "코덱스에게", "코덱스로", "use codex for", "let codex handle", "codex한테 시켜", "codex로 돌려봐". Also trigger when the user wants a second opinion from another AI specifically mentioning Codex or OpenAI, wants to compare Claude's approach with Codex, or asks to run a task with an external OpenAI agent in parallel. Do NOT trigger for general "delegate" or "외부 AI" requests without mentioning Codex/OpenAI — those may be better handled by gemini-delegate or other tools.

Use this skill to delegate tasks to Google Gemini CLI running in the background. Trigger on "delegate to gemini", "send to gemini", "ask gemini to", "run with gemini", "have gemini do", "gemini에게", "gemini로", "제미나이에게", "제미나이로", "use gemini for", "let gemini handle", "gemini한테 시켜", "gemini로 돌려봐". Also trigger when the user wants a second opinion from another AI specifically mentioning Gemini or Google, wants to compare Claude's approach with Gemini, or asks to run a task with an external Google agent in parallel. Do NOT trigger for general "delegate" or "외부 AI" requests without mentioning Gemini/Google — those may be better handled by codex-delegate or other tools.

Use this skill when the user wants to develop features using Test-Driven Development with an agentic Red-Green-Refactor cycle. Trigger on "start TDD", "do TDD", "TDD로 개발해줘", "TDD 시작", "TDD 팀 만들어", "테스트 주도 개발", "red green refactor", "test-driven development", "테스트 먼저 작성하고 싶어", "write tests first then implement", "테스트부터 짜줘", "TDD 방식으로 구현해줘". Also trigger when a user describes a feature and says they want it built incrementally with tests, e.g. "이 기능 테스트 먼저 만들고 하나씩 구현하자", "build this with failing tests first", or "한 단계씩 테스트 작성하면서 개발하고 싶어". Do NOT trigger for simply writing unit tests after implementation, running existing tests, or debugging test failures — those are not TDD workflows.

Use this skill to send a task to Codex running in a cmux pane and get the result back as a file. Trigger on "toby codex", "toby codex에게", "toby codex한테", "toby codex로", "toby codex에게 해줘", "toby codex한테 시켜", "toby codex로 보내", "toby codex에게 물어봐". Only trigger when the user explicitly says "toby codex" — the "toby" prefix is required to distinguish from codex-delegate. Do NOT trigger on bare "codex" mentions without the "toby" prefix. This skill communicates with a persistent Codex pane in cmux (started by toby-team-starter) and collects the result via a file. Do NOT trigger for codex-delegate (which launches a new codex process in the background).

Use this skill to send a task to Gemini running in a cmux pane and get the result back as a file. Trigger on "toby gemini", "toby gemini에게", "toby gemini한테", "toby gemini로", "toby gemini에게 해줘", "toby gemini한테 시켜", "toby gemini로 보내", "toby gemini에게 물어봐". Only trigger when the user explicitly says "toby gemini" — the "toby" prefix is required to distinguish from gemini-delegate. Do NOT trigger on bare "gemini" mentions without the "toby" prefix. This skill communicates with a persistent Gemini pane in cmux (started by toby-team-starter) and collects the result via a file. Do NOT trigger for gemini-delegate (which launches a new gemini process in the background).

Use this skill to spawn a multi-agent workspace with Codex and Gemini running alongside Claude in cmux. Trigger on "toby team", "toby team 시작", "toby team 준비", "toby team 시작해", "toby team 준비해", "toby 팀 시작", "toby 팀 준비", "agent team", "에이전트 팀", "codex랑 gemini 같이", "start agent team", "팀 시작", "멀티 에이전트 시작", "codex gemini 같이 띄워", "에이전트 팀 만들어", "spawn agents", "launch agents", "에이전트 pane 열어", "agent pane", "start multi-agent", "codex gemini pane". Also trigger when the user wants Codex and Gemini running side-by-side in terminal panes for parallel work, or asks to set up a multi-agent development environment. Do NOT trigger when the user just wants to delegate a single task to codex or gemini — use codex-delegate or gemini-delegate for that. This skill is specifically for spawning persistent agent panes in cmux.

This skill should be used when the user asks about "omc", "oh-my-claudecode", "omc 사용법", "omc 활용", "omc guide", "omc tips", "omc cheatsheet", "omc reference", "omc 모드", "omc 에이전트", "omc 스킬", "which omc mode", "how to use omc", "omc keyword", "omc 매직 키워드", "omc commands", "omc modes comparison", "autopilot vs ralph", "autopilot vs team", "ralph vs ultrawork", "team mode", "omc agent", "omc tool", "omc 설정", "omc setup", "omc doctor", "omc pipeline", "omc architecture", or needs guidance on choosing OMC execution modes, agents, skills, or strategies. Provides a comprehensive quick-reference for oh-my-claudecode v4.10+ plugin.

Spring Boot 프로젝트를 Spring Initializr를 이용해 생성하는 스킬. 사용자가 Spring Boot 프로젝트 생성, 스프링 부트 새 프로젝트, Spring Initializr, 새 스프링 앱 만들기, create spring boot app, 스프링 부트 시작 등을 요청할 때 반드시 이 스킬을 사용한다. 간단한 Spring Boot 시작 요청이라도 이 스킬을 사용해야 한다.

Guide for developing with Spring Boot 4 and Spring Framework 7. Use this skill whenever the user is working on a Spring Boot 4 project, asking about Spring Boot 4 or Spring Framework 7 changes, migrating from Boot 3 to 4, or encountering issues related to Boot 4 breaking changes. Trigger on "Spring Boot 4", "Spring 7", "Boot 4 migration", "Spring Boot 4 변경사항", "Boot 4로 업그레이드", "Spring Boot 4 프로젝트", "spring-boot 4.x", "Spring Framework 7 변경", "Boot 4 에러", "Jackson 3 마이그레이션". Also trigger when the user creates a new Spring Boot project and the version is 4.x, or when build errors suggest Boot 4 compatibility issues (e.g., missing starters, Jakarta EE 11 issues, Jackson 3 package errors, HttpHeaders API changes). Do NOT trigger for Spring Boot 3.x or earlier questions that don't involve upgrading.

Use this skill whenever you help Toby draft, polish, translate, or rewrite a social media post — Facebook, Threads, X, LinkedIn, blog shortform — in Toby's voice. Trigger on "페이스북 글", "페북 글", "facebook 글", "FB 포스트", "SNS 글", "소셜 글", "페북에 올릴", "페이스북에 올릴", "토비 스타일로", "내 스타일로 글 써줘", "이거 페북용으로", "이걸 포스트로", "draft a facebook post", "write this in my style", "turn this into a FB post", "make this post-worthy", "write a social post", "페북 초안", "포스트 초안 써줘". Also trigger when Toby shares a URL and asks for a comment, summarizes an experience and asks for a post draft, or asks to rephrase existing prose to sound more like him. Do NOT trigger for git commit messages, PR descriptions, formal documentation, emails, or anything that is clearly not a public-facing casual post.

This skill should be used when the user asks to "use harness", "하네스 사용", "harness use case", "하네스 유즈케이스", "run harness template", "하네스 템플릿", "harness 실행", "하네스 예제 실행", "pick a harness", "하네스 골라줘", "harness menu", "하네스 메뉴", "select harness use case", "하네스 선택", "quick harness", "하네스 빨리", "start harness", "하네스 시작해줘". Presents a menu of pre-built harness use cases and launches the selected one via the harness:harness skill. Do NOT trigger when the user wants to build a custom harness from scratch — use harness:harness directly for that.

Use this skill at the START of a new Claude Code session to pick up where the previous session left off. Finds the most recent handoff document under `.claude/reports/handoff/`, reads it, then VERIFIES its claims against the live codebase (Read each referenced file, run `git status` / `git log --oneline`) before reporting findings and waiting for user instruction. Treats the handoff as a hypothesis, not fact — previous session may have been confused. Trigger on "catchup", "catch up", "이어서 작업", "이어서 해줘", "이전 세션 이어", "resume from handoff", "handoff 읽어", "handoff 참고해서 시작", "어제 작업 이어서", "지난번 이어서", "새 세션 준비", "prepare to continue", "pick up where we left off", "캐치업". Also trigger when the user starts a new session by referencing prior work ("어제 한 작업 이어서 하자", "계속 하자", "resume the auth refactor") and an `.claude/reports/handoff/` directory exists in the project. Do NOT trigger when the user wants to start a brand-new unrelated task, or when they want to read a specific named document (use Read directly).

Use this skill to write a forward-looking handoff document that prepares the NEXT Claude Code session to pick up where this one stops. Generates a compact markdown file (~2K tokens) under `.claude/reports/handoff/` with Summary, Key Decisions, Traps to Avoid, Working Agreements, Relevant Files (with line numbers), Open Work (status-form only, never imperative), and a Prompt for New Chat that includes a verification instruction. Trigger on "handoff", "hand off", "세션 인계", "인계 문서", "다음 세션으로 넘겨", "end-of-session handoff", "session handoff", "세션 종료 전에 정리해", "handoff 문서 만들어", "handoff 써줘", "write a handoff", "prepare next session", "세션 넘기기 전에", "핸드오프". Also trigger when the user is about to run `/clear`, close the terminal, end the day, or says something like "let's wrap up this session", "세션 끝내기 전에 정리하자". Do NOT trigger for `save-conversation` (which is a retrospective transcript log, not a forward-looking handoff), git commit messages, PRD writing, or CLAUDE.md updates.

Use this skill to save a summary of the current conversation to a markdown file. Trigger on "save conv", "save conversation", "대화 저장", "대화내용 저장", "대화 저장해줘", "대화내용 저장해줘", "conversation 저장", "로그 저장", "대화 기록 남겨", "save chat", "save log", "대화 정리해서 저장", "지금까지 대화 저장", "conv 저장". Also trigger when the user asks to log, archive, or record the current conversation, or wants a summary of what was discussed saved to a file. Do NOT trigger for memory saving (use memory system) or for git commit messages.