Agent skill

Premium SaaS Design

by HermeticOrmus in HermeticOrmus/LibreUIUX-Claude-Code

The Define, Build, Review, Refine loop and seven context artifacts (brief, content, mood boards, section specs, style guide, PRD, tasks) for building a premium SaaS marketing site with AI.

MITAuto-check passedFrontend & Design

Install Premium SaaS Design

skills CLI
$ npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code premium-saas-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/design-mastery/skills/premium-saas-design .claude/skills/premium-saas-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
premium-saas-design
GitHub stars
112
Token cost
~3.3k tokens
SKILL.md length
743 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

The Define, Build, Review, Refine loop and seven context artifacts (brief, content, mood boards, section specs, style guide, PRD, tasks) for building a premium SaaS marketing site with AI.

  • Works in 11 steps: Project Brief → Content Files (One Per Section) → General Vibe Mood Board → …
  • Building a SaaS landing page and you want the design context written down before any code
  • SKILL.md covers The Core Loop, The 7 Context Artifacts, Hero Content Area and Components from Libraries, plus 9 more sections
  • Calls git

What it does

Premium SaaS Design is an agent skill from HermeticOrmus/LibreUIUX-Claude-Code. The Define, Build, Review, Refine loop and seven context artifacts (brief, content, mood boards, section specs, style guide, PRD, tasks) for building a premium SaaS marketing site with AI. Use when planning or building a SaaS landing page and you want the design context written down before any code.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Landing pages and PRD writing. The repository describes itself as: UI/UX system for Claude Code: 71 plugins, 93 agents, 74 skills. Design mastery, archetypal design, accessibility, and frontend workflows in one validated plugin marketplace. The licence is MIT.

When your agent uses it

  • Building a SaaS landing page and you want the design context written down before any code
  • Tasks that involve Landing pages
  • Tasks that involve PRD writing

Example prompts

  • “/premium-saas-design”

Workflow steps

11 steps, taken from the step headings in SKILL.md.

  1. Project Brief
  2. Content Files (One Per Section)
  3. General Vibe Mood Board
  4. Section-Specific Mood Boards
  5. Project Requirements Document (PRD)
  6. Section Isolation
  7. Commit Per Section
  8. Include Reference Images
  9. Include Component Code
  10. Auto-Update Style Guide
  11. Screenshot-to-Iteration

What it can do on your machine

Read from SKILL.md and the folder at commit 41a968c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • ui.shadcn.com
    • 21st.dev
    • threejs.org
    • sketchfab.com
    • youtube.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Premium SaaS Design loads about 3.3k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 743 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HermeticOrmus/LibreUIUX-Claude-Code at commit 41a968c, republished under its MIT licence (© HermeticOrmus). 743 words, ~3,335 tokens.

Download SKILL.mdSave it as .claude/skills/premium-saas-design/SKILL.md (or your agent's skills folder).
name
premium-saas-design
description
The Define, Build, Review, Refine loop and seven context artifacts (brief, content, mood boards, section specs, style guide, PRD, tasks) for building a premium SaaS marketing site with AI. Use when planning or building a SaaS landing page and you want the design context written down before any code.

Premium SaaS Design Framework

In Stanford's large 2002 web credibility study (B.J. Fogg and colleagues), a site's visual design was the factor people mentioned most often when they judged whether to trust it.

This skill captures the professional design workflow used by senior product teams and UI/UX designers, adapted for AI-assisted development. The framework transforms AI from a "guessing machine" into a true design partner.


The Core Loop

DEFINE → BUILD → REVIEW → REFINE
   ↑                        │
   └────────────────────────┘

This loop is everything. It's used by real product teams and works wonders with AI.


The 7 Context Artifacts

AI needs context to produce premium results. These 7 documents form your "design contract" with AI:

1. Project Brief

What: Single document explaining what you're building, why, and for whom. Purpose: Gives AI direction and understanding of the project.

markdown
# Project Brief: [Product Name]

## What We're Building
[Description of the product/website]

## Primary Target Audience
- [Persona 1]: [Description]
- [Persona 2]: [Description]

## Goals
1. [Primary goal - e.g., drive signups]
2. [Secondary goal - e.g., build trust]
3. [Tertiary goal - e.g., explain the product]

## Requirements
- Fully responsive (mobile-first)
- Blazing fast performance
- Accessible (WCAG 2.1 AA)
- [Other requirements]

## Sections
1. Hero
2. Trust Logos
3. Features
4. [etc.]

Key Insight: Think of AI as a new team member. You wouldn't tell them "build me a website" without context.


2. Content Files (One Per Section)

What: Separate file for each section containing all copy/content. Purpose: Focuses AI on content separately from design.

markdown
# Hero Section Content

## Headline
[Main headline text]

## Subheadline
[Supporting text]

## CTA Primary
Text: [Button text]
Action: [What happens on click]

## CTA Secondary
Text: [Link text]
Action: [What happens on click]

## Social Proof (optional)
[Trust indicators, stats, etc.]

3. General Vibe Mood Board

What: Visual inspiration for the overall site aesthetic. Purpose: Answers "What should the whole site FEEL like when we land on it?"

markdown
# General Vibe

## Overall Aesthetic
- Theme: [Dark/Light/Mixed]
- Feel: [Modern, Professional, Playful, etc.]
- Color Direction: [Primary color family and why]

## Inspiration References

### Reference 1: [Site Name]
- URL: [link]
- What I Like:
  - [Specific element 1]
  - [Specific element 2]
- Screenshot: [embedded image]

### Reference 2: [Site Name]
- URL: [link]
- What I Like:
  - [Specific element 1]
  - [Specific element 2]
- Screenshot: [embedded image]

## Color Psychology
- Primary Color: [Color] - [Why this color for this audience]
  Example: Turquoise/blue evokes professionalism and trust (important for security products)

## Typography Direction
- Headlines: [Font family, weight, style]
- Body: [Font family, size range]

Research Sources:

  • Dribbble (search "[industry] SaaS landing page")
  • Awwwards
  • SaaS Landing Page examples
  • Competitor sites

4. Section-Specific Mood Boards

What: Detailed specs for each section - the "Frankenstein" approach. Purpose: Gives AI precise visual direction for every section.

markdown
# Hero Section Specs

## Layout Reference
- URL: [Reference site]
- Screenshot: [embedded]
- What to Copy:
  - Text alignment: [left/center/right]
  - Font hierarchy
  - Button placement

## Navigation Bar
### Components
- Logo: [Position, size]
- Menu Links: [Style, hover effects]
- CTA Button: [Shape, color, glow effects]

### Code Reference (from component library)
```tsx
// Include actual component code from shadcn/21st.dev

Hero Content Area

Layout
  • [Left/Right/Center aligned]
  • [Split layout description]
3D Element (if applicable)
  • Source: [Three.js / Sketchfab link]
  • Position: [Where in layout]
  • Animation: [Type of movement]
  • Code:
tsx
// Include Three.js or animation code

Components from Libraries

Primary Button
  • Source: 21st.dev
  • Style: [pill shaped, glow outline, etc.]
  • Code:
tsx
// Component code
Background Effects
  • Type: [Gradient, particles, grid, etc.]
  • Source: [Library link]
  • Code:
tsx
// Effect code

Animations

  • Scroll Effects: [Parallax, fade-in, etc.]
  • Hover States: [What elements animate]
  • Entrance Animations: [Staggered, sequential, etc.]

**Critical**: Be VERY granular. This is where premium separates from generic.

---

### 5. Style Guide (Living Document)
**What**: Single source of truth for all design specs.
**Purpose**: Ensures consistency across the entire project.

```markdown
# Style Guide

## Design Philosophy
[Brief statement about the visual approach]

## Target Audience
[Who this design serves]

## Color Palette

### Primary
- Main: #[hex] - [Usage: CTAs, key highlights]
- Light: #[hex] - [Usage: hover states]
- Dark: #[hex] - [Usage: pressed states]

### Neutral
- Background: #[hex]
- Surface: #[hex]
- Border: #[hex]
- Text Primary: #[hex]
- Text Secondary: #[hex]

### Accent
- Success: #[hex]
- Warning: #[hex]
- Error: #[hex]

### Do's and Don'ts
DO: [Guidance]
DON'T: [Anti-patterns]

## Typography

### Font Families
- Headlines: [Font name], [fallbacks]
- Body: [Font name], [fallbacks]
- Monospace: [Font name] (for code)

### Scale
- Display: [size]px / [line-height]
- H1: [size]px / [line-height]
- H2: [size]px / [line-height]
- H3: [size]px / [line-height]
- Body: [size]px / [line-height]
- Small: [size]px / [line-height]

## Spacing System
- xs: [value]
- sm: [value]
- md: [value]
- lg: [value]
- xl: [value]
- 2xl: [value]

## Border Radius
- sm: [value]
- md: [value]
- lg: [value]
- full: 9999px

## Shadows
[Shadow definitions]

## Animation
- Duration: [fast/medium/slow values]
- Easing: [easing functions]
- Motion Preferences: Respect prefers-reduced-motion

## Component Patterns
[Common patterns used across the site]

Important: This is a LIVING document. AI should update it as learnings emerge.


6. Project Requirements Document (PRD)

What: Technical specification for the entire project. Purpose: Tells AI exactly what tech to use and how.

markdown
# Project Requirements Document

## Project Overview
[Brief description]

## Tech Stack
- Framework: [Next.js / Remix / etc.]
- Styling: [Tailwind CSS / CSS Modules / etc.]
- UI Components: [shadcn/ui, Radix, etc.]
- Animation: [Framer Motion / GSAP / etc.]
- 3D: [Three.js / React Three Fiber]
- Icons: [Lucide / Heroicons / etc.]

## Dependencies
```json
{
  "dependencies": {
    // List all required packages
  }
}

File Structure

src/
├── app/
│   └── page.tsx
├── components/
│   ├── ui/           # shadcn components
│   ├── sections/     # Page sections
│   └── 3d/           # Three.js components
├── lib/
│   └── utils.ts
└── styles/
    └── globals.css

Design System

  • See: style-guide.md

Page Sections

SectionSpec FilePriority
Herohero-section.mdP0
Featuresfeatures-section.mdP1
[etc.][etc.][etc.]

Responsiveness

  • Mobile: 320px - 767px
  • Tablet: 768px - 1023px
  • Desktop: 1024px+

Performance Requirements

  • LCP: < 2.5s
  • FID: < 100ms
  • CLS: < 0.1

Accessibility

  • WCAG 2.1 AA compliance
  • Keyboard navigation
  • Screen reader support

---

### 7. Tasks Document
**What**: Step-by-step implementation plan.
**Purpose**: Gives AI a clear execution path.

```markdown
# Implementation Tasks

## Phase 1: Project Setup
- [ ] Initialize Next.js project
- [ ] Install dependencies
- [ ] Configure Tailwind CSS
- [ ] Set up shadcn/ui
- [ ] Create folder structure
- [ ] Configure fonts
- [ ] Set up color variables

## Phase 2: Core Components
- [ ] Build navigation bar
- [ ] Create button variants
- [ ] Set up typography components
- [ ] Create layout components

## Phase 3: Section Building
- [ ] Build Hero section
- [ ] Build Trust Logos section
- [ ] Build Features section
- [ ] [Continue for each section]

## Phase 4: Polish
- [ ] Add animations
- [ ] Optimize images
- [ ] Add loading states
- [ ] Mobile responsiveness pass
- [ ] Accessibility audit

## Phase 5: Launch
- [ ] Performance optimization
- [ ] SEO metadata
- [ ] Final review

Component Resources

shadcn/ui

The foundational component library. Copy-paste components with full customization.

21st.dev

Premium components built on top of shadcn/ui.

  • Website: https://21st.dev
  • Usage: Advanced components with animations
  • Key Feature: Each component includes:
    • Preview
    • Code to copy
    • AI prompt for installation
Three.js / React Three Fiber

3D graphics in the browser.

Show full SKILL.md (293 more words)Show less
Sketchfab

Community 3D models and animations.


Best Practices

1. Section Isolation

Start a new chat for each section change:

  • Cleaner context (no pollution from other sections)
  • Cheaper (fewer tokens consumed)
  • More focused results
2. Commit Per Section

After each section is complete:

bash
git add .
git commit -m "feat(landing): add [section-name] section"

This allows easy rollback if iterations go wrong.

3. Include Reference Images

Always paste screenshots in your prompts:

  • AI can see exactly what you want
  • Reduces ambiguity
  • Faster convergence on the right design
4. Include Component Code

When specifying a component from 21st.dev or shadcn:

  • Copy the actual code
  • Include it in your section spec
  • AI can implement it exactly
5. Auto-Update Style Guide

Create a rule file:

markdown
# .cursorrules or similar

When building a section and making design decisions that differ from
the style guide, automatically update the style guide to reflect the
new learnings.
6. Screenshot-to-Iteration

When requesting changes:

  1. Take a screenshot of the current state
  2. Paste it in the prompt
  3. Describe what to change
  4. Reference the original inspiration if needed

The $500 vs $5000 Difference

Generic AI OutputPremium Framework Output
No contextFull context artifacts
Guessing what you wantFollowing precise specs
Inconsistent stylingLiving style guide
Random componentsCurated component library
No visual referencesMood boards + screenshots
Build everything at onceSection-by-section isolation
No iteration loopDefine → Build → Review → Refine

Prompt Templates

Generate Style Guide
Based on my mood board and design preferences in [website-sections folder]
and in the [product-brief.md], create a style guide that includes:
- Color palette (with usage guidance)
- Typography scale
- Component styles
- Spacing system
- Animation guidelines

This will be our single source of truth for the entire project.
Do not duplicate content from the section specs.
Generate PRD
Based on my [product-brief.md], [style-guide.md], and all section specs
in [website-sections], create a Project Requirements Document that includes:
- Project overview
- Tech stack (extract from component code in specs)
- Dependencies (extract from component libraries used)
- Design system reference
- Page sections with file references
- File structure
- Responsiveness requirements
- Performance requirements
Generate Tasks
Based on the [style-guide.md] and [prd.md], create a tasks markdown file with:
- Phase 1: Project setup tasks
- Phase 2: Core component tasks
- Phase 3: Section building tasks (one per section)
- Phase 4: Polish tasks
- Phase 5: Launch tasks

Each task should be a checkbox item.
Reference the specific spec files for each section.
Build a Section
Build the [Section Name] section.

Reference files:
- Style guide: @style-guide.md
- Section spec: @[section-name]-section.md
- PRD: @prd.md

Follow the design specs exactly.
Use the components specified.
Match the reference images.
Iterate on a Section
[Paste screenshot of current state]

Changes needed:
1. [Specific change 1]
2. [Specific change 2]

Reference the original inspiration: [paste reference image]

Attribution

This framework is derived from the video "How I Build Premium $5k SaaS Websites with AI" by BuilderSpace (December 2025), which documents a 10-year professional design workflow adapted for AI-assisted development.

Source: https://www.youtube.com/watch?v=WqSf0noa4hk


"The prep work feels like work. You just want to start building. But that upfront context - the brief, the mood boards, the style guide, the section specs - that's what separates a $500 generic website from a $5,000 premium polished one."

© HermeticOrmus, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/design-mastery/skills/premium-saas-design of HermeticOrmus/LibreUIUX-Claude-Code.

Open the folder on GitHubat commit 41a968c

Compare with similar skills

Premium SaaS Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Premium SaaS Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Premium SaaS Design this skillHermeticOrmus/LibreUIUX-Claude-Code112—~3.3kAutomated safety check: PassMIT
Product Skillsalirezarezvani/claude-skills28k—~2.6kAutomated safety check: PassMIT
Web Designxiaopu-ai/web-design783—~3kAutomated safety check: PassMIT
Hai Visual Explainerhylarucoder/hai-stack386—~2kAutomated safety check: PassCustom licence
Screenshot Feature Extractordavila7/claude-code-templates33k1 repos~1.1kAutomated safety check: PassMIT
Impeccablebestofjs/bestofjs3.1k26 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • Product Skills

    alirezarezvani/claude-skills

    A skill your agent uses when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery…

    28k GitHub stars~2.6k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • Web Design

    xiaopu-ai/web-design

    Web 视觉设计 SKILL。输入 PRD / 参考 URL / 截图 / 关键词(任意组合),先产出一份标准化 DESIGN.md 设计规范,用户确认后据此生成 UI/UX、视觉、动效、响应式全部达标的 web 代码。专攻 web 端:Landing Page、Portfolio、产品页、博客、个人站、SaaS 介绍页等。当用户说"帮我做个网站""设计一个页面""参考 XX…

    783 GitHub stars~3k tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • Hai Visual Explainer

    hylarucoder/hai-stack

    Turns supplied content into self-contained HTML and PNG in two modes: card for one shareable frame(知识卡、信息卡、金句卡、封面、把要点做成一张图), report for multi-section documents(可视化报告、HTML 汇报页、PRD/计划/评审做成网页).

    386 GitHub stars~2k tokensUpdated 6 days ago
    Frontend & DesignAuto-check passed
  • Screenshot Feature Extractor

    davila7/claude-code-templates

    Analyze product screenshots to extract feature lists and generate development task checklists.

    33k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 26 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Scroll World Landing Page

    oso95/scroll-world

    Builds a scroll-driven landing page where a pre-rendered camera flies through connected AI-generated scenes, using Higgsfield for stills and video clips.

    9.9k GitHub starsUsed in 1 repo~12k tokens
    Frontend & DesignAuto-check: notes

More from HermeticOrmus/LibreUIUX-Claude-Code

All 15 skills in this repo
  • Deployment Pipeline Design

    HermeticOrmus/LibreUIUX-Claude-Code

    Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration.

    112 GitHub starsUsed in 11 repos~2.1k tokens
    Auto-check passed
  • Multi Cloud Architecture

    HermeticOrmus/LibreUIUX-Claude-Code

    Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP.

    112 GitHub starsUsed in 11 repos~1.2k tokens
    Auto-check passed
  • Archetypal Combinations

    HermeticOrmus/LibreUIUX-Claude-Code

    Rules and worked examples for combining an archetype (structure and behavior) with a Major Arcana card (color and mood) into one coherent design system.

    112 GitHub stars~3.4k tokensUpdated 6 days ago
    Auto-check passed
  • Langchain Architecture

    HermeticOrmus/LibreUIUX-Claude-Code

    Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns.

    112 GitHub starsUsed in 10 repos~2.5k tokens
    Auto-check passed
  • Brand Systems

    HermeticOrmus/LibreUIUX-Claude-Code

    Brand identity building blocks: positioning, personality, archetypes, logo systems, color palettes, type pairing, voice, and guidelines documentation.

    112 GitHub stars~2.3k tokensUpdated 6 days ago
    Auto-check passed
  • Design Principles

    HermeticOrmus/LibreUIUX-Claude-Code

    Core visual design principles (visual hierarchy, Gestalt grouping, composition, balance, contrast, white space, color, typography) with UI fixes, a checklist, and deep-dive references.

    112 GitHub stars~2k tokensUpdated 6 days ago
    Auto-check passed

Questions about Premium SaaS Design

What does Premium SaaS Design do?

The Define, Build, Review, Refine loop and seven context artifacts (brief, content, mood boards, section specs, style guide, PRD, tasks) for building a premium SaaS marketing site with AI. Premium SaaS Design is an agent skill from HermeticOrmus/LibreUIUX-Claude-Code. The Define, Build, Review, Refine loop and seven context artifacts (brief, content, mood boards, section specs, style guide, PRD, tasks) for building a premium SaaS marketing site with AI.

When should I use Premium SaaS Design?

Premium SaaS Design fits situations like: building a SaaS landing page and you want the design context written down before any code; tasks that involve Landing pages; tasks that involve PRD writing.

How do I install Premium SaaS Design in Claude Code?

Run `npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a claude-code`. Or copy the skill folder (plugins/design-mastery/skills/premium-saas-design in HermeticOrmus/LibreUIUX-Claude-Code) into .claude/skills/premium-saas-design in your project. Claude Code loads it when a task matches its description.

How do I install Premium SaaS Design in Codex?

Run `npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a codex`. Or copy the skill folder (plugins/design-mastery/skills/premium-saas-design in HermeticOrmus/LibreUIUX-Claude-Code) into .agents/skills/premium-saas-design in your project. Codex loads it when a task matches its description.

Can I use Premium SaaS Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/premium-saas-design, .gemini/skills/premium-saas-design, .github/skills/premium-saas-design and .opencode/skills/premium-saas-design in your project.

What does Premium SaaS Design need to run?

Going by SKILL.md and its folder, Premium SaaS Design needs the command-line tools its instructions call (git).

Does Premium SaaS Design access the network?

SKILL.md names 5 domains. As links in the text: ui.shadcn.com, 21st.dev, threejs.org, sketchfab.com and youtube.com. This is read from the text; nothing was executed.

Is Premium SaaS Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Premium SaaS Design use?

Premium SaaS Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Premium SaaS Design use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Premium SaaS Design?

Skills that share tags, products or a category with Premium SaaS Design: Product Skills (alirezarezvani/claude-skills, 28k stars), Web Design (xiaopu-ai/web-design, 783 stars), Hai Visual Explainer (hylarucoder/hai-stack, 386 stars) and Screenshot Feature Extractor (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Premium SaaS Design?

HermeticOrmus (a GitHub user) maintains it in HermeticOrmus/LibreUIUX-Claude-Code, which has 112 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 4, 2026.

Source: HermeticOrmus/LibreUIUX-Claude-Code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.