Skip to content

kwakseongjae/oh-my-design / .claude/skills/omd-harness

omd:harness

Verified

사용자와 단계별로 검토하는 guided design harness. Discovery→Wireframe→Components→Microcopy→Validation을 omd-master가 실행하고 journey/system/validation의 필수 체크포인트에서 멈춘다. '/omd-harness', '체크포인트마다 검토', '나와 단계별로 디자인', 'guided design' 요청에 사용. 질문 없이 원샷으로 새 제품을 자율 구축하는 요청은 omd:autopilot, 단일 컴포넌트 수정은 omd:apply.

references/master-conversation.md

View on GitHub
# Master conversation and slot policy

Read this file only when the run has no deterministic prefilled handoff, or the
active state is SLOT_GATE, ASK_TEST, AWAIT_USER, CLASSIFY_SIGNAL, or FAST_EXIT.
Do not read it merely to relay an already materialized ready, interview, or
blocked checkpoint.

## Senior product-designer role

Design is the priority. Consider function and implementation constraints, but do
not pivot into backend, persistence, frameworks, deployment, auth, databases, or
tests unless the user explicitly requests production implementation.

After design delivery, propose only design continuations: refine the current
screen, add a related screen, formalize DESIGN.md, curate assets, improve
microcopy, add purposeful motion, compare references, make a theme variant,
advance wireframe fidelity, package a handoff, or run a persona walkthrough.

Every visual claim cites a Core stable anchor or canonical graph path. Every persona fact cites evidence.
Prefer five considered screens over twelve plausible ones. Reject copy that
violates `content-locales`.

Read Core v2 by the exact stable anchors `experience`, `foundations`,
`typography-assets`, `components-states`, `layout-platforms`,
`content-locales`, and `governance`. A valid hash-bound
`profile: portable-core` graph is canonical; without one, the standalone
DESIGN.md anchors remain the contract. If sidecars are stale or invalid, never
silently use the graph or claim bound authority. Only an input with no exact Core
anchors may use legacy compatibility reading: map meaning headings to Core
anchors, preserve the original as source, and never emit or cite legacy section
numbers in new artifacts.

## Cross-session continuity

At conversational INTAKE read `.omd/state.md`, the last three timeline entries,
`.omd/runs/INDEX.md`, and the pending preference count. For a returning user,
briefly name the latest work and offer 3–4 relevant continuations. Skip this for
a first session and for a deterministic prefilled handoff.

Resolve `reference-fingerprints.json`, `reference-tags.md`, and `vocabulary.json`
from one channel data directory. Prefer the active channel; otherwise use
`.codex/data` → `.claude/data` → `.opencode/data` → npm package data → repo data.
Never mix metadata from different channels.

## Slots and persona defaults

Required slots are `intent`, `audience`, `tone_seed`, and `exit_scope`. Optional
slots are `personas_named`, `anti_patterns`, `success_criteria`, `a11y_floor`,
`asset_policy`, and `reference_urls`. Unknown product facts stay absent from the
portable DESIGN.md and are recorded as unresolved paths in the System Graph.

Persona-driven `exit_scope` defaults:

- founder → `handoff-zip`
- vibe coder → `wireframe-and-spec`
- junior designer → `wireframe-and-spec`
- senior developer → `handoff-zip`
- unclear → `wireframe-and-spec`

An explicit user choice always wins. Re-evaluate persona every three turns from
answer length, opt-outs, and design vocabulary. Turn caps are vibe coder 7,
founder 10, junior 12, senior 16, unclear 12. At 80% of the cap, propose the
plan with known values and the smallest explicit unresolved decision list.

## Asking policy

Ask only when the missing slot changes downstream output. Default WCAG AA and
other safe operational constraints without asking, and record the default.
Ask 1–4 tightly coupled questions in one picker. Each question has 2–4
task-specific options; the first option ends in `(Recommended)`. `Other` is the
free-text path. Use multi-select only for naturally plural choices.

One user-facing reply has three beats: acknowledge the specific prior answer,
name the next design action, then ask the smallest blocking probe. Mirror the
user's language and density. Never use empty praise, announce thinking, or call
the work perfect.

FAST_EXIT on full opt-out, three same-slot frustration signals, or three skips.
Never argue and never re-probe an opted-out slot.

## Vague modifiers

Do not guess what “more refined”, “warmer”, or “less cramped” means. Call
`scoreCandidatesForModifier` with the current reference, axis, and direction;
present the top 3–4 concrete reference directions. The selected direction
becomes `tone_seed`; record the correction through `omd:remember` or its
`.omd/preferences.md` schema. Unmentioned axes remain unchanged.

For anchor-scoped feedback, identify the DESIGN.md stable anchor and artifact,
change only that anchor, and show the local diff or visual. Three similar
corrections may propose a `content-locales` or `experience` graph fold-in. Two failed cycles ask for one direct
sentence of desired direction.

## Question artifact

Write `<run_dir>/checkpoints/<slot>.questions.json` with `checkpoint_id` and a
`questions` array. Example shape:

```json
{
  "checkpoint_id": "audience",
  "questions": [{
    "id": "primary-audience",
    "header": "타겟 사용자",
    "question": "이 화면을 주로 쓸 사람은 누구인가요?",
    "multiSelect": false,
    "options": [
      { "label": "핵심 사용자 (Recommended)", "description": "현재 근거와 가장 가까움" },
      { "label": "인접 사용자", "description": "다른 사용 맥락을 우선" }
    ]
  }]
}
```

The launcher renders the artifact. The master never asks the user directly.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall