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…
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.
$ npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code premium-saas-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "premium-saas-design" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/plugins/design-mastery/skills/premium-saas-design into .claude/skills/premium-saas-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premium-saas-design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/plugins/design-mastery/skills/premium-saas-designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code premium-saas-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/design-mastery/skills/premium-saas-design .agents/skills/premium-saas-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "premium-saas-design" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/plugins/design-mastery/skills/premium-saas-design into .agents/skills/premium-saas-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premium-saas-design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code premium-saas-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/design-mastery/skills/premium-saas-design .cursor/skills/premium-saas-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "premium-saas-design" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/plugins/design-mastery/skills/premium-saas-design into .cursor/skills/premium-saas-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premium-saas-design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git --path plugins/design-mastery/skills/premium-saas-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code premium-saas-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/design-mastery/skills/premium-saas-design .gemini/skills/premium-saas-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "premium-saas-design" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/plugins/design-mastery/skills/premium-saas-design into .gemini/skills/premium-saas-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premium-saas-design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code premium-saas-designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/design-mastery/skills/premium-saas-design .github/skills/premium-saas-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "premium-saas-design" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/plugins/design-mastery/skills/premium-saas-design into .github/skills/premium-saas-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premium-saas-design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill premium-saas-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code premium-saas-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/design-mastery/skills/premium-saas-design .opencode/skills/premium-saas-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "premium-saas-design" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/plugins/design-mastery/skills/premium-saas-design into .opencode/skills/premium-saas-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premium-saas-design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
premium-saas-designThe 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. 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.
11 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 41a968c. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
ui.shadcn.com21st.devthreejs.orgsketchfab.comyoutube.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from HermeticOrmus/LibreUIUX-Claude-Code at commit 41a968c, republished under its MIT licence (© HermeticOrmus). 743 words, ~3,335 tokens.
.claude/skills/premium-saas-design/SKILL.md (or your agent's skills folder).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.
DEFINE → BUILD → REVIEW → REFINE
↑ │
└────────────────────────┘This loop is everything. It's used by real product teams and works wonders with AI.
AI needs context to produce premium results. These 7 documents form your "design contract" with AI:
What: Single document explaining what you're building, why, and for whom. Purpose: Gives AI direction and understanding of the project.
# 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.
What: Separate file for each section containing all copy/content. Purpose: Focuses AI on content separately from design.
# 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.]What: Visual inspiration for the overall site aesthetic. Purpose: Answers "What should the whole site FEEL like when we land on it?"
# 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:
What: Detailed specs for each section - the "Frankenstein" approach. Purpose: Gives AI precise visual direction for every section.
# 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// Include Three.js or animation code// Component code// Effect code
**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.
What: Technical specification for the entire project. Purpose: Tells AI exactly what tech to use and how.
# 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
}
}src/
├── app/
│ └── page.tsx
├── components/
│ ├── ui/ # shadcn components
│ ├── sections/ # Page sections
│ └── 3d/ # Three.js components
├── lib/
│ └── utils.ts
└── styles/
└── globals.css| Section | Spec File | Priority |
|---|---|---|
| Hero | hero-section.md | P0 |
| Features | features-section.md | P1 |
| [etc.] | [etc.] | [etc.] |
---
### 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 reviewThe foundational component library. Copy-paste components with full customization.
Premium components built on top of shadcn/ui.
3D graphics in the browser.
Community 3D models and animations.
Start a new chat for each section change:
After each section is complete:
git add .
git commit -m "feat(landing): add [section-name] section"This allows easy rollback if iterations go wrong.
Always paste screenshots in your prompts:
When specifying a component from 21st.dev or shadcn:
Create a rule file:
# .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.When requesting changes:
| Generic AI Output | Premium Framework Output |
|---|---|
| No context | Full context artifacts |
| Guessing what you want | Following precise specs |
| Inconsistent styling | Living style guide |
| Random components | Curated component library |
| No visual references | Mood boards + screenshots |
| Build everything at once | Section-by-section isolation |
| No iteration loop | Define → Build → Review → Refine |
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.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 requirementsBased 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 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.[Paste screenshot of current state]
Changes needed:
1. [Specific change 1]
2. [Specific change 2]
Reference the original inspiration: [paste reference image]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
Just SKILL.md in plugins/design-mastery/skills/premium-saas-design of HermeticOrmus/LibreUIUX-Claude-Code.
Open the folder on GitHubat commit 41a968c
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Premium SaaS Design this skillHermeticOrmus/LibreUIUX-Claude-Code | 112 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Product Skillsalirezarezvani/claude-skills | 28k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Web Designxiaopu-ai/web-design | 783 | — | ~3k | Automated safety check: Pass | MIT | |
| Hai Visual Explainerhylarucoder/hai-stack | 386 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Screenshot Feature Extractordavila7/claude-code-templates | 33k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT |
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…
xiaopu-ai/web-design
Web 视觉设计 SKILL。输入 PRD / 参考 URL / 截图 / 关键词(任意组合),先产出一份标准化 DESIGN.md 设计规范,用户确认后据此生成 UI/UX、视觉、动效、响应式全部达标的 web 代码。专攻 web 端:Landing Page、Portfolio、产品页、博客、个人站、SaaS 介绍页等。当用户说"帮我做个网站""设计一个页面""参考 XX…
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/计划/评审做成网页).
davila7/claude-code-templates
Analyze product screenshots to extract feature lists and generate development task checklists.
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…
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.
HermeticOrmus/LibreUIUX-Claude-Code
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration.
HermeticOrmus/LibreUIUX-Claude-Code
Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP.
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.
HermeticOrmus/LibreUIUX-Claude-Code
Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns.
HermeticOrmus/LibreUIUX-Claude-Code
Brand identity building blocks: positioning, personality, archetypes, logo systems, color palettes, type pairing, voice, and guidelines documentation.
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.
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.
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.
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.
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.
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.
Going by SKILL.md and its folder, Premium SaaS Design needs the command-line tools its instructions call (git).
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.
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.
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.
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.
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.
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.