Token导航 LogoToken导航

Agent Skill · 研究检索

cleanui(cleanui 搜索)

cleanui 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

cleanui 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 56,238。

总安装 461周安装 19GitHub Stars 4下载 150核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:cleanui(cleanui 搜索)
来源仓库:https://github.com/peterhdd/cleanui
仓库路径:skills/cleanui
安装命令:
npx skills add https://github.com/peterhdd/cleanui --skill cleanui
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/peterhdd/cleanui --skill cleanui

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

cleanui 强制生成符合专业 UI 设计规范的界面,避免常见“AI 感”视觉问题。适用于需要高质量前端输出、品牌一致性强的产品设计或客户交付场景。内置 HARD NO LIST 禁止模式,如过度使用阴影、渐变或特定布局结构。使用前请确认设计系统与颜色规范已定义,避免生成偏离品牌标准的界面。

建议结合 Figma 或 Sketch 参考图使用,确保输出贴近人类设计师水准。

来源仓库内路径:skills/cleanui

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/peterhdd/cleanui --skill cleanui;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

cleanui 怎么安装?

在终端执行 npx skills add https://github.com/peterhdd/cleanui --skill cleanui。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

cleanui 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

cleanui 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

cleanui 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

cleanui 用的人多吗?

公开数据是累计安装 461 次,近一周安装 19 次,下载 150 次,GitHub 4 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

cleanui 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
cleanui

cleanui 搜索 · 本页

4614只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

CleanUI — AI UI Design Enforcement Skill

STOP. Before you write ANY UI code, read this file. You are an AI code generator with deeply ingrained UI habits that produce recognizable "AI-looking" output. This skill exists to override those habits and produce professional, human-designed interfaces. Your process for every UI task: 1. Think about what you would NORMALLY generate 2. Check each element against the HARD NO list below 3. Replace every violation with the specified alternative 4. Only then write the code

HARD NO LIST — AUTOMATIC FAIL PATTERNS

If your output contains ANY of these, stop and fix before returning code.

Typography

  • BANNED: font-extrabold (800), font-black (900), fontWeight: "800", fontWeight: "900"
  • USE INSTEAD: font-bold (700) max. font-semibold (600) for section headings.
  • SELF-CHECK: Search your code for "extrabold" and "black". Replace all with "bold".

Logo / Trust Bars

  • BANNED: Company names as identical plain text in identical bordered pills/boxes
  • USE INSTEAD: Make each logo visually distinct — pair icons with names, vary weight/italic/tracking per logo, or use SVG logos
  • SELF-CHECK: Do all logos look identical? Fix it.

Uppercase / Letter Spacing

  • BANNED: tracking-[0.18em], tracking-[0.2em], tracking-[0.24em] or any custom wide letter-spacing
  • BANNED: More than 2 uppercase tracked labels on the entire page
  • USE INSTEAD: Sentence case. If uppercase needed, tracking-wider (0.05em) max.

Eyebrow Badges

  • BANNED: Decorative pill/badge above headlines that restates what the headline says (e.g., "AI writing system for content teams")
  • USE INSTEAD: Remove entirely, or use factual info: "Now in beta", "Trusted by 2,400 teams", "Free plan available"

Hero Headlines

  • BANNED: Headlines wrapping to 4+ lines on desktop
  • USE INSTEAD: 4-8 words, max 2 lines. Rewrite shorter.
  • BANNED: Subtitle longer than 2 sentences
  • USE INSTEAD: 1-2 short sentences max.

Decorative Copy

  • BANNED: Ornamental labels like "Live pulse", "Night shift", "Operational clarity without the clutter"
  • USE INSTEAD: Real data (status, counts, dates) or remove entirely. Every label must serve a function.

Shadows

  • BANNED: shadow-xl, shadow-2xl, blur above 8px on cards
  • USE INSTEAD: shadow-sm or shadow-none with subtle border.

Border Radius

  • BANNED: Random mixing of rounded-md, rounded-xl, rounded-2xl, rounded-3xl, rounded-[24px], rounded-[32px]
  • USE INSTEAD: Pick 2-3 values. Cards: 8-12px. Buttons: 6-8px (or rounded-full for pills). Inputs: 6-8px. Be consistent.

Icons

  • BANNED: Unicode characters as icons (↑, ↓, ◌, ⌂, ◫)
  • USE INSTEAD: lucide-react (web), @expo/vector-icons (React Native), SF Symbols (iOS), Material Icons (Android)

File Structure

  • BANNED: Entire app in a single file
  • USE INSTEAD: Separate: screens/pages, components, constants/theme, data, navigation

LAYOUT RULES

Match Layout to Content Type

Content TypeLayoutDon't Use
Images/visual (food, travel, products)Horizontal carousels, image grids, hero imagesText-only vertical lists
Data/numbers (finance, fitness, analytics)Stat cards, progress bars, metric gridsHero image cards
Feed (social, news, posts)Full-width stacking cards, infinite scrollSectioned layout with drag handles
Items to browse (e-commerce, tasks, email)Vertical list with search/filtersHero sections
Multimedia (streaming, music, podcasts)Horizontal scroll shelves (Netflix-style)Vertical lists
Chat/messagesContact list + chat detailHero cards or stat grids
Maps/locationMap view + bottom sheet overlayStandard list layout

Anti-Templating Rules

  • NEVER use the same layout skeleton for every app. Read the prompt, identify the content type, pick the right layout.
  • NEVER use ALL of these together: hero card + grid buttons + drag handle + segmented control + vertical list. That's a template.
  • If the app is image-heavy, show actual images — thumbnails, photos — not just icons in rounded squares.
  • Use horizontal scrolls (FlatList horizontal, CSS overflow-x-auto) for categories, featured items, content shelves. AI generators underuse these.

DESIGN TASTE

Color Restraint

  • Monochrome or near-monochrome palettes often look better than colorful ones.
  • Color should appear mainly in actions (buttons, links), status (badges), and highlights (selected states). Not on everything.
  • Dark elements (cards, sections) are justified ONLY when they represent a real-world object (credit card, media player, code block) or create deliberate visual rhythm. Not just "for variety."

List Items

  • NEVER use letter initials as the only identifier. Use category-specific icons (utensils for restaurant, bus for transport, repeat for subscription) in rounded squares.
  • Always include metadata: date/time, category, status. "Restaurant" feels fake. "Restaurant · May 5 · 14:28" feels real.

Filters

  • Any list with 5+ items should have a filter or segmented control.
  • Segmented control: pill-track style with solid fill on selected segment.

Action Buttons

  • Borderless style often looks cleaner: icon in muted-background square + label below. No card wrapper, no shadow, no border needed.

MOBILE RULES

See Mobile Patterns Reference for full iOS color palettes, Android Material 3 tokens, component guidelines, and code examples.

All Platforms

  • Use real navigation libraries, not custom View-based nav bars. React Native: @react-navigation/bottom-tabs. iOS: TabView. Android: Material NavigationBar.
  • NEVER build floating pill-shaped bottom nav bars. No position: absolute, no borderRadius: 28, no dark floating pill.
  • Use Platform.select() or Platform.OS for conditional styling in React Native.
  • Define design tokens (colors, spacing, radii, typography) in a constants file.
  • Handle 3 states per screen: loading (skeletons), content, empty.

iOS

  • Quiet, soft, premium. Restrained color. System fonts (SF Pro). Semantic colors (.label, .secondaryLabel, .systemBackground). Translucent nav/tab bars. listStyle(.insetGrouped). SF Symbols for icons. Hairline separators. Corner radius: 10-12. No heavy shadows — use background contrast.

Android (Material 3)

  • Structured, bold, expressive. Material components from material3. Tonal surfaces (tonalElevation) instead of drop shadows. Scaffold with TopAppBar + NavigationBar. ListItem composable for list rows. HorizontalDivider() between items. Corner radius: 12dp for cards. Generate color scheme from seed color.

React Native / Expo

  • Platform-conditional colors, shadows, and spacing via Platform.select().
  • iOS uses shadowColor/shadowOpacity/shadowRadius. Android uses elevation.
  • Different background colors per platform: iOS #F2F2F7, Android #F9F9FF.
  • Different primary colors: iOS #007AFF, Android uses Material seed color.

WEB RULES

Creative Freedom + Structure

You have freedom on: color palette, font choice, border radius values, brand personality, background treatments.

You must follow: section structure, hero content limits, component patterns, responsive behavior.

Navigation

  • Sticky top with backdrop-blur and semi-transparent background
  • Logo left, nav links center, CTA buttons right
  • Mobile: hamburger menu

Landing Page Structure

Hero       → headline + subtitle + 2 CTAs + one trust element
Trust      → logo bar (visually distinct logos)
Features   → 3-column grid with icons + title + description
How it works → 3-step process
Testimonials → avatar + name + role + quote
Pricing    → 2-3 tiers, featured tier visually inverted (dark bg)
CTA        → final call to action
Footer     → link columns + copyright

Hero

  • Headline + short subtitle + 2 buttons + one trust element. That's it.
  • Product mockup/screenshot on the right side of a two-column hero is fine.
  • Do NOT put stat cards, complex preview cards with lists, or multi-paragraph descriptions in the hero.

Feature Cards

  • Icon container: at least 48px with tinted background. Not tiny.
  • Card padding: generous (p-6 to p-8).
  • Each card should feel full — icon + title + description.

Pricing

  • Featured tier: inverted (dark bg, light text) or thicker border + "Most popular" badge.
  • Full-width CTA in each card.

Sign-In

  • Two-column: brand panel (left, dark) + form (right).
  • Social login above email form.
  • Mobile: hide brand panel, show form with logo.

Dashboard

  • Sidebar (240-260px) + main content.
  • Sidebar: logo, nav items with icons, optional upgrade card.
  • Top bar: search + notifications + avatar.
  • Content: greeting → stat cards → filtered list with tabs → activity feed.

Dark Mode

  • Background: very dark gray, not pure black.
  • Text: off-white, not pure white.
  • Borders: dark gray. Reduce color saturation.

PRE-OUTPUT CHECKLIST

Before returning code, verify:

Typography:

  • No font-extrabold or font-black anywhere
  • Max 2 font weights used (regular + bold/semibold)

Visual:

  • No tracking-[0.18em] or wider
  • Max 2 uppercase labels on the entire page
  • Logo bar items look visually distinct from each other
  • No shadow-xl or shadow-2xl on cards
  • Consistent border radius (2-3 values max)

Hero:

  • Headline fits in 2 lines on desktop
  • Eyebrow badge (if present) adds new info, doesn't restate headline
  • Subtitle is 1-2 sentences, not a paragraph

Structure:

  • Multiple files (screens, components, constants, navigation)
  • Real icon library (not Unicode)
  • Platform-specific styling (React Native)
  • Loading/empty states exist

Layout:

  • Layout matches content type (not the same template every time)
  • List items have category icons + metadata
  • Lists with 5+ items have filters

平台分布

Codex

36.46%
按下载量换算55

Claude

27.77%
按下载量换算42

Cursor

20.17%
按下载量换算30

Gemini CLI

8.78%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills