Claude Skills by yongwoon

(ywc) Use when periodically evaluating or scoring the quality of existing ywc-* skills or agents in this toolkit, running the evaluate→improve cycle, or auditing the skill/agent catalog for activation accuracy, structure compliance, and behavioral efficacy. Triggers: "skill 평가", "agent 평가", "toolkit 평가해줘", "skill 점수 매겨줘", "평가 사이클", "evaluate skills", "score the agents", "skill quality eval", "스킬 평가", "에이전트 평가", "スキル評価", "エージェント評価", "evaluation cycle", "toolkit 품질 점검". Do not use for authoring...

(ywc) Use when evaluating, scoring, auditing, or producing a prioritized improvement backlog for this repository's Codex ywc-* skills and Codex custom agents as a repeatable maintenance cycle. Triggers: "Codex skill 평가", "Codex agent 평가", "Codex 평가 기준", "codex toolkit 평가해줘", "skill/agent 개선 cycle", "evaluate Codex skills", "score Codex agents", "Codex skill maturity", "Codex scoreboard", "Codex スキル評価", "Codex エージェント評価". Do not use for Claude Code skill/agent evaluation (use .claude/skills/ywc...

<!-- Proposed directory name, e.g. ywc-api-design -->

(ywc) Use when capturing, reading, listing, or curating (deprecating) a project's Architecture Decision Records — durable records of a hard-to-reverse architectural choice and the trade-off reasoning behind it. Triggers: "ADR 작성", "아키텍처 결정 기록해줘", "이 결정 ADR 로 남겨줘", "architecture decision record", "record this decision", "curate an ADR", "deprecate ADR", "ADR-0004 정리해줘", "アーキテクチャ決定記録", "ADR作成". Do not use for durable project intent (use ywc-project-mission), review preferences (use ywc-review-l...

(ywc) Use when the user explicitly requests autonomous, end-to-end lifecycle delivery through Plan → Execute → Evaluate → Repeat. Triggers: "agentic end-to-end lifecycle", "autonomous end-to-end delivery", "run the full lifecycle", "ywc-agentic", "자율 end-to-end 실행", "전체 lifecycle 자율 실행", "自律エンドツーエンド実行". Do not use for generic planning (use ywc-plan), an ordinary direct change (use the implementation workflow), one-off skill invocations or direct task execution without autonomous orchestration...

(ywc) Use when implementing authentication features (email/password, OAuth, MFA, shallow RBAC) — runs a policy interview, detects the stack, recommends battle-tested libraries, then dispatches implementation to ywc-backend-coder/ywc-frontend-coder under TDD discipline and legal-page drafts to ywc-doc-writer. Triggers: "인증 구현", "로그인 기능", "OAuth 연동", "implement auth", "add login", "set up authentication", "認証実装", "ログイン機能", "ywc-auth-implement". Do not use for security code review after implemen...

(ywc) Use when the user has a rough idea, half-formed feature request, or "let's build X" framing and intent isn't pinned down yet. Surfaces purpose, constraints, success criteria, and 2-3 alternatives via Socratic dialogue before implementation, hands off to ywc-plan. Triggers: "아이디어", "구상", "어떻게 만들지", "만들고 싶은데", "brainstorm", "discuss this idea", "ideate", "アイディア", "どう作る", "ブレスト", "ywc-brainstorm". Do not use for an already-clear request (use ywc-plan), validating an existing spec (use ywc-...

(ywc) Use when you need to generate CHANGELOG.md entries or user-facing release notes from git history, merged PRs, or ywc-release-pr-list output after completing a release or sprint. Trigger phrases: "changelog 작성", "릴리즈 노트 생성", "release notes", "変更履歴", "リリースノート作成", "changelog", "what changed in this release", "ywc-changelog-release-notes". Do not use for listing merged PRs as a summary table (use ywc-release-pr-list), committing the changelog file (use ywc-commit), creating the release PR (...

(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 single-file edits, refactoring an existing module, debugging, when a tasks/ directory already defines the work (use ywc-sequential-executor or ywc-parallel-executor), 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, code review, or making code changes.

(ywc) Use when you need to gate an implementation start — before non-trivial implementation, before invoking ywc-code-gen, ywc-sequential-executor, or ywc-parallel-executor, or before committing to a design path with material rework cost. Scores five readiness dimensions and gates with PROCEED/REVIEW/STOP. Triggers: "ready to implement", "should I proceed", "is this ready", "confidence check", "confidence gate", "준비 됐어", "確信度チェック", "実装着手", "ywc-confidence-gate". Do not use for completion veri...

(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, for the full delivery lifecycle of merging an already-completed branch (use ywc-finish-branch), or for handling existing PR review comments (use ywc-handle-pr-reviews).

(ywc) Use when a bug, test failure, build failure, or unexpected behavior appears, before proposing or applying a fix. Forces root-cause identification via 4-phase investigation, blocks symptom patching, and questions architecture after 3+ failed fixes. Triggers: "디버그", "버그", "이상해", "왜 안돼", "원인 찾아줘", "debug", "find the bug", "root cause", "what's wrong", "デバッグ", "原因不明", "通らない", "落ちる", "おかしい", "ywc-debug-rootcause". Do not use for implementation drafting (use ywc-code-gen), post-hoc incident p...

(ywc) Use when an existing frontend surface looks generic or "AI-made" and needs distinctive visual-design renewal, or an AI-slop audit (gradient text, cyan-on-dark, uniform card grids) before shipping. Triggers: "design renew", "de-slop this UI", "make it look less AI-generated", "AI slop check", "디자인 리뉴얼", "디자인이 너무 평범해", "AI 슬롭", "デザインリニューアル", "AIっぽいデザインを直して". Do not use for usability/accessibility/UX review (use ywc-ui-ux-review), new UI from scratch (use frontend-design/impeccable), backe...

(ywc) Use when parallel Git worktrees each run their own Docker stack and collide on host ports ("port is already allocated") — derives a deterministic per-worktree host-port block + COMPOSE_PROJECT_NAME, tears down only that worktree's stack, and audits stale stacks. Delegated from `ywc-parallel-executor` (audit/setup/teardown). Triggers: "docker port 격리", "compose 포트 충돌", "ywc-docker-isolate", "docker isolate", "worktree docker stack", "Docker ポート分離". Do not use for projects without Docker/...

(ywc) Use when designing an automated E2E test strategy, setting up Playwright from scratch, auditing E2E coverage gaps, or generating Playwright test code for a critical user flow with CI integration. Triggers: \"E2E 테스트 전략\", \"e2e test strategy\", \"Playwright 설정\", \"playwright setup\", \"critical path 자동화\", \"E2E 테스트 작성\", \"e2e coverage 점검\", \"E2Eテスト戦略\", \"Playwright設定\", \"テスト自動化\". Do not use for manual verification test sheets (use ywc-gen-testcase), unit or integration tests at t...

(ywc) Use when delivering a single completed feature branch to the base branch — covers mark-PR-ready, CI wait + bot review polling, merge (PR/local), post-merge verification, Mark Task Complete bookkeeping, and local branch cleanup. Triggers: "finish branch", "deliver branch", "ywc-finish-branch", "merge feature branch", "branch 마무리", "ブランチ完了", "deliver task", "task 마감". Do not use for branch creation (handled by upstream executor), worktree management (caller of `ywc-parallel-executor` hand...

(ywc) Use when generating a manual verification testsheet (developer + QA gate) from a PR, task directory, git range, or diff, with prose in Korean, Japanese, English, Chinese, or Spanish. Triggers: "generate test case", "testsheet", "QA checklist", "PR 테스트 케이스", "테스트시트", "テストシート作って", "manual test", "release 범위 test", "수기 검증", "生成测试用例", "测试表", "generar caso de prueba", "hoja de pruebas". Do not use for writing automated unit/integration tests, code-level test generation, or in-IDE test scaffo...

(ywc) Use when handling an open PR's review feedback — addressing comments, replying to review threads, and leaving the PR mergeable by clearing CI failures and base-branch conflicts too. Triggers: "handle PR reviews", "fix PR CI", "resolve PR conflict", "PR CI 고쳐줘", "PR conflict 해결", "리뷰 대응", "レビュー対応". Do not use for creating a new PR (use ywc-create-pr), reviewing code yourself (use ywc-impl-review), verify-before-agreeing on feedback (use ywc-receive-review), storing durable review learnin...

(ywc) Use when authoring or modifying Infrastructure-as-Code from a design — Terraform for AWS/GCP/Azure/Kubernetes (K8s/Helm via Terraform kubernetes/helm providers, never raw manifests or a second IaC tool), including validate/plan verification and a blast-radius summary. Triggers: "IaC 작성", "terraform 작성", "인프라 코드", "k8s 매니페스트", "write terraform", "author IaC", "provision infrastructure", "IaC を書いて", "ywc-iac-author". Do not use for app logic (ywc-backend-coder), topology design (ywc-infra...

(ywc) Use when implementation is complete and before creating a PR, to validate code against the spec or run a comprehensive quality review. Triggers: "구현 검증", "impl review", "implementation review", "사양 적합성", "코드 리뷰", "구현 리뷰", "PR 전 검증", "check my implementation", "実装レビュー". Do not use for active code generation, spec-only review (use ywc-spec-validate), product/business review (use ywc-product-review), durable review-preference capture (use ywc-review-learnings), or a security-only audit of ...

(ywc) Use when a production incident has occurred and you need a structured postmortem: timeline reconstruction, root cause analysis (5 Whys), impact assessment, prevention action items, and an optional sanitized client-facing report. Trigger phrases: "장애 회고", "장애 원인 분석", "사고 회고록", "postmortem", "incident report", "outage report", "ポストモーテム", "障害振り返り", "ywc-incident-postmortem" Do not use for security scanning before an incident (ywc-security-audit), code review unrelated to an incident (ywc...

(ywc) Use when designing cloud/infrastructure architecture before writing IaC — requirements gathering, provider selection, network/compute/ storage/IAM topology, and a reliability/cost/security pre-check producing infra-design.md for ywc-iac-author. Triggers: "인프라 설계", "클라우드 아키텍처", "aws 구성 설계", "네트워크 토폴로지", "infra design", "cloud architecture", "design the infrastructure", "インフラ設計", "クラウド構成", "ywc-infra-design". Do not use for writing IaC (use ywc-iac-author), folder layout (use ywc-project-...

(ywc) Use when improving existing infrastructure: cost right-sizing, removing unused resources, reserved/spot adoption, drift detection & remediation, and reliability hardening for AWS/GCP/Azure/K8s — the safe change-loop equivalent of refactor-clean for infra. Triggers: "인프라 개선", "비용 최적화", "right-sizing", "drift 점검", "미사용 리소스 정리", "cost optimization", "optimize infrastructure", "terraform drift", "インフラ最適化", "ywc-infra-optimize". Do not use for greenfield infrastructure design (use ywc-infra-...

(ywc) Use when reviewing IaC / cloud configuration for misconfiguration, least-privilege, cost, and reliability before applying — security groups, IAM, public exposure, secrets in state, cost right-sizing, and SPOF/backup gaps across AWS/GCP/Azure/K8s Terraform. Fans out to security/cost/reliability lenses with severity-rated findings. Triggers: "인프라 리뷰", "terraform 검토", "iam 과권한", "보안 그룹 점검", "infra review", "review my terraform", "インフラレビュー", "ywc-infra-review". Do not use for app-code auth/...

(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 entering an unfamiliar repository for the first time to generate a starter CLAUDE.md from detected conventions or produce an architecture/convention briefing for a new joiner, emitting a printed Onboarding Guide plus Starter CLAUDE.md. Triggers: "onboard me", "walk me through this repo", "generate CLAUDE.md", "이 repo 처음이야", "리포 분석해줘", "コードベースを案内して", "ywc-onboard-repo". Do not use for creating a brand-new repo from scratch (use ywc-project-scaffold), CodeTour .tour walkthroughs,...

(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, standalone git worktree management — create / audit / prune without task execution (use ywc-worktr...

(ywc) Use when the user has a rough feature idea or change request and needs a concrete plan before implementation, including scale assessment and routing to the right downstream skill. Triggers: "plan 세워줘", "어떻게 진행할지", "plan this", "make a plan", "プラン作成", "計画立てて", "ywc-plan", "task 만들기 전 plan". Do not use for spec validation (use ywc-spec-validate), task decomposition (use ywc-task-generator), product reasoning (use ywc-product-review), pre-intent clarification (use ywc-brainstorm), spec aut...

(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", "プロダクトレビュー", "サービス改善", "ywc-product-review". 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 the user wants to generate or add project docs/ documentation in Korean, Japanese, English, Chinese, or Spanish (Architecture, Product, Plans, operational guides). Triggers: '문서 작성', 'write a doc', 'add to docs/', 'English docs', '中文文档', 'ドキュメント作成', '文書作成', 'documentación del proyecto'. Do not use for code comments, README at repo root, skill authoring (use ywc-skill-author), domain glossary (use ywc-ubiquitous-language), changelog/release notes (use ywc-changelog-release-notes...

(ywc) Use when capturing, reading, or curating a project's durable Mission / North-Star, measurable Success Criteria, and Out-of-Scope non-goals — the "why this project exists" memory that frames every planning session. Triggers: "프로젝트 미션 정리", "이 프로젝트 미션 기억해둬", "north star 정의", "success criteria 정리", "プロジェクトミッション", "project mission", "mission persistence". Do not use for domain vocabulary (use ywc-ubiquitous-language), review preferences (use ywc-review-learnings), a single feature's plan (us...

(ywc) Use when the user wants to scaffold a new project structure, design a folder layout, or organize files for a specific tech stack. Triggers: 'project structure', 'scaffold a new project', 'folder layout', 'project skeleton', '프로젝트 구조', 'プロジェクト構成', a language/framework combined with 'structure' or 'scaffold', or reviewing this skill's `references/<language>.md` (e.g. 'review go.md', 'refresh the python reference'). Do not use for modifying an existing structure, generating individual file...

(ywc) Use when receiving code-review feedback (human, CodeRabbit, Codex, Claude, or ChatGPT review) before responding. Verify before agreeing; block performative agreement ("You're absolutely right!"); clarify unclear items before partial implementation. Triggers: "리뷰 받았어", "리뷰 코멘트", "리뷰 지적이 맞는지 확인", "PR comment 처리", "review feedback", "is this review comment correct", "レビュー受信", "レビュー指摘の妥当性確認", "コメント返信", "ywc-receive-review". Do not use for performing a code review yourself (ywc-impl-review),...

(ywc) Use when removing dead code (unused functions / exports / files / dependencies / imports), consolidating near-duplicate utilities, or running a scheduled hygiene pass on a codebase. Triggers: "dead code 제거", "knip / depcheck / ts-prune 돌려줘", "refactor clean", "dead code cleanup", "remove unused exports", "デッドコード削除", "ywc-refactor-clean". Do not use for active feature implementation on the same branch (finish the feature first), behavior-changing refactors (use ywc-tdd-ritual + ywc-code-...

(ywc) Use when working on a release PR (e.g., develop→main) and the user wants to generate the merged PR list grouped by author. Triggers: "release PR list", "릴리즈 PR 정리", "릴리스 PR 리스트", "release pr 정리", "リリースPR一覧", "ywc-release-pr-list", or any request to build a release-PR description from merged PR numbers. Do not use for normal feature PR creation (use ywc-create-pr), handling PR review comments (use ywc-handle-pr-reviews), or CHANGELOG / release-note generation from git history or merged P...

(ywc) Use when capturing, reading, or curating a project's accumulated code-review learnings — durable review preferences (what, why, polarity) that sharpen future reviews (CodeRabbit's "learnings" pattern, runtime-agnostic). Triggers: "리뷰 학습 누적", "이 지적 학습해둬", "이건 false positive 야 학습해줘", "review learnings", "レビュー学習", "remember this review preference", "accumulate review feedback". Do not use for implementation review itself (ywc-impl-review), open PR comment handling (ywc-handle-pr-reviews), ...

(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 (branch → implement → commit → PR → CI → merge → cleanup). 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), an autonomous goal-to-code...

(ywc) Use when the user wants to set or inspect the persistent output language for ywc-generated documents, PRs, and commit messages so they stop passing --lang on every call. Triggers: "set output language", "set project language", "ywc-setup-language", "언어 설정", "언어 정책 설정", "言語設定", "出力言語を設定". Do not use for a one-off per-call override (pass --lang to the consuming skill instead), the session/chat language (never config-governed), editing consumer skills, or defining the resolution rules them...

(ywc) Use when creating a new ywc-* skill, restructuring an existing one's frontmatter/body sections/references, or auditing existing ywc-* skills against the canonical rule set. Triggers: "ywc skill 생성", "create ywc skill", "ywc skill 만들어줘", "ywc skill 개선", "new ywc skill", "ywc skill upgrade", "ywcスキル作成", "ywc skill audit", "ywc skill 룰 점검". Do not use for editing skill content during normal task execution, for non-ywc-* skills, or for renaming/moving skills (use `git mv` directly).

(ywc) Use when a spec from ywc-plan still has Critical/Warning findings and you want it auto-driven to ywc-spec-validate DONE — looping ywc-plan --update-spec and ywc-spec-validate until ready for ywc-task-generator, then stopping at the handoff. Triggers: "spec 수렴", "spec ready loop", "ywc-spec-ready", "사양 수렴 자동화", "spec を DONE まで". Do not use for the full goal-to-code pipeline (use ywc-agentic), a one-shot spec review without re-planning (use ywc-spec-validate), initial spec authoring (use ...

(ywc) Use when a specification has been written and before task decomposition, and the user wants to validate spec completeness, consistency, feasibility, or readiness for implementation. 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.

(ywc) Use when creating or updating a project specification (사양서) in docs/specification/, including task-range and PR-based incremental updates. Triggers: "사양서 작성", "spec 작성", "사양서 업데이트", "task 로 사양서 갱신", "PR 로 사양서 갱신", "write spec", "update spec from task range", "update spec from PRs", "仕様書作成", "スペック作成", "仕様書更新", "タスク範囲から仕様書更新", "PRから仕様書更新", "编写规范文档", "中文规范", "escribir especificación", "ywc-spec-writer". Do not use for spec quality review (use ywc-spec-validate), task decomposition from a f...

(ywc) Use when converting a specification into implementation tasks. Task documents can be written in Korean, Japanese, English, Chinese, or Spanish. Triggers: "task 생성", "タスク生成", "spec to tasks", "task breakdown", "작업 분해", "仕様からタスク生成", "implementation tasks", "스펙 분해", "从规范生成任务", "中文任务", "generar tareas", "tareas en español", 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 any new feature, bug fix, or behavior change, before writing production code. Enforces RED → GREEN → REFACTOR with a mandatory watch-it-fail step; forbids test-after patterns. Triggers: "TDD", "test first", "test-first", "RED-GREEN", "regression test", "테스트 먼저", "회귀 테스트", "テスト先行", "テストファースト", "ywc-tdd-ritual", "ywc-code-gen --tdd". Do not use for opted-out throwaway prototypes, debugging an existing test failure (use ywc-debug-rootcause), generated/config files, or...

(ywc) Use when comparing libraries, investigating implementation approaches, evaluating technology options, or gathering best practices before writing specifications. Triggers: "기술 조사", "라이브러리 비교", "research", "investigate", "compare options", "어떤 걸 쓸까", "best way to implement", "技術調査", "ライブラリ比較", "ywc-tech-research". Do not use for spec writing (output goes to ywc-spec-validate), code generation (use ywc-code-gen), or simple documentation lookup that does not require comparison/evaluation.

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

(ywc) Use when the user wants a UI/UX review combining static code analysis with live UI exploration (Chrome DevTools MCP) covering information architecture, 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), aesthetic / visual de-slop renewal...

(ywc) Use when about to claim that work is complete, tests pass, the build succeeds, a bug is fixed, requirements are met, or a subagent finishes — and before commit, PR creation, executor handoff, or task transition. Triggers: "완료", "다 됐어", "끝났어", "verify done", "검증해줘", "done", "finished", "ready to merge", "完了", "終わった", "確認お願いします", "ywc-verify-done". Do not use for ongoing implementation drafting (use ywc-code-gen), root-cause debugging (use ywc-debug-rootcause), pre-implementation confiden...