Introduction

If you've used Claude Code to build anything, you've probably noticed a pattern: it writes solid, working code, but the interface often looks like every other AI-generated app out there. Inter font, a blue-to-purple gradient header, three cards in a row, an emoji tucked into each one. It's become so common that people can spot an AI-built UI within seconds.

9 Best Design Skills for Claude Code in 2026 — Tested and Ranked

The fix for a lot of developers has been "skills" — a folder containing a single file (SKILL.md) that teaches Claude how to handle one specific task really well. Claude automatically pulls in the right skill when your request matches it, so you don't need to write long, repetitive prompts every time. Design knowledge in particular has exploded into this format.

The problem now is there are simply too many of them. Many are barely more than a single prompt dressed up with a nice README, and a lot of them overlap — install three at once and Claude ends up getting conflicting instructions about fonts, spacing, and layout.

Below is a tested list of the ones actually worth installing, based on real output across a landing page, a dashboard, and a settings page for each.

1. frontend-design (by Anthropic)

This is the one to install first, and it comes straight from Anthropic. Before writing any code, it forces Claude to commit to a real design direction — brutalist, editorial, retro-futuristic, luxury, playful — instead of defaulting to the generic "centered hero, three cards, footer" layout. It's currently the most widely installed design skill available, and for good reason: it resets Claude's baseline taste, so everything you build afterward improves without extra prompting effort.

1. frontend-design (Anthropic)
   Install: /plugin install frontend-design@claude-plugins-official or npx skills add anthropics/skills --skill frontend-design
   GitHub: github.com/anthropics/skills

2. UI UX Pro Max

Where frontend-design gives Claude taste, this one gives it a full reference library — a searchable database of UI styles, over 190 color palettes organized by industry, 70+ font pairings, and a reasoning engine that turns a vague brief like "I'm building a fintech app" into a complete, matched design system. It supports more than 20 frameworks, including React, Next.js, Vue, SwiftUI, and Flutter, and is one of the most-starred skill repositories currently available.

1. UI UX Pro Max
   Install: /plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill, then /plugin install ui-ux-pro-max@ui-ux-pro-max-skill
   GitHub: github.com/nextlevelbuilder/ui-ux-pro-max-skill

3. Taste Skill

This pack exists specifically to override Claude's generic design instincts. Instead of vague instructions like "make it look modern," it gives Claude concrete, metric-driven layout, typography, motion, and spacing rules. It also includes style-specific variants (minimalist, brutalist, high-end visual) and a standout feature: a skill that audits an existing codebase and flags exactly what's making the UI feel cheap or dated, then fixes it section by section.

1. Taste Skill
   Install: npx skills add https://github.com/Leonxlnx/taste-skill --skill "design-taste-frontend"
   GitHub: github.com/Leonxlnx/taste-skill

4. Impeccable

This one functions more like a full design toolkit than a single skill. It adds over 20 commands for setting up a project's design direction, running technical audits, doing UX critiques, and polishing the final result. Breaking design work into discrete steps — critique, then polish — makes the process feel far more structured than just asking Claude to "improve" something and hoping for the best.

1. Impeccable
   Install: /plugin marketplace add pbakaus/impeccable, then install via /plugin
   GitHub: github.com/pbakaus/impeccable

5. Emil Kowalski's Skills

If an app looks fine but feels lifeless, this is usually the fix. Built by a well-known design engineer, this pack focuses entirely on motion — proper easing, duration, and animation review — along with tools for spotting where subtle animation would actually improve the experience. Motion is often where AI-built interfaces give themselves away, and this addresses exactly that gap.

1. Emil Kowalski's Skills
   Install: npx skills@latest add emilkowalski/skills
   GitHub: github.com/emilkowalski/skills

6. Interface Design

One frustrating habit of AI coding tools is forgetting earlier design decisions between sessions. This skill solves that by saving your project's design system — button heights, spacing, colors, patterns — to a local file that Claude reads every time it starts working again. The result is consistency across pages built days or weeks apart, instead of small stylistic drift creeping in page by page.

1. Interface Design
   Install: npx skills add https://github.com/dammyjay93/interface-design --skill interface-design --agent claude-code -g
   GitHub: github.com/Dammyjay93/interface-design

7. shadcn/ui Skill

For anyone building with shadcn/ui components, this is the official skill and an easy install. It reads your project's existing component setup so Claude knows exactly what's already available, preventing it from hand-writing duplicate components or importing from the wrong path.

1. shadcn/ui Skill
   Install: npx skills add shadcn/ui
   GitHub: github.com/shadcn-ui/ui

8. Web Design Guidelines (by Vercel)

Less flashy than the others, but arguably one of the most useful. It checks your UI code against more than 100 real interface guidelines — accessibility, focus states, form behavior, reduced-motion support, image dimensions, and locale formatting. These are the invisible details that separate a genuinely polished product from something that merely looks fine in a screenshot.

1. Web Design Guidelines (Vercel)
   Install: npx skills add https://github.com/vercel-labs/agent-skills --skill web-design-guidelines
   GitHub: github.com/vercel-labs/agent-skills

9. webapp-testing (by Anthropic)

The skill that ties everything else together. It lets Claude actually open your app using Playwright, take screenshots, click through user flows, and read browser logs — meaning it can catch its own mistakes, like an overlapping mobile navigation bar, before you ever open the browser yourself.

1. webapp-testing (Anthropic)
   Install: /plugin marketplace add anthropics/skills, then /plugin install example-skills@anthropic-agent-skills
   GitHub: github.com/anthropics/skills

A Word of Caution

Don't install all nine at once. Design skills overlap more than any other category, and running several with conflicting rules produces a confused result rather than a better one. A sensible starting stack: frontend-design for taste, Interface Design for consistency, and Web Design Guidelines as a final pre-launch check — then add shadcn's skill if relevant, and pick either UI UX Pro Max or Taste Skill as your main style engine, not both.

Conclusion

The skills genuinely worth keeping all share one trait: they don't just tell Claude to "make it look good." They hand it a real design system, concrete rules, persistent memory, or actual visibility into the finished result. That's what separates a tool that helps from one that just adds noise.

Which of these skills have you tried? Share your experience in the comments, and pass this along to any developer still shipping AI-generated interfaces that all look the same.

 6 PHP 8 Features You Should Be Using in 2026

1. Constructor property promotion

class User {
    public function __construct(
        public string $name,
        public string $email
    ) {}
}

2. Named arguments

setcookie(name: 'token', value: $t, httponly: true);

3. Nullsafe operator

$city = $user?->address?->city;

4. match expression

$label = match($status) {
    1 => 'Active',
    2 => 'Pending',
    default => 'Unknown',
};

5. Enums (PHP 8.1+)

enum Status: int {
    case Active = 1;
    case Pending = 2;
}

6. Readonly properties (PHP 8.1+)

public readonly int $id;

match throws an error for unmatched values without a default, unlike switch, which quietly falls through. That catches bugs earlier.

Which feature do you use most? Drop a comment, and share this with a PHP developer still writing PHP 5 style code.

 Most PHP developers learn MySQL by trial and error, which means a lot of bad habits get baked into production code early and never get questioned. Here are the ten most common mistakes that quietly wreck performance as your application scales.

10 MySQL Mistakes

1. Using SELECT * Instead of Named Columns

-- Bad
SELECT * FROM users WHERE id = 1;

-- Good
SELECT id, name, email FROM users WHERE id = 1;

SELECT * pulls unnecessary data over the wire and prevents MySQL from using covering indexes effectively.

2. Not Using Prepared Statements

// Vulnerable to SQL injection
$query = "SELECT * FROM users WHERE email = '$email'";

// Safe and reusable
$stmt = $pdo->prepare("SELECT * FROM users WHERE email = ?");
$stmt->execute([$email]);

Beyond security, prepared statements let MySQL cache the query execution plan, improving performance on repeated queries.

3. Missing Indexes on Foreign Keys
A shocking number of production databases have foreign key columns with no index at all, turning every JOIN into a full table scan.

4. N+1 Query Problem

// Bad - runs 1 query + N queries in a loop
foreach ($orders as $order) {
    $items = getItemsByOrderId($order['id']);
}

// Good - one query with a JOIN
$query = "SELECT o.*, i.* FROM orders o 
          JOIN items i ON i.order_id = o.id";

5. Using LIKE '%keyword%' on Large Tables
Leading wildcards prevent MySQL from using indexes at all. For real search functionality, use MySQL's FULLTEXT indexes or a dedicated search engine like Elasticsearch.

6. Storing Passwords Without Proper Hashing

// Never do this
$password = md5($_POST['password']);

// Always do this
$password = password_hash($_POST['password'], PASSWORD_DEFAULT);

7. Not Closing Database Connections
Long-running scripts that don't explicitly close connections can exhaust MySQL's max_connections limit under load.

8. Ignoring EXPLAIN on Slow Queries
Running EXPLAIN SELECT ... before deploying a query takes 10 seconds and can reveal missing indexes or full table scans before they hit production.

9. Storing Dates as Strings

-- Bad
created_at VARCHAR(20)

-- Good
created_at DATETIME

String dates break sorting, filtering, and date arithmetic, and they're a common source of subtle bugs.

10. Not Using Connection Pooling in High-Traffic Apps
Opening a fresh MySQL connection on every request is expensive. For high-traffic PHP apps, persistent connections or a pooling layer significantly reduce overhead.

Found a mistake you're guilty of? Drop a comment — and share this with a junior dev on your team before it costs you a production incident.

Banning things reflects cultural values — and sometimes produces surprising results.

Unusual Bans Around the World

Chewing Gum in Singapore

Singapore banned the import and sale of chewing gum in 1992. The reason: gum stuck to public surfaces, causing maintenance issues. Exceptions exist for therapeutic gum (prescribed by doctors).

Diamonds in Russia

During the Soviet era, citizens were discouraged from wearing diamonds publicly. The government viewed them as Western capitalist symbols. Owning large diamonds was considered suspicious.

Hamas in Many Countries

Hamas is designated a terrorist organization by many Western countries. Various forms of the group are banned across Europe, North America, and elsewhere.

Baby Walkers in Canada

Canada banned baby walkers in 2004, citing safety concerns. Babies can fall down stairs, reach dangerous objects, or tip the walker over. The ban applies to selling, importing, and advertising them.

Pet Fish in Romania

Romania previously banned goldfish as pets, though enforcement was unclear. The rationale was that keeping fish in small bowls was considered animal cruelty.

Knives in Public in Various Countries

Several countries including the UK, Australia, and others restrict carrying knives in public spaces. Specific blade lengths and types vary.

Why They Ban Things

• Public safety — baby walkers, knives
• Cultural values — diamonds in Soviet Russia
• Public order — gum in Singapore
• Animal welfare — fish in Romania
• Terrorism — political organizations

For decades, some of the most notorious crimes went unsolved. DNA technology changed that.

Cases Cracked

The Golden State Killer

For over 30 years, the Golden State Killer (later called the East Area Rapist) terrorized California. At least 13 murders, 50 rapes. In 2018, DNA from a crime scene was uploaded to a public genealogy database. A distant relative's DNA match identified Joseph James DeAngelo. He was arrested at age 72.

The BTK Killer

Dennis Rader killed 10 people in Kansas between 1974 and 1991. He taunted police with letters and a floppy disk. In 2005, DNA from the disk matched a family member. Rader was arrested. He is serving 10 consecutive life sentences.

Elizabeth Short (Black Dahlia)

The 1947 murder of Elizabeth Short has never been officially solved. In 2018, a retired detective claimed DNA evidence and modern genealogy pointed to a suspect. The LAPD hasn't confirmed these findings.

The Zodiac Killer

In 2018, forensic genealogists identified a suspect in the Zodiac's 1969 Lake Berryessa attack using DNA from the postage stamp. The suspect died in 2018. Police have not confirmed the findings.

How It Works

Forensic genealogists take crime scene DNA, upload it to public databases, and look for matches with people who voluntarily submitted their DNA for ancestry research. Even distant relatives can provide enough information to narrow down suspects to a specific family tree.

The Controversy

• Privacy concerns — people who never committed crimes can be identified through relatives
• Consent — genetic data was uploaded for genealogy, not law enforcement
• D数据库 coverage — databases are predominantly used by people of European descent

Some people vanish and leave almost no trace. Despite extensive searches and investigations, no explanation ever emerges.

Notable Cases

1. The Sodder Children (1945)

Five of the nine Sodder children disappeared during a fire at their family home in Fayetteville, West Virginia. The parents believed the children died, but the body was never recovered. The family never gave up hope — and the case remains officially unsolved.

2. Harold Holt (1967)

Harold Holt, the Prime Minister of Australia, went swimming at Cheviot Beach in Victoria. He never surfaced. Despite one of the largest search operations in Australian history, his body was never found.

3. The Lost City of Z

British explorer Percy Fawcett disappeared in the Amazon rainforest in 1925 while searching for a legendary lost city. He and his son Jack, along with Jack's friend Raleigh Rimell, were never found.

4. The Mary Celeste

The Mary Celeste was found adrift in the Atlantic Ocean in 1872. The ship was intact, supplies were ample, but the crew was gone — ten people and the captain's family. No one was ever found or determined to be responsible.

5. The Skeleton Coast Ships

Namibia's Skeleton Coast has dozens of shipwrecks with no crew aboard. Some date back centuries. Theories range from storms to mutiny to supernatural causes. No artifacts explain the disappearances.

Why Some Disappearances Stay Mysterious

• Remote locations — bodies in wilderness may never be found
• Water — oceans and rivers swallow evidence
• Time — evidence degrades, witnesses die
• Intentionally hidden — some disappearances are planned

Some robberies were so audacious that the criminals vanished — and the loot remained missing.

The Biggest Unsolved Heists

1. Isabella Stewart Gardner Museum (1990)

Two men dressed as Boston police officers entered the Gardner Museum through a side entrance. They subdued the guards and walked out with 13 works of art — including Rembrandt's "The Storm on the Sea of Galilee." The heist is the largest property crime in US history. The art has never been recovered.

The reward is $10 million. In 2013, the FBI announced they believed they knew the identities of the thieves but chose not to reveal them in order to protect an ongoing investigation.

2. The Central Bank of Iraq (1990)

During the Gulf War, Iraqi forces allegedly removed approximately $1 billion in gold and currency from the Central Bank of Kuwait. The scale and method remain disputed. Much of the gold was never recovered.

3. The Hatton Garden Safe Deposit Heist (2015)

In London, a gang of elderly thieves broke into the vault over Easter weekend. They accessed 73 safe deposit boxes containing an estimated $200 million in jewelry, cash, and valuables. Most of the gang was eventually caught and sentenced — but a significant portion of the loot remains unrecovered.

4. The Brink's-Mat Robbery (1983)

Gunmen robbed the Brink's-Mat warehouse at Heathrow Airport in London, taking about $26 million in gold, diamonds, and cash. Only a small fraction was ever recovered. Several people were killed in connection to the aftermath, but most of the gold has never been found.

Why They Stay Unsolved

• No witnesses — careful planning eliminates witnesses
• Clean getaway — no trail to follow
• Destroyed evidence — loot melted, sold, or hidden
• Inside help — someone within the institution facilitated entry
• Time — statute of limitations expires, witnesses die