cc-frontend-skills MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Opinionated style guidance to avoid default AI aesthetics
References editorial / print / brutalist / minimalist design languages
Japanese-authored prompts — but works in any language
Focus on typography, whitespace, and grid rigor
Framework-agnostic (React, Vue, Svelte, plain HTML)

라이브 데모

실제 사용 모습

cc-frontend-skill.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "cc-frontend-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/oikon48/cc-frontend-skills",
        "~/.claude/skills/cc-frontend-skills"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "cc-frontend-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/oikon48/cc-frontend-skills",
        "~/.claude/skills/cc-frontend-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "cc-frontend-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/oikon48/cc-frontend-skills",
        "~/.claude/skills/cc-frontend-skills"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "cc-frontend-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/oikon48/cc-frontend-skills",
        "~/.claude/skills/cc-frontend-skills"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "cc-frontend-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/oikon48/cc-frontend-skills",
        "~/.claude/skills/cc-frontend-skills"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "cc-frontend-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/oikon48/cc-frontend-skills",
          "~/.claude/skills/cc-frontend-skills"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add cc-frontend-skill -- git clone https://github.com/oikon48/cc-frontend-skills ~/.claude/skills/cc-frontend-skills

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: cc-frontend-skills

Build a landing page with visual identity, not AI sludge

👤 Indie devs, founders who hate how their AI-generated landing page looks ⏱ ~60 min intermediate

언제 쓸까: You asked Claude for a landing page and got yet another purple-gradient hero with rounded cards.

사전 조건

Skill installed — git clone https://github.com/oikon48/cc-frontend-skills ~/.claude/skills/cc-frontend-skills
A reference style in mind — Name one — editorial, swiss, brutalist, y2k, warm-monochrome, anything

흐름

Name the aesthetic

Use cc-frontend-skills. Build a landing page for my book in the style of mid-century Penguin paperback covers — restrained type, one accent color, generous whitespace.✓ 복사됨

→ Layout draft with specific type choices, not a shadcn hero
Iterate on grid and type

Tighten the typographic scale to a 1.333 modular scale; use Charter or similar serif.✓ 복사됨

→ Concrete CSS with named fonts, not 'sans-serif'
Strip AI tells

Audit for AI-design tells: emoji headers, excessive shadow-lg, gradient text, identical card layouts. Kill them.✓ 복사됨

→ Diff removing the usual suspects

결과: A landing page that looks like someone cared.

함정

Claude reverts to defaults after a few iterations — Pin the style ref in each follow-up prompt — don't rely on context to carry it

함께 쓰기: filesystem

Refactor a generic dashboard into something that feels designed

👤 Teams shipping internal tools that everyone silently hates ⏱ ~90 min intermediate

언제 쓸까: Your dashboard works but looks like every other shadcn-based app.

흐름

Diagnose

Use cc-frontend-skills. Look at /app/dashboard. What are the specific AI-design tells here?✓ 복사됨

→ Concrete list: 'everything is lg-rounded, shadows on every card, gradient CTA, grid is always 3-col'
Propose an alternative

Suggest an aesthetic direction anchored to one data-dense design reference (Bloomberg terminal, Figma's inspector panel).✓ 복사됨

→ Named references with concrete applications
Apply incrementally

Start with typography only — fix hierarchy without touching layout.✓ 복사됨

→ Diff changing font-size, letter-spacing, weight only

결과: A dashboard with opinions.

함정

Over-designing and breaking accessibility — Keep AA contrast; visual identity doesn't require light-gray-on-white

함께 쓰기: chrome-devtools

Give your component library a consistent visual voice

👤 Design-system maintainers ⏱ ~60 min advanced

언제 쓸까: Your buttons, cards, and inputs were each generated independently and now clash.

흐름

Inventory

Use cc-frontend-skills. Review components/ and identify inconsistencies in border-radius, shadow, spacing.✓ 복사됨

→ Variance table per token
Propose tokens

Propose a consolidated design token set with one radius scale, one shadow scale, one spacing ramp.✓ 복사됨

→ Token JSON / Tailwind config

결과: A token set that makes the library feel like one thing.

조합

다른 MCP와 조합해 10배 효율

cc-frontend-skill + chrome-devtools

Live-tweak styles in the browser and feed changes back to source

Open the page, tweak type scale in devtools until it feels right, then apply the diff to CSS.✓ 복사됨

cc-frontend-skill + filesystem

Apply design-system updates across a monorepo

Update all button variants in packages/ui/ to the new token set.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
style_audit	component or page	Diagnosing generic AI aesthetic
aesthetic_brief	named reference style	Kicking off a new page with direction
typography_tune	current scale	Fixing type hierarchy

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Moderate
금액: Free
팁: Do one page at a time; full app refactors blow up the context.

보안

권한, 시크릿, 파급범위

자격 증명 저장: None

데이터 외부 송신: None — local skill

문제 해결

자주 발생하는 오류와 해결

Claude keeps suggesting shadcn/Tailwind defaults

Be explicit: 'do not use shadcn defaults; use the aesthetic brief from cc-frontend-skills'

Generated code uses unnamed fonts

Prompt-specify font stacks; Claude often leaves them generic

Skill docs are in Japanese and I can't read them

Ask Claude to translate SKILL.md; the skill works regardless of prompt language

대안

cc-frontend-skills 다른 것과 비교

대안	언제 쓰나	단점/장점
apple-hig-designer-skill	Specifically targeting iOS / macOS HIG aesthetic	Platform-specific
Tailwind UI / shadcn blocks	You want speed over identity	Everything looks the same

cc-frontend-skills