Claude Skills by yongwoon

(ywc) Use when creating, auditing, pruning, or resolving the worktree location for an isolated workspace — delegated from `ywc-parallel-executor` (creation, Pre-flight audit) and `ywc-finish-branch` (post-merge prune), standalone for one-off use. Triggers: "worktree 생성", "worktree 정리", "worktree 위치 확정", "ワークツリー作成", "ワークツリー監査", "create worktree", "audit worktrees", "prune worktrees", "ywc-worktrees". Do not use for branch creation/deletion alone (use `git checkout -b` / `git branch -d`), PR cr...

(ywc) Use when the user explicitly wants autonomous end-to-end delivery through Plan -> Execute -> Evaluate -> Repeat; supports resuming an existing `tasks/` run with `--resume`. Triggers: "agentic end-to-end lifecycle", "run the full lifecycle", "ywc-agentic", "자율 end-to-end 실행", "自律エンドツーエンド実行". Do not use for generic planning (use ywc-plan), an ordinary direct change (use the implementation workflow), or one-off execution without autonomous orchestration (use an executor).

(ywc) Validate an optional repository-root architecture-invariants.json contract and bounded normalized edge evidence. Triggers: "architecture invariants", "architecture boundary", "architecture contract", "boundary validation". Validation-only in v1; never executes verifier data. Do not use for: verifier execution, general architecture advisory or design trade-off judgment (use ywc-architect), or security review (use ywc-security-audit / ywc-security-engineer).

(ywc) Use when planning a secure application authentication feature, choosing an auth library/service from project evidence, or gating auth implementation through policy, security audit, and E2E. Triggers: "auth implementation", "implement authentication", "로그인 구현", "인증 구현", "OAuth 설정", "ywc-auth-implement". Do not use to hand-roll JWT/password/secret crypto, implement an application without approved auth policy, or replace a security audit.

(ywc) Use when the user has a rough idea or "let's build X" framing and intent is not yet pinned down. Clarifies purpose, constraints, success criteria, and 2-3 approaches before handing off to ywc-plan. Triggers: "아이디어", "brainstorm", "let's build", "アイディア", "ブレスト", "ywc-brainstorm". Do not use for an already-clear request (use ywc-plan), spec validation (use ywc-spec-validate), library/framework comparison (use ywc-tech-research), or implementation-time questions (use ywc-code-gen).

(ywc) Use when generating CHANGELOG.md entries or user-facing release notes from git history, merged PRs, or ywc-release-pr-list output after a release or sprint. Triggers: "changelog 작성", "release notes", "リリースノート作成", "changelog". Do not use for merged-PR attribution tables (use ywc-release-pr-list), committing release-note changes (use ywc-commit), creating the release PR (use ywc-create-pr), or post-fix incident analysis (use ywc-incident-postmortem).

(ywc) Use when the user wants parallel multi-layer code generation (Backend + Frontend + QA simultaneously) from a spec. Triggers: "코드 생성", "code gen", "풀스택 생성", "full-stack generation", "scaffold feature", "CRUD 생성", "API + UI 동시 생성", "コード生成". Do not use for a single approved spec or ticket (use ywc-implement), single-file edits, refactoring an existing module, debugging, or when no specification exists.

(ywc) Use when the user says "commit", "커밋", "커밋 해줘", "commit push", "push", "지금까지 한 작업 커밋", "コミットして", "プッシュして", or any phrase indicating intent to stage, commit, or push current work. Do not use for PR creation (use ywc-create-pr), handling PR review feedback (use ywc-handle-pr-reviews), code review (use ywc-impl-review), or making code changes.

(ywc) Use when checking readiness before non-trivial implementation, executor/code-gen delegation, or a design path with material rework cost. Triggers: "confidence check", "confidence gate", "ready to implement", "should I proceed", "준비 됐어", "구현 시작해도 돼", "実装着手", "確信度チェック", "ywc-confidence-gate". Do not use for completion verification (use ywc-verify-done), spec quality review (use ywc-spec-validate), implementation review (use ywc-impl-review), or brainstorming intent (use ywc-brainstorm).

(ywc) Use when the user wants to open a pull request and says "create a PR", "open a PR", "submit code for review", "push and create PR", "PR 만들어줘", "풀리퀘 작성", "プルリク作成", or is wrapping up a feature branch. Do not use for committing only without PR creation, or for handling existing PR review comments (use ywc-handle-pr-reviews).

(ywc) Use when a bug, test/build failure, or other unexpected behavior appears before any fix is proposed. Forces root-cause investigation and blocks symptom patching. Triggers: "디버그", "버그", "debug", "デバッグ", "ywc-debug-rootcause". Do not use for implementation drafting (use ywc-code-gen), incident postmortems (use ywc-incident-postmortem), security triage (use ywc-security-audit), or pre-implementation confidence checks (use ywc-confidence-gate).

(ywc) Use when an existing frontend surface looks generic or AI-made and needs visual renewal, or an AI-slop audit before shipping. Triggers: "디자인 리뉴얼", "AI 슬롭", "design renew", "デザインリニューアル", "デザイン刷新". Do not use for UX/accessibility review (use ywc-ui-ux-review), brand-new UI from scratch (use frontend-design or impeccable), backend/API review (use ywc-impl-review), product/business review (use ywc-product-review), or preference capture without code changes (use ywc-review-learnings).

(ywc) Use when parallel Git worktrees run separate Docker stacks and collide on host ports, for example "port is already allocated". Derives a deterministic per-worktree host-port block and COMPOSE_PROJECT_NAME for setup, teardown, and audit; primarily called by ywc-parallel-executor. Triggers: "docker port 격리", "port is already allocated", "docker isolate", "Docker ポート分離", "ywc-docker-isolate". Do not use for non-Docker isolation, ywc-sequential-executor, or a standalone container manager.

(ywc) Use when designing an automated E2E strategy for a web app, setting up Playwright, auditing E2E coverage gaps, or generating Playwright tests for a critical user flow with CI integration. Triggers: "E2E 테스트 전략", "Playwright 설정", "e2e test strategy", "playwright setup", "playwright test", "E2Eテスト戦略", "Playwright設定". Do not use for manual verification sheets (use ywc-gen-testcase), unit/integration test implementation, or security-focused penetration testing (use ywc-security-audit).

(ywc) Use when delivering one completed feature branch to the base branch: PR-ready, CI wait, bot review polling, merge, post-merge verification, task bookkeeping, and local branch cleanup. Triggers: "finish branch", "deliver branch", "ywc-finish-branch", "merge feature branch", "branch 마무리", "ブランチ完了", "deliver task". Do not use for branch creation, worktree management, draft PR creation alone (use ywc-create-pr), or PR review comment handling (use ywc-handle-pr-reviews).

(ywc) Use when generating a manual verification testsheet (developer + QA gate) from a PR, task directory, task directory range, git range, or diff, with Markdown or HTML output. Triggers: "generate test case", "testsheet", "QA checklist", "PR 테스트 케이스", "테스트시트", "テストシート作って", "manual test", "release 범위 test", "수기 검증". Do not use for writing automated unit/integration tests, code-level test generation, or in-IDE test scaffolding.

(ywc) Use when an open GitHub PR has review threads, comments, or feedback that must be fetched, fixed, replied to, marked, pushed, and CI-verified. Triggers: "handle PR reviews", "review comments", "리뷰 대응", "レビュー対応", "ywc-handle-pr-reviews". Do not use for standalone feedback before PR automation (use ywc-receive-review), new PR creation (use ywc-create-pr), doing the code review yourself (use ywc-impl-review), review learnings (use ywc-review-learnings), or changes outside open-PR context.

(ywc) Use when authoring Terraform from a design for AWS, GCP, Azure, or Kubernetes/Helm, with validate/plan verification and a blast-radius summary. Triggers: "IaC 작성", "terraform 작성", "write terraform", "IaC を書いて", "ywc-iac-author". Do not use for application/business logic, topology design first (use ywc-infra-design), IaC review (use ywc-infra-review), cost/right-sizing remediation (use ywc-infra-optimize), or worktree Docker port collisions (use ywc-docker-isolate).

(ywc) Use when implementation is complete and the user wants pre-PR code quality review, spec conformance checks, or comprehensive implementation validation. Triggers: "구현 검증", "impl review", "코드 리뷰", "実装レビュー", "ywc-impl-review". Do not use for active code generation (use ywc-code-gen), spec-only review before code exists (use ywc-spec-validate), product/business review (use ywc-product-review), review learnings (use ywc-review-learnings), or UI-only live design audits (use ywc-ui-ux-review).

(ywc) Use when the user asks to implement exactly one approved repository specification or ticket through a focused, review-gated change. Triggers: "implement approved spec", "implement ticket", "direct implementation", "승인된 명세 구현", "チケットを実装". Do not use for vague ideas (use ywc-brainstorm or ywc-plan), parallel multi-layer generation (use ywc-code-gen), or generated task directories (use ywc-sequential-executor).

(ywc) Use when a production incident needs a structured postmortem: timeline reconstruction, 5 Whys, impact assessment, prevention actions, and optionally a sanitized client-facing report. Triggers: "장애 회고", "postmortem", "incident report", "ポストモーテム", "incident postmortem". Do not use for proactive security scanning before an incident (use ywc-security-audit), unrelated code review (use ywc-impl-review), or release-note generation after a fix (use ywc-changelog-release-notes).

(ywc) Use when designing cloud/infrastructure architecture before IaC: provider, topology, and a reliability/cost/security pre-check that produces infra-design.md for ywc-iac-author. Triggers: "인프라 설계", "infra design", "インフラ設計", "ywc-infra-design". Do not use for writing IaC (use ywc-iac-author), source layout (use ywc-project-scaffold), tech comparison alone (use ywc-tech-research), reviewing provisioned infra (use ywc-infra-review), or worktree Docker port collisions (use ywc-docker-isolate).

(ywc) Use when improving existing infrastructure: cost right-sizing, unused resource cleanup, reserved/spot adoption, drift remediation, and reliability hardening for AWS, GCP, Azure, or K8s. Triggers: "인프라 개선", "비용 최적화", "optimize infrastructure", "インフラ最適化", "ywc-infra-optimize". Do not use for greenfield infrastructure design (use ywc-infra-design), first-time IaC authoring (use ywc-iac-author), pre-apply review (use ywc-infra-review), or app hotspots (use ywc-performance-engineer).

(ywc) Use when reviewing IaC or cloud configuration for misconfiguration, least privilege, cost, and reliability before apply across AWS, GCP, Azure, or K8s Terraform. Fans out to security, cost, and reliability lenses. Triggers: "인프라 리뷰", "IaC 리뷰", "infra review", "インフラレビュー", "ywc-infra-review". Do not use for app-code auth/injection review (use ywc-security-audit), writing IaC (use ywc-iac-author), drift remediation (use ywc-infra-optimize), or general app code review (use ywc-impl-review).

(ywc) Use when the user wants to merge Dependabot PRs, batch-process dependency updates, or clean up accumulated Dependabot PRs. Triggers: "merge dependabot", "dependabot PR", "dependency updates", "security updates merge", "디펜다봇 머지", "依存関係更新マージ". Do not use for non-Dependabot PRs, manual dependency upgrades, or for merging feature PRs (use ywc-create-pr or platform tools).

(ywc) Use when first entering an unfamiliar repository to generate a starter AGENTS.md or an onboarding architecture/convention briefing. Triggers: "onboard me", "이 repo 처음이야", "리포 분석해줘", "generate AGENTS.md", "walk me through this repo", "コードベースを案内して", "ywc-onboard-repo". Do not use for brand-new project scaffolding (use ywc-project-scaffold), CodeTour `.tour`, one-file explanation, or codemap refresh after the repo is understood.

(ywc) Use when multiple independent tasks from tasks/ can run simultaneously and the user wants faster execution via Git Worktree isolation. Triggers: "병렬 실행", "parallel execute", "parallel-executor", "agent executor", "동시 실행", "워크트리 실행", "execute tasks in parallel", "run tasks simultaneously", "並列実行", "並列ワークフロー". Do not use for strictly sequential tasks (use ywc-sequential-executor), single-task execution, or when no dependency-graph.md exists.

(ywc) Use when a rough feature idea or change request needs a concrete plan, scale assessment, and routing before implementation. Triggers: "plan 세워줘", "계획 세워", "plan this", "make a plan", "プラン作成", "計画立てて", "ywc-plan". Do not use for spec validation (use ywc-spec-validate), finalized-spec task decomposition (use ywc-task-generator), product/business reasoning (use ywc-product-review), or architecture-only exploration (use ywc-tech-research).

(ywc) Use when the user wants a business/service perspective review of a project (user value, UX, growth, risk, market). Triggers: "product review", "service feedback", "비즈니스 관점 리뷰", "서비스 개선 포인트", "what should we improve", "プロダクトレビュー", "サービス改善". Do not use for code-level review (use ywc-impl-review), security review (use ywc-security-audit), or UI/UX implementation review (use ywc-ui-ux-review).

(ywc) Use when creating or updating project docs in Korean, Japanese, English, Chinese, or Spanish. Triggers: "문서 작성", "문서", "document this", "write a doc", "English docs", "Chinese docs", "Spanish docs", "写文档", "crear documentación", "ドキュメント作成". Do not use for code comments, root README changes, project structure design (use ywc-project-scaffold), implementation tasks (use ywc-task-generator), domain vocabulary docs (use ywc-ubiquitous-language), or formal specifications (use ywc-spec-writer).

(ywc) Use when designing a new project's directory structure or architecture skeleton before files are generated. Triggers: "project structure", "scaffold a new project", "folder layout", "프로젝트 구조", "디렉토리 구조", "プロジェクト構成", "フォルダ構成", or reviewing this skill's `references/<language>.md`. Do not use for generic documentation review, existing repo changes, file generation (use ywc-code-gen), task creation (use ywc-task-generator), or onboarding (use ywc-onboard-repo).

(ywc) Use when receiving code-review feedback and about to reply or implement changes; verify comments before agreeing or coding, avoid performative acknowledgments, and clarify unclear items first. Triggers: "리뷰 받았어", "리뷰 코멘트", "리뷰 대응", "review feedback", "received review", "respond to review", "レビュー受信", "レビュー対応", "ywc-receive-review". Do not use for performing a code review (use ywc-impl-review), creating a PR (use ywc-create-pr), or PR-comment automation (use ywc-handle-pr-reviews).

(ywc) Use when removing dead code, unused dependencies/imports/files, consolidating near-duplicate utilities, or running a hygiene pass. Triggers: "dead code 제거", "unused import 정리", "knip / depcheck / ts-prune 돌려줘", "refactor clean", "dead code cleanup", "remove unused exports", "デッドコード削除", "未使用 import 整理", "ywc-refactor-clean". Do not use for feature implementation in the same branch, behavior-changing refactors (use ywc-tdd-ritual + ywc-code-gen), or performance/architecture restructuring.

(ywc) Use when working on a release PR (for example develop→main) and the user wants the merged PR numbers grouped by author for the PR description's `## PR LIST` section. Triggers: "release PR list", "릴리즈 PR 정리", "릴리스 PR 리스트", "release pr 정리", "リリースPR一覧", "PR LIST 갱신". Do not use for user-facing release notes or CHANGELOG entries (use ywc-changelog-release-notes), normal feature PR creation (use ywc-create-pr), or PR review comment handling (use ywc-handle-pr-reviews).

(ywc) Use when capturing or curating durable repo-specific code-review preferences. Triggers: "리뷰 학습 누적", "리뷰 피드백 축적", "review learnings", "review memory", "remember this review preference", "レビュー学習". Do not use for implementation review (use ywc-impl-review), PR comment handling (use ywc-handle-pr-reviews), in-the-moment review replies (use ywc-receive-review), domain vocabulary (use ywc-ubiquitous-language), or spec review (use ywc-spec-validate).

(ywc) Use when reviewing authentication/authorization code, external-facing endpoints, code handling sensitive data, or for periodic security reviews. Triggers: "보안 점검", "security audit", "보안 감사", "OWASP", "취약점 분석", "보안 리뷰", "security check", "is this code secure", "セキュリティ監査". Do not use for general code review (use ywc-impl-review), product-level risk review (use ywc-product-review), or for code that does not touch auth/external input/sensitive data.

(ywc) Use when executing tasks from the tasks/ directory in strict order through their full lifecycle. Triggers: "execute task", "implement tasks 000001-010", "run the next task", "implement all remaining tasks", "start implementing", "sequential-executor", "순차 실행", "タスク順次実行". Do not use for parallel/concurrent execution (use ywc-parallel-executor), code generation without a task directory (use ywc-code-gen), or a single approved spec/ticket implementation (use ywc-implement).

(ywc) Use when configuring the default output language or collaborator initials for Codex ywc skills. Triggers: "ywc-setup", "setup ywc language", "setup collaborator initials", "ywc 언어 설정", "project language default", "user language default". Do not use for Claude Code setup, session language defaults, or generating project documentation.

(ywc) Use when creating or restructuring a ywc-* skill, or auditing ywc-* skills against canonical rules. Triggers: "ywc skill 생성", "create ywc skill", "ywc skill 만들어줘", "ywc skill 개선", "new ywc skill", "ywc skill audit", "ywcスキル作成", "ywc skill 룰 점검". Do not use for normal task-execution content edits, non-ywc-* skills, or renaming/moving skills.

(ywc) Use when a natural-language goal or existing specification needs to be refined until it is ready for task generation. Triggers: "spec ready", "prepare spec", "스펙 준비", "make this spec ready", "仕様を準備", "タスク生成前に仕様確認". Do not use for direct implementation (use ywc-code-gen or ywc-sequential-executor), one-shot spec review only (use ywc-spec-validate), rough planning without a spec-readiness loop (use ywc-plan), or task decomposition after the spec is ready (use ywc-task-generator).

(ywc) Use when a specification document exists and the user wants to validate spec completeness, consistency, feasibility, or readiness before task decomposition. Triggers: "사양 검토", "spec review", "사양 리뷰", "review specification", "스펙 점검", "check the spec", "is this spec complete", "仕様レビュー", "仕様確認". Do not use for code-level review (use ywc-impl-review), product/business review (use ywc-product-review), or when no specification document exists yet (use ywc-plan or ywc-spec-writer).

(ywc) Use when creating or updating docs/specification/ from project context, task ranges, or PRs. Triggers: "spec 작성", "사양서 작성", "사양서 업데이트", "write spec", "generate specification", "update spec from task range", "update spec from PRs", "中文规格", "escribir especificación", "仕様書作成", "仕様書更新", "ywc-spec-writer". Do not use for spec quality review (use ywc-spec-validate), finalized-spec task decomposition (use ywc-task-generator), or pre-implementation planning without a spec intent (use ywc-plan).

(ywc) Use when converting a specification into implementation tasks. Triggers: "task 생성", "タスク生成", "spec to tasks", "task breakdown", "작업 분해", "仕様からタスク生成", "任务拆分", "从 spec 生成 task", "generar tareas", "desglosar spec", "implementation tasks", "스펙 분해", or any spec-to-task decomposition request. Do not use for direct code implementation, spec review (use ywc-spec-validate), or planning without a written specification.

(ywc) Use when implementing a new feature, bug fix, or behavior change before production code is written; enforce RED → GREEN → REFACTOR and a real failing-test step. Triggers: "TDD", "test first", "테스트 먼저", "regression test", "テスト先行", "ywc-tdd-ritual", "ywc-code-gen --tdd". Do not use for opted-out throwaway prototypes, existing test-failure debugging (use ywc-debug-rootcause), generated/config files, or completion verification (use ywc-verify-done).

(ywc) Use when the user explicitly asks Codex to assemble a specialist team, delegate work to subagents, run a swarm, or split a complex task across parallel expert roles. Triggers: "assemble a team", "use agents", "delegate", "parallel agents", "swarm", "specialist team", "팀 구성", "전문가 팀", "エージェントチーム", "専門家チーム". Do not use for simple questions, single-file edits, strictly sequential work, or any task where the user has not explicitly authorized subagents/parallel/delegated execution.

(ywc) Use when comparing libraries, investigating implementation approaches, evaluating technology options, or gathering sourced best practices before a plan/spec decision. Triggers: "기술 조사", "라이브러리 비교", "research", "compare options", "best way to implement", "技術調査", "ライブラリ比較". Do not use for spec writing (use ywc-spec-writer), spec validation (use ywc-spec-validate), code generation (use ywc-code-gen), or simple doc lookup with no evaluation decision.

(ywc) Use when creating, extracting, or updating a project's ubiquitous language document: the shared domain vocabulary between developers, experts, and LLMs. Triggers: "유비쿼터스 언어 작성", "도메인 용어 정리", "ubiquitous language", "도메인 glossary 만들어줘", "용어집 업데이트", "ubiquitous language 추출", "プロジェクト用語集作成", "domain glossary", "DDD 용어 정리", "ubiquitous language document". Do not use for general project docs (use ywc-project-docs), spec writing (use ywc-plan), or task decomposition (use ywc-task-generator).

(ywc) Use when the user wants a UI/UX review combining static code analysis with live UI exploration across IA, visual design, usability, and accessibility. Triggers: "UI/UX review", "UX 점검", "UI 검토", "usability audit", "design review", "accessibility review", "사용성 점검", "UX 監査", "UI レビュー". Do not use for backend/API review (use ywc-impl-review), product/business strategy review (use ywc-product-review), visual redesign (use ywc-design-renew), or code-only review without a running UI.

(ywc) Use when about to claim work is complete, tests/build pass, a bug is fixed, requirements are met, or a subagent has finished, and before commit, PR creation, executor handoff, or task transition. Triggers: "완료", "끝났어", "verify done", "검증해줘", "done", "完了", "終わった", "ywc-verify-done". Do not use for implementation drafting (use ywc-code-gen), root-cause debugging (use ywc-debug-rootcause), pre-implementation confidence assessment, or exploration before planning (use ywc-plan).

(ywc) Use when a large or uncertain change needs multi-session discovery with a deterministic local map and exactly one active ticket before planning or implementation. Triggers: "wayfinder", "길찾기", "discovery map", "multi-session discovery", "탐색 ticket", "経路整理", "探索マップ", "ywc-wayfinder". Do not use for ordinary planning (use ywc-plan), idea clarification (use ywc-brainstorm), direct implementation, or tracker/database writes outside the local Markdown map.