mit einem Klick
claude-overlay
claude-overlay enthält 6 gesammelte Skills von chlee1001, mit Repository-Berufsabdeckung und Skill-Detailseiten auf SkillsMP.
Skills in diesem Repository
Re-apply and maintain local OMC (oh-my-claudecode) plugin customizations after an update — a guided, step-by-step workflow that first detects what changed upstream (via the marketplace git clone of Yeachan-Heo/oh-my-claudecode), then 3-way merges each patch onto the new version, preserving upstream changes and surfacing conflicts. Make sure to use this skill whenever OMC was updated, upgraded, or reinstalled; when a patched OMC agent or skill (git-master, planner, executor, team, etc.) looks reverted or behaves like the stock version; when you want to know what an OMC update changed in files you have customized; or to verify your local OMC patches are still applied. Run it from the claude-overlay folder after any oh-my-claudecode version bump.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
claude-overlay 재흡수 플로우 — 우리가 외부에서 흡수한 것(design-discovery←insane-design 등, completion-gate←Superpowers, korean-writing←humanize-korean)의 원본이 업데이트됐는지 감지하고, OMC architect deep-analysis로 triage해서 우리 번들 자산에 다시 흡수한다. OMC 업데이트(apply.sh)와 독립된 사이드 플로우. claude-overlay 폴더에서 실행. Triggers: "재흡수", "reabsorb", "흡수물 드리프트", "원본 업데이트 반영", "reabsorb 돌려줘", "insane-design 업데이트 반영".
PLAN→BUILD 사이의 빠진 페이즈 — 확정된 .omc/plans/*.md(+open-questions.md)를 받아 근거 기반 디자인 방향을 확정하는 디스커버리 단계. 앱 코드는 건드리지 않고 탐색 아티팩트만 생성한다. 타깃 프로젝트에 디자인 가이드가 있으면(brownfield) 구조·인터랙션·느낌만 가져오고 값(hex/폰트/spacing/컴포넌트)은 기존 시스템에서 와야 하므로 reconciliation으로 매핑하고 plan delta를 뱉는다. 없으면(greenfield) 레퍼런스 값을 그대로 써서 design.md를 만든다. UI 표면이 있는 플랜에만 작동(백엔드/CLI 전용은 skip). Manual: /design-discovery <plan-path>. Triggers: "기획서 디자인 뽑아줘", "플랜 기반 UI 탐색", "디자인 디스커버리", "design discovery", "plan to UI", "기획서로 디자인 방향".
Strict TDD (the IRON LAW) for the current task. Use ONLY when the user explicitly asks for rigorous/strict TDD — triggers: '엄격 tdd', '엄격한 tdd', 'strict tdd', 'rigorous tdd', 'IRON LAW', or /strict-tdd. Establishes no-production-code-without-a-failing-test discipline directly in this session, superseding the softer default 'tdd' reminder. Do NOT trigger on a bare 'tdd' mention (that stays soft).
Generate a human-review companion for a finalized work plan. Use right after a work plan is saved (e.g. to .omc/plans/*.md by planner/ralplan/plan), or when the user wants a jargon-free, no-abbreviation prose version of a plan for human review. Produces <plan>.readable.md next to the machine plan without modifying the original.