** Claude Code, Cursor 및 MCP 클라이언트를 제공하는 MCP 서버는 Apple Human Interface Guidelines as Structured data** — real system color values, type Tilt, Liquid Glass constraints, SwiftUI mappings — 대신에 misread 또는 stale hex to hallucinate.

문제 모든 Apple dev (그리고 그들의 대리인) 지금 있다

WWDC25 Apple은 액체 유리를 발송하지 않았습니다. 조용히 ** 시스템 색상 팔레트를 복사 ** (HIG changelog, 6 월 9, 2025). systemBlue은 더 이상 없습니다. #0088FF입니다.

어떤 의미:

• ** 모든 LLM의 교육 데이터가 잘못됩니다. ** iOS 색상의 에이전트를 요청하고 정확히 pre-2025 팔레트를 해독합니다.
• ** HIG는 prose, 데이터가 아닙니다. ** Apple은 웹 페이지로 가이드 라인을 게시합니다. 에이전트는 수천 개의 토큰을 태칭 한 다음 여전히 숫자를 추측합니다.
• **Liquid Glass에는 아무도 한 곳에서 썼지 않습니다 ** - blur 예산, 퇴비 층 모자, 대조 측정 된 after blur, 필수 감소 투명성 fallback. 에이전트는 기본적으로 그들 모두를 위반.

looks plausible이 생성 된 SwiftUI를 검토하고 어디에나 하위 별입니다.

어떻게 hig-mcp 그것을 해결

hig-mcp — Apple HIG design tokens for AI coding agents

An MCP server that gives Claude Code, Cursor, and any MCP client the Apple Human Interface Guidelines as structured data — real system color values, the type ramp, Liquid Glass constraints, and SwiftUI mappings — instead of prose to misread or stale hex to hallucinate.

The problem every Apple dev (and their agent) has right now

At WWDC25 Apple didn’t just ship Liquid Glass — it quietly refreshed the system color palette (HIG changelog, June 9, 2025). systemBlue is not #007AFF anymore. It’s #0088FF.

Which means:

• Every LLM’s training data is wrong. Ask an agent for iOS colors and it confidently hardcodes the pre-2025 palette.
• The HIG is prose, not data. Apple publishes guidelines as web pages; an agent burns thousands of tokens fetching one, then still guesses the numbers.
• Liquid Glass has rules nobody wrote down in one place — blur budgets, compositing layer caps, contrast measured after blur, the mandatory Reduce Transparency fallback. Agents violate all of them by default.

You end up reviewing generated SwiftUI that looks plausible and is subtly off-spec everywhere.

How hig-mcp solves it

Curated, verified token files live inside the server — offline, deterministic, near-zero tokens — and prose is fetched live from sosumi.ai so guidance is never stale. Ask for color and you get the current post-WWDC25 spec table, not a 2023 memory.

How it works

Four tools over stdio (Python, the official mcp SDK 2.x). The structured half is plain JSON you own and extend (src/hig_mcp/data/); the prose half is delegated to sosumi.ai’s DocC-to-Markdown rendering rather than rebuilt. Every value is provenance-tagged:

• apple-system / apple-hig — Apple-published facts (system colors, type ramp, 44pt hit targets).
• wcag-aa — the 4.5:1 contrast rule.
• figma-effect / community-bestpractice — useful numbers Apple never published, flagged so you know to confirm.
• verify: true — beta-era API names that shift; confirm via hig_fetch or Xcode before shipping.

Each data file also carries a checked date in its _meta: the day its values were last compared with Apple’s live pages.

Honest data beats confident data.