By weberswords
Foundational designer skills: detect a project's existing design system, honor its vibe instead of homogenizing it, build the project its own system when it has none, audit an existing one for consistency, apply UX principles, and work from a brand kit. No house style — every project gets its own, integrated into its repo.
Capture, define, and apply a project's brand kit — logo, color, typography, voice, imagery, and motion personality — so design work stays on-brand and identity is preserved. Use when a project has brand assets that must be honored, when starting a project that needs a brand foundation defined, or before a redesign (existing brand is starting material, not optional). Produces or reads a brand-kit.md the whole team and toolkit can work from, integrated into the target project's repo. designer has no house brand of its own — this captures each project's own identity.
Help a project discover its own design aesthetic and build its own design system from scratch — when it has none, or only scattered fragments. Use when starting design work on a project without a coherent system, or when the user wants to establish one. Analyzes the target project, asks sharp questions to shape a direction, recommends options with rationale, then builds the tokens, type, color, spacing, and conventions INTO the target project's repository. There is no house baseline to impose — every value is chosen for this project. Confirm maturity with detect-design-system first.
Evaluate an existing design or design system for quality and consistency, and report concrete fixes. Use when a project already has a design system or built UI and you want to check whether it holds together — consistent corner rounding, values on the scale, tokens vs. one-off colors, real visual hierarchy, and no lazy patterns like boxes-nested-in-boxes or everything-is-a-gray-card. Produces a prioritized findings list with specific fixes that get integrated into the target project's repository. Run detect-design-system first to know what the system is before judging whether it's applied well.
Inspect a codebase to discover its existing design system (if it has one) before making any visual change. Use whenever you start UI work in an unfamiliar project, are asked to add a component or page that must fit in, or are redesigning and need to know what to preserve. Inventories design tokens, theme files, Tailwind/CSS config, component libraries, fonts, color, spacing, radii, shadows, and motion, then produces a structured Design Read. Not for authoring a new system from scratch — for finding and honoring the one that's already there.
The prime directive and entry point for design work across any project. Use at the START of any UI/UX task — designing, redesigning, building a component or page, styling, theming, establishing or auditing a design system. Reads a project's own vibe, energy, feeling, and goals and commits to honoring them instead of flattening everything into the same generic look. designer has no house style of its own — it helps each project find and build its own. Sets the precedence order (the project's own identity always wins) and routes to the right foundational skill. Not for backend or non-UI work.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Your portable UI/UX designer for Claude Code — a plugin marketplace you add to any repo to get a designer's foundational craft plus a curated set of best-in-class design skills.
The whole thing is built around one objective:
Honor each project's own vibe, energy, feeling, and goals — don't make everything look the same.
It reads what a project already is, respects its existing design system, and only reaches for house defaults when there's nothing of the project's own to honor. Difference is the deliverable.
This repo is a Claude Code plugin marketplace. It ships one plugin authored here and references three excellent third-party skill sets, so installing this one marketplace gives you the whole designer.
| Plugin | Source | What it gives you |
|---|---|---|
ih-designer | this repo | The foundational designer: detect a project's design system, honor its vibe, build the project its own system when it has none, audit an existing one, apply UX principles, and work from a brand kit. No house style — every project gets its own. |
impeccable | pbakaus/impeccable | Broad frontend design fluency — one skill with ~23 commands (polish, audit, critique, craft, …) and anti-pattern detection. Ships a Node-based PostToolUse hook that lints UI edits. |
taste-skill | leonxlnx/taste-skill | Anti-slop taste for landing pages, portfolios, and redesigns (brutalist, minimalist, soft, redesign, brandkit, image-to-code, …). |
emil-design-skills | emilkowalski/skills | Design-engineering taste from Vercel/Linear pedigree — motion, easing, animation review, and interface detail. |
ih-designer foundational skillshonor-the-vibe — the prime directive and entry point. Reads the project, sets the precedence order (the project's own identity always wins), routes to the right skill, and refuses homogenization. Start here.detect-design-system — inspects a codebase for its existing tokens, theme, component library, type, color, space, and motion, and produces a structured Design Read with a maturity verdict.build-design-system — when a project has no system (or fragments), facilitates finding its aesthetic (asks questions, recommends directions) and builds its own tokens/type/color/space/conventions into the target repo.design-audit — when a system already exists, checks quality and consistency: consistent corner rounding, on-scale values, real hierarchy, no boxes-in-boxes.ux-principles — style-agnostic usability, accessibility, and interaction fundamentals (+ a full ux-principles.md checklist).brand-kit — capture, define, and apply a project's brand identity (+ a brand-kit-template.md).designer has no baseline design system of its own. You point it at a project — say a repo called
tide— and its job is to analyzetide, help shapetide's aesthetic, and integrate the result intotide's repository. Two projects designer touches should end up looking like themselves, not like each other.
honor-the-vibe ─▶ detect-design-system ─▶ read the project's vibe, goals & maturity
│ │
│ branch on maturity: ▼
│ Established ─▶ honor it + design-audit (tighten, don't restyle)
│ Partial ─▶ build-design-system (consolidate) + design-audit
│ None ─▶ build-design-system (create the project its own)
│
│ precedence when deciding (higher wins):
│ 1. project's own design system ─▶ extend it invisibly
│ 2. project's brand kit / assets ─▶ brand-kit
│ 3. a system built with the project ─▶ build-design-system
│ 4. craft references ─▶ impeccable · taste-skill · emil
│ 5. universal UX principles ─▶ ux-principles
▼
commit & ship into the TARGET repo — real tokens, verified contrast, honest motion
There is no designer house style in that order. The fallback for a blank project is to build the project's own — never to stamp a default.
In any project where you use Claude Code:
/plugin marketplace add weberswords/designer
Then install the whole designer, or pick pieces:
/plugin install ih-designer@designer
/plugin install impeccable@designer
/plugin install taste-skill@designer
/plugin install emil-design-skills@designer
Update the catalog later with:
/plugin marketplace update designer
npx claudepluginhub weberswords/designer --plugin ih-designerComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
This skill should be used when users need to generate ideas, explore creative solutions, or systematically brainstorm approaches to problems. Use when users request help with ideation, content planning, product features, marketing campaigns, strategic planning, creative writing, or any task requiring structured idea generation. The skill provides 30+ research-validated prompt patterns across 14 categories with exact templates, success metrics, and domain-specific applications.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Consult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, plus codex, antigravity, and grok CLIs when installed) to get diverse perspectives on coding problems