Skip to content
cccskills
FreePublished on GitHub

aesthetic

Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.

The English summary is being prepared. Showing the original description.

Works withGemini
See how to install

Files included (7)

  • SKILL.md6.2 KB
  • assets/design-guideline-template.md3.4 KB
  • assets/design-story-template.md2.6 KB
  • references/design-principles.md2.3 KB
  • references/design-resources.md2.2 KB
  • references/micro-interactions.md1.7 KB
  • references/storytelling-design.md1.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Aesthetic

Create aesthetically beautiful interfaces by following proven design principles and systematic workflows.

When to Use This Skill

Use when:

  • Building or designing user interfaces
  • Analyzing designs from inspiration websites (Dribbble, Mobbin, Behance)
  • Generating design images and evaluating aesthetic quality
  • Implementing visual hierarchy, typography, color theory
  • Adding micro-interactions and animations
  • Creating design documentation and style guides
  • Need guidance on accessibility and design systems

Core Framework: Four-Stage Approach

1. BEAUTIFUL: Understanding Aesthetics

Study existing designs, identify patterns, extract principles. AI lacks aesthetic sense—standards must come from analyzing high-quality examples and aligning with market tastes.

Reference: references/design-principles.md - Visual hierarchy, typography, color theory, white space principles.

2. RIGHT: Ensuring Functionality

Beautiful designs lacking usability are worthless. Study design systems, component architecture, accessibility requirements.

Reference: references/design-principles.md - Design systems, component libraries, WCAG accessibility standards.

3. SATISFYING: Micro-Interactions

Incorporate subtle animations with appropriate timing (150-300ms), easing curves (ease-out for entry, ease-in for exit), sequential delays.

Reference: references/micro-interactions.md - Duration guidelines, easing curves, performance optimization.

4. PEAK: Storytelling Through Design

Elevate with narrative elements—parallax effects, particle systems, thematic consistency. Use restraint: "too much of anything isn't good."

Reference: references/storytelling-design.md - Narrative elements, scroll-based storytelling, interactive techniques.

Workflows

Workflow 1: Capture & Analyze Inspiration

Purpose: Extract design guidelines from inspiration websites.

Steps:

  1. Browse inspiration sites (Dribbble, Mobbin, Behance, Awwwards)
  2. Use chrome-devtools skill to capture full-screen screenshots (not full page)
  3. Use ai-multimodal skill to analyze screenshots and extract:
    • Design style (Minimalism, Glassmorphism, Neo-brutalism, etc.)
    • Layout structure & grid systems
    • Typography system & hierarchy IMPORTANT: Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use Inter or Poppins.
    • Color palette with hex codes
    • Visual hierarchy techniques
    • Component patterns & styling
    • Micro-interactions
    • Accessibility considerations
    • Overall aesthetic quality rating (1-10)
  4. Document findings in project design guidelines using templates

Workflow 2: Generate & Iterate Design Images

Purpose: Create aesthetically pleasing design images through iteration.

Steps:

  1. Define design prompt with: style, colors, typography, audience, animation specs
  2. Use ai-multimodal skill to generate design images with Gemini API
  3. Use ai-multimodal skill to analyze output images and evaluate aesthetic quality
  4. If score < 7/10 or fails professional standards:
    • Identify specific weaknesses (color, typography, layout, spacing, hierarchy)
    • Refine prompt with improvements
    • Regenerate with ai-multimodal or use media-processing skill to modify outputs (resize, crop, filters, composition)
  5. Repeat until aesthetic standards met (score ≥ 7/10)
  6. Document final design decisions using templates

Design Documentation

Create Design Guidelines

Use assets/design-guideline-template.md to document:

  • Color patterns & psychology
  • Typography system & hierarchy
  • Layout principles & spacing
  • Component styling standards
  • Accessibility considerations
  • Design highlights & rationale

Save in project ./docs/design-guideline.md.

Create Design Story

Use assets/design-story-template.md to document:

  • Narrative elements & themes
  • Emotional journey
  • User journey & peak moments
  • Design decision rationale

Save in project ./docs/design-story.md.

Resources & Integration

Related Skills

  • ai-multimodal: Analyze documents, screenshots & videos, generate design images, edit generated images, evaluate aesthetic quality using Gemini API
  • chrome-devtools: Capture full-screen screenshots from inspiration websites, navigate between pages, interact with elements, read console logs & network requests
  • media-processing: Refine generated images (FFmpeg for video, ImageMagick for images)
  • ui-styling: Implement designs with shadcn/ui components + Tailwind CSS utility-first styling
  • web-frameworks: Build with Next.js (App Router, Server Components, SSR/SSG)

Reference Documentation

References: references/design-resources.md - Inspiration platforms, design systems, AI tools, MCP integrations, development strategies.

Key Principles

  1. Aesthetic standards come from humans, not AI—study quality examples
  2. Iterate based on analysis—never settle for first output
  3. Balance beauty with functionality and accessibility
  4. Document decisions for consistency across development
  5. Use progressive disclosure in design—reveal complexity gradually
  6. Always evaluate aesthetic quality objectively (score ≥ 7/10)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Process and generate multimedia content using Google Gemini API. Capabilities include analyze audio files (transcription with timestamps, summarization, speech understanding, music/sound analysis up to 9.5 hours), understand images (captioning, object detection, OCR, visual Q&A, segmentation), process videos (scene detection, Q&A, temporal analysis, YouTube URLs, up to 6 hours), extract from documents (PDF tables, forms, charts, diagrams, multi-page), generate images (text-to-image, editing, composition, refinement). Use when working with audio/video files, analyzing images or screenshots, processing PDF documents, extracting structured data from media, creating images from text prompts, or implementing multimodal AI features. Supports multiple models (Gemini 2.5/2.0) with context windows up to 2M tokens.

The English summary is being prepared. Showing the original description.

mrgoonie/claudekit-skills2.2KUpdated Apr 3, 2026

Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

The English summary is being prepared. Showing the original description.

mrgoonie/claudekit-skills2.2KUpdated Apr 3, 2026

Implement authentication and authorization with Better Auth - a framework-agnostic TypeScript authentication framework. Features include email/password authentication with verification, OAuth providers (Google, GitHub, Discord, etc.), two-factor authentication (TOTP, SMS), passkeys/WebAuthn support, session management, role-based access control (RBAC), rate limiting, and database adapters. Use when adding authentication to applications, implementing OAuth flows, setting up 2FA/MFA, managing user sessions, configuring authorization rules, or building secure authentication systems for web applications.

The English summary is being prepared. Showing the original description.

mrgoonie/claudekit-skills2.2KUpdated Apr 3, 2026

bunny

Free

Integrate Bunny.net services (CDN, Storage, Stream, DNS, Edge Scripting, Shield, Magic Containers, Optimizer, Database). Use when building with Bunny.net APIs, deploying to Bunny CDN, uploading files to Edge Storage, managing video streaming, configuring DNS zones, writing edge scripts, setting up WAF/DDoS protection, deploying containers, or optimizing images. Triggers on "bunny", "bunnycdn", "b-cdn", "pull zone", "edge storage", "bunny stream".

The English summary is being prepared. Showing the original description.

mrgoonie/claudekit-skills2.2KUpdated Apr 3, 2026

Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.

The English summary is being prepared. Showing the original description.

mrgoonie/claudekit-skills2.2KUpdated Apr 3, 2026

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

The English summary is being prepared. Showing the original description.

mrgoonie/claudekit-skills2.2KUpdated Apr 3, 2026

See all skills by mrgoonie

Report a problem with this skill