cc-frontend-skills MCP — Use Cases, Install & Live Demo

Why use it

Key features

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)

Live Demo

What it looks like in practice

cc-frontend-skill.replay ▶ ready

0/0

Install

Pick your client

~/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
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.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 uses the same mcpServers schema as Claude Desktop. Project config wins over global.

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
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "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
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.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 uses an array of server objects rather than a map.

~/.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"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

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

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use 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

When to use: You asked Claude for a landing page and got yet another purple-gradient hero with rounded cards.

Prerequisites

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

Flow

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.✓ Copied

→ 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.✓ Copied

→ 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.✓ Copied

→ Diff removing the usual suspects

Outcome: A landing page that looks like someone cared.

Pitfalls

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

Combine with: filesystem

Refactor a generic dashboard into something that feels designed

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

When to use: Your dashboard works but looks like every other shadcn-based app.

Flow

Diagnose

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

→ 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).✓ Copied

→ Named references with concrete applications
Apply incrementally

Start with typography only — fix hierarchy without touching layout.✓ Copied

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

Outcome: A dashboard with opinions.

Pitfalls

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

Combine with: chrome-devtools

Give your component library a consistent visual voice

👤 Design-system maintainers ⏱ ~60 min advanced

When to use: Your buttons, cards, and inputs were each generated independently and now clash.

Flow

Inventory

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

→ Variance table per token
Propose tokens

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

→ Token JSON / Tailwind config

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

Combinations

Pair with other MCPs for X10 leverage

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.✓ Copied

cc-frontend-skill + filesystem

Apply design-system updates across a monorepo

Update all button variants in packages/ui/ to the new token set.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
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

Cost & Limits

What this costs to run

API quota: None
Tokens per call: Moderate
Monetary: Free
Tip: Do one page at a time; full app refactors blow up the context.

Security

Permissions, secrets, blast radius

Credential storage: None

Data egress: None — local skill

Troubleshooting

Common errors and fixes

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

Alternatives

cc-frontend-skills vs others

Alternative	When to use it instead	Tradeoff
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

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills