/ Annuaire / Playground / cc-frontend-skills
● Communauté oikon48 ⚡ Instantané

cc-frontend-skills

par oikon48 · oikon48/cc-frontend-skills

Claude Code plugin for frontend UIs that don't look like every other ChatGPT-generated page — escape the purple-gradient-and-rounded-corners aesthetic.

A Japanese-authored Claude Code skill for building frontend UIs with deliberate visual identity. Steers Claude away from the default 'AI design language' (generic gradients, same card layouts, shadcn clone) and toward choices that look intentional — typography, grids, color systems rooted in real design references.

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

cc-frontend-skill.replay ▶ prêt
0/0

Installer

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

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.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 utilise un tableau d'objets serveur plutôt qu'une 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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : 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

Quand l'utiliser : You asked Claude for a landing page and got yet another purple-gradient hero with rounded cards.

Prérequis
  • 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
Déroulement
  1. 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.✓ Copié
    → Layout draft with specific type choices, not a shadcn hero
  2. Iterate on grid and type
    Tighten the typographic scale to a 1.333 modular scale; use Charter or similar serif.✓ Copié
    → Concrete CSS with named fonts, not 'sans-serif'
  3. Strip AI tells
    Audit for AI-design tells: emoji headers, excessive shadow-lg, gradient text, identical card layouts. Kill them.✓ Copié
    → Diff removing the usual suspects

Résultat : A landing page that looks like someone cared.

Pièges
  • 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
Combiner avec : filesystem

Refactor a generic dashboard into something that feels designed

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

Quand l'utiliser : Your dashboard works but looks like every other shadcn-based app.

Déroulement
  1. Diagnose
    Use cc-frontend-skills. Look at /app/dashboard. What are the specific AI-design tells here?✓ Copié
    → Concrete list: 'everything is lg-rounded, shadows on every card, gradient CTA, grid is always 3-col'
  2. Propose an alternative
    Suggest an aesthetic direction anchored to one data-dense design reference (Bloomberg terminal, Figma's inspector panel).✓ Copié
    → Named references with concrete applications
  3. Apply incrementally
    Start with typography only — fix hierarchy without touching layout.✓ Copié
    → Diff changing font-size, letter-spacing, weight only

Résultat : A dashboard with opinions.

Pièges
  • Over-designing and breaking accessibility — Keep AA contrast; visual identity doesn't require light-gray-on-white
Combiner avec : chrome-devtools

Give your component library a consistent visual voice

👤 Design-system maintainers ⏱ ~60 min advanced

Quand l'utiliser : Your buttons, cards, and inputs were each generated independently and now clash.

Déroulement
  1. Inventory
    Use cc-frontend-skills. Review components/ and identify inconsistencies in border-radius, shadow, spacing.✓ Copié
    → Variance table per token
  2. Propose tokens
    Propose a consolidated design token set with one radius scale, one shadow scale, one spacing ramp.✓ Copié
    → Token JSON / Tailwind config

Résultat : A token set that makes the library feel like one thing.

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié
cc-frontend-skill + filesystem

Apply design-system updates across a monorepo

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

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
style_audit component or page Diagnosing generic AI aesthetic 0
aesthetic_brief named reference style Kicking off a new page with direction 0
typography_tune current scale Fixing type hierarchy 0

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
Moderate
Monétaire
Free
Astuce
Do one page at a time; full app refactors blow up the context.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : None
Sortie de données : None — local skill

Dépannage

Erreurs courantes et correctifs

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 autres

AlternativeQuand l'utiliserCompromis
apple-hig-designer-skillSpecifically targeting iOS / macOS HIG aestheticPlatform-specific
Tailwind UI / shadcn blocksYou want speed over identityEverything looks the same

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills