{"slug": "claude-skills-that-fix-claude-s-ugly-ui", "title": "Claude Skills That Fix Claude's Ugly UI", "summary": "Anthropic ships an official `frontend-design` Skill for Claude Code that gives Claude specific guidance on typography, color, layout, copy and visual direction, and instructs it to plan, review, build and critique a frontend interface. The Skill installs via `/plugin install frontend-design@claude-plugins-official`, or standalone through Vercel's Skills CLI with `npx skills add anthropics/skills --skill frontend-design -a claude-code`, which requires Node.js 22.20 or later. The walkthrough pairs the Skill with a detailed product brief — for a fictional API monitoring platform called Monitorly — to steer Claude away from generic purple gradients and identical cards toward a specified design system.", "body_md": "Ask Claude to build a landing page and there's a good chance you'll get the same familiar design: a centered hero, purple gradient, three rounded cards, and a big \"Get Started\" button.\n\nIt works, but it doesn't exactly look designed.\n\nYou can keep telling Claude to change the font, try another color palette, or make the layout more interesting. But repeating those instructions in every conversation gets old.\n\nThere's a better way. Anthropic has an official `frontend-design` Skill that gives Claude more specific design instructions. You can also create your own Skills to make it follow your preferred fonts, colors, layouts, and component styles.\n\nThis walkthrough focuses on Claude Code. Let's install the Skill, build a custom design system, and make Claude review its own work.\n\n## 1. Install the frontend-design Skill\n\nStart with Anthropic's official `frontend-design` plugin. You don't need to write anything yourself.\n\nOpen your project directory and start Claude Code:\n\n```\nclaude\n```\n\nThen run this command inside Claude Code:\n\n```\n/plugin install frontend-design@claude-plugins-official\n```\n\nClaude Code will open the plugin details. Review the information and choose where you want to install it:\n\n- User: available across your projects.\n- Project: available to everyone working on the repository.\n- Local: available only to you in that project.\n\nThat's the installation part done.\n\nIf Claude Code says the marketplace can't be found, add it manually:\n\n```\n/plugin marketplace add anthropics/claude-plugins-official\n```\n\nThen run the install command again.\n\n### Try the Skill\n\nOnce installed, type:\n\n```\n/frontend-design:frontend-design\n```\n\nYou can also let Claude select it automatically when you ask it to build or improve a frontend interface.\n\nThe Skill gives Claude guidance about typography, color, layout, copy, and visual direction. It also asks Claude to plan the design, review that plan, build the interface, and critique the result.\n\nYou can read its actual instructions in the [official frontend-design SKILL.md](https://github.com/anthropics/claude-plugins-official/blob/main/plugins/frontend-design/skills/frontend-design/SKILL.md).\n\n### Alternative: Install it using the Skills CLI\n\nYou can also install the standalone Skill through Vercel's Skills CLI.\n\nThis method requires Node.js 22.20 or later.\n\nFrom your project directory, run:\n\n```\nnpx skills add anthropics/skills --skill frontend-design -a claude-code\n```\n\nThis installs the standalone Skill from Anthropic's Skills repository for Claude Code rather than the complete marketplace plugin.\n\nBoth methods work. Choose one; you don't need to install both.\n\n## 2. Give Claude a better prompt\n\nInstalling the Skill is only half the job. Your prompt still matters.\n\nInstead of asking:\n\n```\nBuild me a modern SaaS landing page.\n```\n\nGive Claude an actual product brief.\n\nFor this example, let's build a landing page for a fictional API monitoring platform called Monitorly.\n\nCopy this prompt:\n\n```\nBuild a responsive landing page for Monitorly, an API\nmonitoring platform for small engineering teams.\n\nThe product helps developers monitor API uptime,\ntrack response times, and investigate incidents.\n\nVisual direction:\n- Light technical interface.\n- Cool grey canvas with clean white surfaces.\n- Deep teal for primary actions and navigation.\n- Muted amber for warnings and alerts.\n- Clear, compact sans-serif typography.\n- Strong information hierarchy.\n- A distinctive hero composition based on the product.\n\nInclude:\n- A hero introducing the product.\n- A realistic API monitoring dashboard preview.\n- Three product features.\n- An uptime and response-time section.\n- Pricing information.\n- A final call to action.\n\nTechnical requirements:\n- React and CSS.\n- Responsive layout.\n- Reusable components.\n- Accessible buttons and navigation.\n\nAvoid:\n- Generic purple gradients.\n- Identical cards for every section.\n- Unnecessary glass effects.\n- Decorative animations that add no value.\n\nUse realistic placeholder data and identify it as sample data.\n\nBefore coding, briefly explain your design direction.\nThen build the page.\n```\n\nThe important difference is that Claude now knows what the product does and who will use it.\n\nThe `frontend-design` Skill helps it make more deliberate design choices instead of reaching for the same familiar layout.\n\n## 3. Create your own design Skill\n\nThe official Skill is useful, but it doesn't know your brand.\n\nMaybe you always use particular fonts, have a fixed color palette, or want every dashboard to follow the same spacing and component rules.\n\nYou can save those preferences in a custom Skill.\n\nInside your project, create this folder:\n\n```\nyour-project/\n└── .claude/\n    └── skills/\n        └── my-brand-ui/\n            └── SKILL.md\n```\n\nOpen `SKILL.md` and add:\n\n```\n---\nname: my-brand-ui\ndescription: Apply my preferred design system when building\n  landing pages, dashboards, components, and frontend interfaces.\n---\n\n# My Brand UI\n\n## Typography\n- Headings: IBM Plex Sans, weight 600.\n- Body: IBM Plex Sans, 16px.\n- Maintain a clear hierarchy.\n- Load the required fonts explicitly.\n\n## Colors\nDefine these CSS variables on :root:\n\n- --canvas: #E9EFF1\n- --surface: #FBFCFC\n- --ink: #20343B\n- --primary: #0F6B70\n- --secondary: #54747A\n- --warning: #D99A3B\n\nUse the warning color for alerts, not ordinary decoration.\n\n## Layout\n- Follow an 8px spacing scale.\n- Prioritize content hierarchy.\n- Avoid unnecessary cards.\n- Use consistent spacing between sections.\n- Keep mobile layouts simple and readable.\n\n## Components\n- Reuse existing project components where possible.\n- Keep buttons consistent.\n- Include hover and keyboard focus states.\n- Make forms accessible.\n- Avoid unnecessary animations.\n\n## Before finishing\n- Check typography and color consistency.\n- Check text contrast.\n- Test the layout at 375px width.\n- Verify that interactive elements work.\n- Remove decorative elements that don't serve the design.\n```\n\nThe colors and fonts are just an example. Replace them with your actual brand guidelines.\n\nNow Claude has a reusable reference for your preferred design system.\n\nYou can invoke it directly:\n\n```\n/my-brand-ui\n```\n\nYou can also ask Claude to use it when building a new page:\n\n```\nBuild the Monitorly dashboard using my-brand-ui.\nFollow the existing project components and design tokens.\n```\n\n**A useful tip:** Keep project-specific Skills inside `.claude/skills/`. If you want the same Skill available across all your projects on your machine, use `~/.claude/skills/` instead.\n\nIf you're working with a team, commit the project Skill to your repository so everyone can use the same design instructions.\n\n## 4. Make Claude review the UI\n\nThere's another problem with AI-generated interfaces: they can look good in the first draft but still have plenty of small issues.\n\nYou might notice inconsistent spacing, awkward mobile layouts, missing focus states, or buttons that don't work as expected.\n\nLet's create a second Skill to check those things.\n\nCreate:\n\n```\n.claude/\n└── skills/\n    └── ui-review/\n        └── SKILL.md\n```\n\nAdd this:\n\n```\n---\nname: ui-review\ndescription: Review and improve existing frontend interfaces.\n  Use after building or modifying a page or component.\n---\n\n# UI Review\n\nReview the current frontend implementation.\n\n1. Check typography and font consistency.\n2. Check colors against the design system.\n3. Find inconsistent spacing.\n4. Check text and background contrast.\n5. Verify button hover and focus states.\n6. Check navigation and interactive elements.\n7. Look for horizontal overflow on mobile.\n8. Check layouts at 375px, 768px, and 1280px.\n9. Remove unnecessary animations and decoration.\n10. Fix the most important issues first.\n\nIf browser or screenshot tools are available,\ninspect the actual rendered page.\n\nDo not claim something has been tested if it hasn't.\n\nAt the end, summarize:\n- Problems found.\n- Changes made.\n- Issues that still need attention.\n```\n\nAfter Claude finishes building the page, run:\n\n```\n/ui-review\n```\n\nOr give it a more specific instruction:\n\n```\nReview the current Monitorly page.\n\nFix visual inconsistencies, responsive issues,\nand missing interaction states.\n\nKeep the existing design direction.\nDon't redesign everything unnecessarily.\n\nRun the available checks and tell me\nabout anything you couldn't verify.\n```\n\nThis gives you a simple workflow: build the interface, review it, and fix the problems before moving on.\n\n## 5. Test the difference yourself\n\nWant to see whether the Skill actually changes the result?\n\nRun a simple before-and-after test.\n\n**Test A: Without frontend-design**\n\nBefore installing the Skill, start a fresh Claude Code session.\n\nUse the same project setup and submit this prompt:\n\n```\nBuild a landing page for an API monitoring product.\n\nUse React and CSS. Include a hero, features,\nproduct preview, and pricing section.\n```\n\nSave a screenshot of the result.\n\n**Test B: With frontend-design**\n\nNow install the Skill, start another fresh session, and submit exactly the same prompt.\n\nSave another screenshot.\n\nCompare the two pages.\n\nPay attention to:\n\n- Typography and font choices.\n- Hero composition.\n- Color combinations.\n- Layout and spacing.\n- How product information is presented.\n- Whether the mobile version is usable.\n\nFor a fair comparison, use two clean copies of the same starter project. Keep the model, prompt, framework, and available assets the same.\n\nRun the comparison more than once if you want a reliable result. AI output can vary between generations, so one good screenshot doesn't prove the Skill will always produce a better design.\n\nIf you're publishing your own results, include the actual screenshots from these tests. Don't use illustrative mockups as evidence of a real Claude run.\n\n## 6. Find more design Skills\n\nOnce you've tried the official Skill and created your own, you can explore other options.\n\nHere are a few useful places:\n\n- [Anthropic's Skills repository](https://github.com/anthropics/skills) — official examples and reusable instructions.\n- [Anthropic's Claude Code plugins](https://github.com/anthropics/claude-plugins-official) — official plugins, including frontend-design.\n- [Skills.sh](https://skills.sh/) — discover community-created Skills and install them with the CLI.\n- [Agent Skills](https://agentskills.io/) — documentation for the open Skill format.\n\nOne thing worth remembering: don't install every Skill you find.\n\nRead its `SKILL.md`, inspect bundled scripts, and check the repository before using it. Plugins can also include hooks and MCP servers, so review what a plugin adds before enabling it.\n\nStart with one or two and see whether they actually improve your workflow.\n\n## My recommended setup\n\nYou don't need ten different Skills to improve Claude's frontend output.\n\nI'd start with these three:\n\n| Skill | What it does | \n|---|---|\n| `frontend-design` | Helps establish a distinctive visual direction | \n| `my-brand-ui` | Keeps your fonts, colors, and layouts consistent | \n| `ui-review` | Reviews the finished interface for common issues | \n\nUse `frontend-design` when starting a new interface, `my-brand-ui` whenever you're working on your product, and `ui-review` before considering the page finished.\n\nThat's a much better starting point than repeatedly telling Claude to stop using purple gradients.\n\n## Final thoughts\n\nThe biggest improvement isn't necessarily installing more Skills. It's giving Claude better instructions about what you're building and what the finished interface should look like.\n\nStart with Anthropic's `frontend-design`, add your own brand rules, and give the finished page a proper review.\n\nYou can set this up without building a complicated design system or maintaining a huge prompt.\n\nAnd the next time Claude starts creating another generic SaaS landing page, you'll have a better way to steer it.", "url": "https://wpnews.pro/news/claude-skills-that-fix-claude-s-ugly-ui", "canonical_source": "https://zyvop.com/claude-skills-that-fix-claude-s-ugly-ui-584pn", "published_at": "2026-11-19 13:58:16+00:00", "updated_at": "2026-11-19 14:14:05.735853+00:00", "lang": "en", "topics": ["ai-tools", "ai-products", "developer-tools", "generative-ai", "ai-agents"], "entities": ["Anthropic", "Claude Code", "frontend-design", "Vercel", "Skills CLI", "Monitorly", "Node.js"], "also_reported_by": [], "takeaway": "Install Anthropic's `frontend-design` Skill in Claude Code with `/plugin install frontend-design@claude-plugins-official` (or `npx skills add anthropics/skills --skill frontend-design -a claude-code` on Node.js 22.20+) and pair it with a product brief that names fonts, colors, layout and explicit av", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/claude-skills-that-fix-claude-s-ugly-ui", "markdown": "https://wpnews.pro/news/claude-skills-that-fix-claude-s-ugly-ui.md", "text": "https://wpnews.pro/news/claude-skills-that-fix-claude-s-ugly-ui.txt", "jsonld": "https://wpnews.pro/news/claude-skills-that-fix-claude-s-ugly-ui.jsonld"}}