ワンクリックでManusで任意のスキルを実行

coach

スター1

フォーク0

更新日2026年7月13日 10:13

Read the project's check history and tell the user what they keep getting wrong, what is improving, and what to study next. Skill, not taste — it never reads preferences. Use when the user asks how their design is trending, what mistakes repeat, or wants a review of accumulated findings. Triggers: 코치, 내가 뭘 반복해서 틀리지, 디자인 실력, 추세, coach, what do I keep getting wrong, design habits.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

3x-haust

3x-haust/oh-my-design

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

oh-my-design:coach

omd coach

The CLI computes; you interpret. It reads .omd/history.jsonl (every omd check run) and decisions.md, and reports recurring rules, trends, and overruled slop findings.

How to read it to the user

Lead with the pattern, not the list. "대비비 지적이 4런에 걸쳐 26건, -70% 개선 중" is data; "대비는 잡히기 시작했는데, 이제 위계 지적이 늘고 있다 — 다음 병목은 정보 구조다"가 코칭이다.
Honesty is enforced, honor it. Under four runs the tool refuses to claim a trend — do not invent one on top. A rule with no baseline prints "appeared", never a percentage; keep it that way in your prose.
Overrules are choices, not sins. SLOP-GRADIENT overruled twice with a brand reason is a decision holding steady. The same overrule with "it looked fine" is a habit worth naming.
End with one thing to observe, not ten. Pick the costliest recurring rule and give one concrete study: a reference to look at (oh-my-design:scout can fetch it measured) and what to notice there.

The boundary

Never mix skill with taste. "You keep missing contrast" has a right answer; "you prefer dense layouts" does not (professional designers agree at α = 0.248). Coach speaks only about the first kind, and never reads .omd/taste/.

このリポジトリの他の Skills

同じリポジトリ

figma

3x-haust/oh-my-design

Implement a Figma design end to end: pull the file, synthesize the design system, build each frame pixel-faithfully with an iterative diff loop, match responsive pairs, and ship with a fidelity report. Use when a figma.com link is present in the brief — the design decisions were already made in Figma; the job here is faithful implementation and systematization, not concept invention. Triggers: 피그마, figma link, 피그마 그대로 구현, any figma.com URL in the brief.

2026-07-131

humanize

3x-haust/oh-my-design

Rewrite text so it reads as if a person wrote it — strip AI prose tics (Korean and English), translation-ese, uniform rhythm, hedging stacks, and self-negating meta-copy — without changing a single fact. Works on any text: page copy, blog posts, READMEs, marketing lines. Also used by oh-my-design:ultradesign for every word that ships. Triggers: humanize, 사람같이, 사람처럼 써, AI티 빼줘, 자연스럽게 바꿔, 글 다듬어, make it sound human, de-AI, rewrite naturally.

2026-07-131

scout

3x-haust/oh-my-design

Build a measured reference board without designing anything: whole pages for feel, tight selectors for component anatomy, typography studies, motion studies, image refs for the unrenderable. Use when the user asks for references, inspiration, benchmarks, or "how do good sites do X" — standalone, before or without a build. Minimum 18 captures, target 25. Triggers: 레퍼런스 찾아줘, 레퍼런스 수집, 참고 사이트, 벤치마킹, find references, inspiration board, how do other sites do.

2026-07-131

ultradesign

3x-haust/oh-my-design

Design and build an interface the way a designer does — interrogate the brief, commit to a concept, study real references and extract why they work, commit to one structure, look at what actually rendered, and let what you see rewrite the problem. Produces work with a position, not the average of every landing page ever scraped. Runs end to end without asking the user to approve anything. Reference URLs included in the brief are captured first and treated as first-class user-provided references. Use when asked to design, build, redesign, or lay out any interface, page, component, app, blog, dashboard, or landing page. Triggers: ultradesign, 울트라디자인, 디자인해줘, 만들어줘, UI, 화면, 리디자인, 페이지, 랜딩, 블로그, 대시보드, landing page, redesign, make it look good.

2026-07-131

omd-figma

3x-haust/oh-my-design

2026-07-131

omd-ultradesign

3x-haust/oh-my-design

2026-07-131

name

coach

description

oh-my-design:coach

omd coach

The CLI computes; you interpret. It reads .omd/history.jsonl (every omd check run) and decisions.md, and reports recurring rules, trends, and overruled slop findings.

How to read it to the user

Lead with the pattern, not the list. "대비비 지적이 4런에 걸쳐 26건, -70% 개선 중" is data; "대비는 잡히기 시작했는데, 이제 위계 지적이 늘고 있다 — 다음 병목은 정보 구조다"가 코칭이다.
Honesty is enforced, honor it. Under four runs the tool refuses to claim a trend — do not invent one on top. A rule with no baseline prints "appeared", never a percentage; keep it that way in your prose.
Overrules are choices, not sins. SLOP-GRADIENT overruled twice with a brand reason is a decision holding steady. The same overrule with "it looked fine" is a habit worth naming.
End with one thing to observe, not ten. Pick the costliest recurring rule and give one concrete study: a reference to look at (oh-my-design:scout can fetch it measured) and what to notice there.