aesthetic▌
mrgoonie/claudekit-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Create aesthetically beautiful interfaces by following proven design principles and systematic workflows.
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:
- Browse inspiration sites (Dribbble, Mobbin, Behance, Awwwards)
- Use chrome-devtools skill to capture full-screen screenshots (not full page)
- 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)
- Document findings in project design guidelines using templates
Workflow 2: Generate & Iterate Design Images
Purpose: Create aesthetically pleasing design images through iteration.
Steps:
- Define design prompt with: style, colors, typography, audience, animation specs
- Use ai-multimodal skill to generate design images with Gemini API
- Use ai-multimodal skill to analyze output images and evaluate aesthetic quality
- 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)
- Repeat until aesthetic standards met (score ≥ 7/10)
- 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
- Aesthetic standards come from humans, not AI—study quality examples
- Iterate based on analysis—never settle for first output
- Balance beauty with functionality and accessibility
- Document decisions for consistency across development
- Use progressive disclosure in design—reveal complexity gradually
- Always evaluate aesthetic quality objectively (score ≥ 7/10)
How to use aesthetic on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add aesthetic
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches aesthetic from GitHub repository mrgoonie/claudekit-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate aesthetic. Access the skill through slash commands (e.g., /aesthetic) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★38 reviews- ★★★★★Xiao Sharma· Dec 20, 2024
aesthetic has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Amina Martinez· Dec 16, 2024
We added aesthetic from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Alexander Chawla· Dec 16, 2024
Keeps context tight: aesthetic is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Dec 12, 2024
Keeps context tight: aesthetic is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kabir Ramirez· Nov 11, 2024
Useful defaults in aesthetic — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Alexander Abebe· Nov 7, 2024
Registry listing for aesthetic matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Piyush G· Nov 3, 2024
Registry listing for aesthetic matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Alexander Farah· Oct 26, 2024
aesthetic reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Shikha Mishra· Oct 22, 2024
aesthetic reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Min Chawla· Oct 2, 2024
I recommend aesthetic for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 38