跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 heroui-native

Heroui Native

HeroUI 原生组件库用于回放原生(Tailwind v4通过Uniwind). 与 HeroUI 本地创建移动 UI 时使用 – 创建按钮,卡片,文本字段,对话框; 安装 heroui-native; 配置暗/光主题; 或获取组件 docs 。 关键词 : 英雄UI原生地,她的同源地,反应原生地UI,Uniwind,移动组件.

10548 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

HeroUI 本地组件库用于 React Industrial (通过 Uniwind 的 Tailwind v4)

何时用

与 HeroUI 原生创建移动 UI —— 创建按钮,卡片,文本字段,对话框; 安装 heroui-native ; 配置暗/光主题; 或获取组件文件 。 关键词 : 英雄UI 原生,她的同源, 反应原生UI, Uniwind, 移动组件

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:HeroUI Native Development Guide、Installation、CRITICAL: Native Only - Do Not Use Web Patterns、Core Principles、Accessing Documentation & Component Information、Using Scripts。

文件分析

文件分析:除 SKILL.md 外,正文引用了 scripts/list_components.mjs、scripts/get_component_docs.mjs、scripts/get_theme.mjs、scripts/get_docs.mjs,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

HeroUI Native component library for React Native (Tailwind v4 via Uniwind). Use when building mobile UIs with HeroUI Native — creating Buttons, Cards, TextFields, Dialogs; installing heroui-native; configuring dark/light themes; or fetching component docs. Keywords: HeroUI Native, heroui-native, React Native UI, Uniwind, mobile components.

HeroUI Native Development GuideInstallationCRITICAL: Native Only - Do Not Use Web PatternsCore PrinciplesAccessing Documentation & Component InformationUsing ScriptsList all available componentsGet component documentation (MDX)Get theme variablesGet non-component docs (guides, releases)Direct MDX URLsInstallation Essentials

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
heroui-native
description
HeroUI Native component library for React Native (Tailwind v4 via Uniwind). Use when building mobile UIs with HeroUI Native — creating Buttons, Cards, TextFields, Dialogs; installing heroui-native; configuring dark/light themes; or fetching component docs. Keywords: HeroUI Native, heroui-native, React Native UI, Uniwind, mobile components.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 4
  • scripts/list_components.mjs
  • scripts/get_component_docs.mjs
  • scripts/get_theme.mjs
  • scripts/get_docs.mjs

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「heroui-native」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-b1dae020b0b37eea-Heroui-Native.html
请存为 .cursor/skills/heroui-native/SKILL.md 或 .claude/skills/heroui-native/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/heroui-inc/heroui 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/heroui-inc/heroui' --list

npx skills add 'https://github.com/heroui-inc/heroui' --skill 'heroui-native'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: heroui-native description: "HeroUI Native component library for React Native (Tailwind v4 via Uniwind). Use when building mobile UIs with HeroUI Native — creating Buttons, Cards, TextFields, Dialogs; installing heroui-native; configuring dark/light themes; or fetching component docs. Keywords: HeroUI Native, heroui-native, React Native UI, Uniwind, mobile components." metadata: author: heroui version: "2.0.1" --- # HeroUI Native Development Guide HeroUI Native is a component library built on **Uniwind (Tailwind CSS for React Native)** and **React Native**, providing accessible, customizable UI components for mobile applications. --- ## Installation ```bash curl -fsSL https://heroui.com/install | bash -s heroui-native ``` --- ## CRITICAL: Native Only - Do Not Use Web Patterns **This guide is for HeroUI Native ONLY.** Do NOT apply HeroUI React (web) patterns — the package, styling engine, and color format all differ: | Feature | React (Web) | Native (Mobile) | | ------------ | -------------------- | ----------------------------------- | | **Styling** | Tailwind CSS v4 | Uniwind (Tailwind for React Native) | | **Colors** | oklch format | HSL format | | **Package** | `@heroui/react` | `heroui-native` | | **Platform** | Web browsers | iOS & Android | ```tsx // CORRECT — Native pattern import { Button } from "heroui-native"; console.log("Pressed!")}> Click me ; ``` **Always fetch Native docs before implementing.** --- ## Core Principles - Semantic variants (`primary`, `secondary`, `tertiary`) over visual descriptions - Composition over configuration (compound components) - Theme variables with HSL color format - React Native StyleSheet patterns with Uniwind utilities --- ## Accessing Documentation & Component Information **For component details, examples, props, and implementation patterns, always fetch documentation:** ### Using Scripts ```bash # List all available components node scripts/list_components.mjs # Get component documentation (MDX) node scripts/get_component_docs.mjs Button node scripts/get_component_docs.mjs Button Card TextField # Get theme variables node scripts/get_theme.mjs # Get non-component docs (guides, releases) node scripts/get_docs.mjs /docs/native/getting-started/theming ``` ### Direct MDX URLs Component docs: fetch `.mdx` with a concrete kebab-case slug. Run `node scripts/list_components.mjs` when the slug is unknown, and never fetch a URL that still contains a placeholder. Examples: - Button: `https://heroui.com/docs/native/components/button.mdx` - Dialog: `https://heroui.com/docs/native/components/dialog.mdx` - TextField: `https://heroui.com/docs/native/components/text-field.mdx` Getting started guides: use a concrete topic URL such as `https://heroui.com/docs/native/getting-started/quick-start.mdx`. **Important:** Always fetch component docs before implementing. The MDX docs include complete examples, props, anatomy, and API references. --- ## Installation Essentials ### Quick Install ```bash npm i heroui-native react-native-reanimated react-native-gesture-handler react-native-safe-area-context @gorhom/bottom-sheet react-native-svg react-native-worklets tailwind-merge tailwind-variants ``` ### Framework Setup (Expo - Recommended) 1. **Install dependencies:** ```bash npx create-expo-app MyApp cd MyApp npm i heroui-native uniwind tailwindcss npm i react-native-reanimated react-native-gesture-handler react-native-safe-area-context @gorhom/bottom-sheet react-native-svg react-native-worklets tailwind-merge tailwind-variants ``` 2. **Create `global.css`:** ```css @import "tailwindcss"; @import "uniwind"; @import "heroui-native/styles"; @source "./node_modules/heroui-native/lib"; ``` 3. **Wrap app with providers:** ```tsx import { GestureHandlerRootView } from "react-native-gesture-handler"; import { HeroUINativeProvider } from "heroui-native"; import "./global.css"; export default function Layout() { return ( ); } ``` ### Critical Setup Requirements 1. **Uniwind is Required** - HeroUI Native uses Uniwind (Tailwind CSS for React Native) 2. **HeroUINativeProvider Required** - Wrap your app with `HeroUINativeProvider` 3. **GestureHandlerRootView Required** - Wrap with `GestureHandlerRootView` from react-native-gesture-handler 4. **Use Compound Components** - Components use compound structure (e.g., `Card.Header`, `Card.Body`) 5. **Use onPress, not onClick** - React Native uses `onPress` event handlers 6. **Platform-Specific Code** - Use `Platform.OS` for iOS/Android differences --- ## Component Patterns HeroUI Native uses **compound component patterns**. Each component has subcomponents accessed via dot notation. **Example - Card:** ```tsx {/* Icons, badges */} Title Description {/* Actions */} ``` **Key Points:** - Always use compound structure - don't flatten to props - Subcomponents are accessed via dot notation (e.g., `Card.Header`) - Native Card uses `Card.Body` (not `Card.Content`); Title and Description go inside Body - **Fetch component docs for complete anatomy and examples** --- ## Semantic Variants HeroUI uses semantic naming to communicate functional intent: | Variant | Purpose | Usage | | ------------- | --------------------------------- | -------------- | | `primary` | Main action to move forward | 1 per context | | `secondary` | Alternative actions | Multiple | | `tertiary` | Dismissive actions (cancel, skip) | Sparingly | | `danger` | Destructive actions | When needed | | `danger-soft` | Soft destructive actions | Less prominent | | `ghost` | Low-emphasis actions | Minimal weight | | `outline` | Secondary actions | Bordered style | **Don't use raw colors** - semantic variants adapt to themes and accessibility. --- ## Theming HeroUI Native uses CSS variables via Tailwind/Uniwind for theming. Theme colors are defined in `global.css`: ```css @theme { --color-accent: hsl(260, 100%, 70%); --color-accent-foreground: hsl(0, 0%, 100%); } ``` **Get current theme variables:** ```bash node scripts/get_theme.mjs ``` **Access theme colors programmatically:** ```tsx import { useThemeColor } from "heroui-native"; const accentColor = useThemeColor("accent"); ``` **Theme switching (Light/Dark Mode):** ```tsx import { Uniwind, useUniwind } from "uniwind"; const { theme } = useUniwind(); Uniwind.setTheme(theme === "light" ? "dark" : "light"); ``` For detailed theming, fetch: `https://heroui.com/docs/native/getting-started/theming.mdx`

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…