Loading...
Loading...
Found 25 Skills
Audits code for SOLID principle violations — Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. Identifies classes and methods that violate these principles and generates fix prompts. Trigger phrases: "SOLID check", "solid review", "SRP violation", "dependency inversion".
Framework orientation for Layers of Product Design — load this first; provides the context all other skills depend on
Actionable design system complementing official frontend-design plugin. The plugin provides philosophy; this skill provides executable patterns. Invoke when: - Building web components, pages, or applications - Designing UI that needs to stand out (not generic) - Implementing visual polish and micro-interactions - Choosing typography, color palettes, or spatial layouts CRITICAL: Avoid "AI slop" aesthetics. Make creative, unexpected choices. MANDATORY: Consult Gemini before any frontend work. See also: references/dna-codes.md, references/banned-patterns.md
Use when working on landing pages — creation, copywriting, design, optimization, or conversion rate improvement. Covers hero sections, above-the-fold content, value propositions, CTAs, landing page templates, and high-converting page structure. Applies to sales pages, lead capture pages, product pages, and marketing site pages. Use this skill for landing page copy, landing page design, landing page optimization, CTA writing, conversion rate optimization, hero section content, value proposition work, and any page builder or landing page template tasks.
Design clear, accessible data visualizations with appropriate chart selection and styling.
Audit and refactor code for clarity, maintainability, and correctness. Use when the user asks to refactor, clean up code, reduce complexity, fix code smells, or improve code quality.
Understand and apply psychological concepts to create superior user experiences (UX) in frontend design.
Apply principles of good design taste when creating, reviewing, or critiquing any creative or technical work. Use this skill whenever the user asks you to design something, review a design, create UI/UX, architect a system, write something with aesthetic intent, evaluate the quality of code or creative work, or asks for feedback on whether something is "good." Also trigger when users mention taste, aesthetics, beauty in design, elegance, simplicity, or when they want help making something not just functional but genuinely well-crafted. This skill applies across domains: software, writing, visual design, architecture, presentations, APIs, data models, and more. Even if the user doesn't explicitly mention "design," use this skill when the underlying task is about making something better, more elegant, or more refined.
Use when a request asks for software design patterns or design principles, including explanations, comparisons, summaries, or quick reference grounded in local docs.
Help other designers develop judgment without imposing your style. Use when mentoring designers, running design education, or building team-wide quality standards.
Use when making UI/UX decisions, building components, choosing colors, layouts, typography, or reviewing any visual design — enforces anti-slop standards against generic AI aesthetics
Transforms Claude from a 'Graphic Designer' into a 'Design Thinker'. Trigger this skill whenever the user asks for design, redesign, creation of graphics, layouts, UI/UX, or any creative asset. Use this skill even if the user provides a direct request like 'make a flyer' or 'redesign my site'. The goal is to ask critical questions and solve the underlying problem before touching any visual elements.