Token导航 LogoToken导航

Agent Skill · 前端设计

webflow-code-component%3aconvert-component(Webflow 代码 component 3aconvert component)

webflow-code-component%3aconvert-component 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

webflow-code-component%3aconvert-component 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为操作浏览器;许可证信息还不明确,暂无第三方扫描结果,按安装量在前端设计类的 10,216 个 Skill 里排第 1,552。

总安装 5,010周安装 213GitHub Stars 62下载 1,755核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/webflow/webflow-skills --skill webflow-code-component:convert-component

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网或文件读写。

涉及敏感操作时应先评估影响范围,避免误删或修改关键资源。

来源仓库内路径:skills/webflow-code-component%3Aconvert-component

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要操作浏览器,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

webflow-code-component%3aconvert-component 怎么安装?

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

webflow-code-component%3aconvert-component 支持哪些 AI 工具?

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

webflow-code-component%3aconvert-component 需要什么权限?

权限级别是操作浏览器。该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

webflow-code-component%3aconvert-component 是免费的吗?

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

webflow-code-component%3aconvert-component 用的人多吗?

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

webflow-code-component%3aconvert-component 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

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

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
webflow-code-component%3aconvert-component

Webflow 代码 component 3aconvert component · 本页

5,01062操作浏览器未明确未收录

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

SKILL.md 原文

Convert Component

Convert an existing React component into a Webflow Code Component by analyzing its structure and generating the appropriate .webflow.tsx definition file.

When to Use This Skill

Use when:

  • User has an existing React component they want to use in Webflow
  • User asks to "convert", "adapt", or "make this work with Webflow"
  • User provides a React component file and wants a Webflow definition
  • User is migrating components from another React project

Do NOT use when:

  • Creating a component from scratch (use component-scaffold)
  • User just wants to understand code components (answer directly)
  • Component is already a Webflow code component (use component-audit)

Instructions

Phase 1: Analyze Existing Component

  1. Read the React component file: Get the full source code
  2. Extract component information:

- Component name (function/const name) - Props interface or type definition - Each prop's TypeScript type - Default values if defined - Whether component uses children

  1. Identify incompatible patterns: Pattern Issue Resolution React Context usage Context doesn't work across Webflow components Refactor to props or use nano stores window/document in render SSR will fail Wrap in useEffect or set ssr: false localStorage/sessionStorage in render SSR will fail Wrap in useEffect or set ssr: false Complex object props Can't map to Webflow prop types Break into individual props Function props (callbacks) Not supported in Webflow Remove or internalize logic useContext hook Won't work across components Use alternative state patterns External CSS imports May not work in Shadow DOM Import in.webflow.tsx instead CSS class references to global styles Won't work in Shadow DOM Use component-scoped styles styled-components Needs Shadow DOM decorator Set up globals.ts with decorator Emotion (@emotion/styled) Needs Shadow DOM decorator Set up globals.ts with decorator
  2. Detect styling approach and note required setup: If using styled-components: npm i @webflow/styled-components-utils styled-components Create/update globals.ts: import {styledComponentsShadowDomDecorator} from "@webflow/styled-components-utils"; export const decorators = [styledComponentsShadowDomDecorator]; If using Emotion: npm i @webflow/emotion-utils @emotion/cache @emotion/react Create/update globals.ts: import {emotionShadowDomDecorator} from "@webflow/emotion-utils"; export const decorators = [emotionShadowDomDecorator]; For both CSS-in-JS approaches, update webflow.json: styled-components: {"library": {"globals": "./src/globals.ts", "renderer": {"server": "@webflow/styled-components-utils/server"}}} Emotion: {"library": {"globals": "./src/globals.ts", "renderer": {"server": "@webflow/emotion-utils/server"}}}
  3. Flag any dependencies that might cause issues:

- Large libraries (bundle size concern) - Browser-only libraries - Libraries that manipulate DOM directly

Phase 2: Map Props to Webflow Types

  1. Apply TypeScript → Webflow prop type mapping: TypeScript Type Webflow Prop Notes string props.Text() Default for short text string (long/HTML content) props.RichText() If prop name suggests content/body/description React.ReactNode / children props.Slot() For nested content number props.Number() Numeric values boolean props.Boolean() Toggles "option1" | "option2" props.Variant() String literal unions (requires options array) enum props.Variant() Convert enum values to options array (required) {href: string;...} props.Link() Returns {href, target?, preload?} object — may need wrapper if component expects separate href/target props Image-related types props.Image() Image src, url, etc. string (canvas-editable text) props.TextNode() For text editable directly on canvas; has multiline param boolean (show/hide) props.Visibility() Semantic show/hide toggle string (for HTML id) props.Id() If prop is named "id" or used for accessibility Complex objects SPLIT Break into multiple simple props Functions/callbacks REMOVE Not supported Arrays SPECIAL May need component redesign
  2. Handle special cases: Complex object props - Break them down: // Original interface Props {author: {name: string; avatar: string; bio: string;}} // Converted to flat props props: {authorName: props.Text({name: "Author Name"}), authorAvatar: props.Image({name: "Author Avatar"}), authorBio: props.RichText({name: "Author Bio"})} Union types with more than simple strings: // Original - complex union type Size = "sm" | "md" | "lg" | {width: number; height: number}; // Convert to Variant with only string options size: props.Variant({name: "Size", options: ["sm", "md", "lg", "custom"], defaultValue: "md"}) // Note: Custom size would need additional Number props Optional props - Provide defaultValue for prop types that support it. Note: Link, Image, Slot, and Id do not accept defaultValue. // Original interface Props {title?: string;} // Converted - provide default for types that support it title: props.Text({name: "Title", defaultValue: "" // Empty string or sensible default})

Phase 3: Check Project Setup

  1. Verify Webflow setup exists:

- Check for webflow.json in project root - Check for required dependencies (@webflow/webflow-cli, @webflow/data-types, @webflow/react) - If using styled-components/Emotion, check for decorator packages - If missing, offer to set up or direct to local-dev-setup skill

  1. Determine file locations:

- Identify where the original component lives - Determine where .webflow.tsx should be created (same directory) - Check for existing styles that need to be imported

Phase 4: Generate Definition File

  1. Create the .webflow.tsx file:
import { declareComponent } from "@webflow/react";
import { props } from "@webflow/data-types";
import { ComponentName } from "./ComponentName";
// Import styles if they exist
import "./ComponentName.module.css"; // or .css

export default declareComponent(ComponentName, {
  name: "ComponentName",
  description: "[Generated from component purpose]",
  group: "[Appropriate category]",
  props: {
    // Mapped props here
  },
  // decorators: [], // Optional — per-component decorators (e.g., for CSS-in-JS Shadow DOM support)
  options: {
    applyTagSelectors: true, // Default is false. Set to true to apply Webflow's tag selectors (e.g., h1, p styles) inside the component.
    ssr: true // or false if browser APIs detected
  }
});
  1. Provide the complete file with all props mapped

Phase 5: Document Required Changes

  1. List modifications needed to the original component:
## Required Changes to [ComponentName].tsx

### Must Fix (Component won't work without these):
- [ ] Issue 1: [Description and how to fix]
- [ ] Issue 2: [Description and how to fix]

### Recommended (Will improve Webflow integration):
- [ ] Recommendation 1
- [ ] Recommendation 2

### Props Mapping Summary:
| Original Prop | Webflow Prop | Notes |
|---------------|--------------|-------|
| title: string | props.Text() | Direct mapping |
| isOpen: boolean | props.Boolean() | Direct mapping |
| data: object | SPLIT → dataTitle, dataValue | Flattened |
| onClick: function | REMOVED | Not supported |
  1. Provide modified component code if changes are needed:

- Show the updated TypeScript interface - Show any useEffect wrappers needed for SSR - Show style import changes - Note CSS-in-JS setup requirements if applicable

Examples

Example 1: Simple Component Conversion

User prompt:

Convert this React component to work with Webflow:

// TestimonialCard.tsx
interface TestimonialCardProps {
  quote: string;
  authorName: string;
  authorTitle?: string;
  rating?: number;
}

export const TestimonialCard: React.FC<TestimonialCardProps> = ({
  quote,
  authorName,
  authorTitle = "",
  rating = 5
}) => {
  return (
    <div className="testimonial-card">
      <div className="stars">{"★".repeat(rating)}</div>
      <blockquote>{quote}</blockquote>
      <div className="author">
        <strong>{authorName}</strong>
        {authorTitle && <span>{authorTitle}</span>}
      </div>
    </div>
  );
};

Response:

## Component Analysis: TestimonialCard

### Props Detected:
| Prop | TypeScript Type | Webflow Mapping |
|------|-----------------|-----------------|
| quote | string | props.Text() |
| authorName | string | props.Text() |
| authorTitle | string (optional) | props.Text() |
| rating | number (optional) | props.Number() |

### Issues Found:
- **CSS class "testimonial-card"** - Uses global class that won't work in Shadow DOM
  - Fix: Convert to CSS Modules or import scoped styles

### No blocking issues - ready to convert!

---

## Generated Files

### TestimonialCard.webflow.tsx

import { declareComponent } from "@webflow/react"; import { props } from "@webflow/data-types"; import { TestimonialCard } from "./TestimonialCard"; import "./TestimonialCard.module.css";

export default declareComponent(TestimonialCard, { name: "TestimonialCard", description: "Display customer testimonials with rating stars", group: "Display", props: { quote: props.Text({ name: "Quote", defaultValue: "This product changed my life!" }), authorName: props.Text({ name: "Author Name", defaultValue: "Jane Doe" }), authorTitle: props.Text({ name: "Author Title", defaultValue: "CEO, Company" }), rating: props.Number({ name: "Rating", defaultValue: 5, min: 1, max: 5 }) }, options: { applyTagSelectors: true, ssr: true } });


### Required Changes to TestimonialCard.tsx

1. **Convert to CSS Modules** - Rename `TestimonialCard.css` to `TestimonialCard.module.css` and update imports:

import styles from "./TestimonialCard.module.css";

// Default CSS Modules uses bracket notation: <div className={styles["testimonial-card"]}> <div className={styles["stars"]}> // Dot notation (styles.testimonialCard) requires camelCase class names // or a webpack override for css-loader.


### Setup Check

- Verify webflow.json exists
- Install dependencies if needed: `npm i --save-dev @webflow/webflow-cli @webflow/data-types @webflow/react`

Example 2: Component with Incompatible Patterns

User prompt:


Make this work as a Webflow code component:

// Modal.tsx import {createContext, useContext, useState} from 'react';

const ModalContext = createContext<{isOpen: boolean; toggle: () => void} | null>(null);

export const useModal = () => {const context = useContext(ModalContext); if (!context) throw new Error('useModal must be used within ModalProvider'); return context;};

interface ModalProps {trigger: React.ReactNode; children: React.ReactNode; onOpen?: () => void; onClose?: () => void;}

export const Modal: React.FC = ({trigger, children, onOpen, onClose}) => {const [isOpen, setIsOpen] = useState(false);

const toggle = () => {const newState =!isOpen; setIsOpen(newState); if (newState && onOpen) onOpen(); if (!newState && onClose) onClose();};

useEffect(() => {if (isOpen) {document.body.style.overflow = 'hidden';} else {document.body.style.overflow = '';}}, [isOpen]);

return (<ModalContext.Provider value={{isOpen, toggle}}> {trigger} {isOpen && (<div className="modal-content" onClick={e => e.stopPropagation()}> {children})} </ModalContext.Provider>);};

Response:

## Component Analysis: Modal

### Issues Found:

| Issue | Severity | Resolution |
|-------|----------|------------|
| React Context (ModalContext) | Critical | Context won't work across Webflow components. Since this is internal to Modal, it's OK but exported useModal hook won't work. |
| document.body manipulation | Critical | SSR incompatible. Must set `ssr: false` or wrap in useEffect check. |
| onOpen/onClose callbacks | Warning | Function props not supported in Webflow. Must remove. |
| Global CSS classes | Warning | "modal-overlay", "modal-content" won't work in Shadow DOM. |

### Props Detected:
| Prop | TypeScript Type | Webflow Mapping | Status |
|------|-----------------|-----------------|--------|
| trigger | React.ReactNode | props.Slot() | OK |
| children | React.ReactNode | props.Slot() | OK |
| onOpen | function | REMOVE | Not supported |
| onClose | function | REMOVE | Not supported |

---

## Required Changes

### 1. Remove function props (onOpen, onClose)
These cannot be passed from Webflow Designer. Remove from interface and component.

### 2. Fix SSR issue with document.body
Either set `ssr: false` or add typeof check:

useEffect(() => { if (typeof document === 'undefined') return; // ... rest of effect }, [isOpen]);


### 3. Convert to CSS Modules

Rename styles and update class references.

### 4. Remove exported useModal hook

This won't work for external components. Keep ModalContext internal only.

---

## Generated Files

### Modal.webflow.tsx

import { declareComponent } from "@webflow/react"; import { props } from "@webflow/data-types"; import { Modal } from "./Modal"; import "./Modal.module.css";

export default declareComponent(Modal, { name: "Modal", description: "Overlay modal dialog with trigger element", group: "Interactive", props: { trigger: props.Slot({ name: "Trigger" }), children: props.Slot({ name: "Content" }) }, options: { applyTagSelectors: true, ssr: false // Required due to document.body usage } });


### Updated Modal.tsx

import { useState, useEffect } from 'react'; import styles from "./Modal.module.css";

interface ModalProps { trigger: React.ReactNode; children: React.ReactNode; // Removed: onOpen, onClose - not supported in Webflow }

export const Modal: React.FC<ModalProps> = ({ trigger, children }) => { const [isOpen, setIsOpen] = useState(false);

const toggle = () => setIsOpen(!isOpen);

useEffect(() => { if (typeof document === 'undefined') return;

if (isOpen) { document.body.style.overflow = 'hidden'; } else { document.body.style.overflow = ''; }

return () => { document.body.style.overflow = ''; }; }, [isOpen]);

return ( <> <div onClick={toggle}>{trigger}</div> {isOpen && ( <div className={styles["overlay"]} onClick={toggle}> <div className={styles["content"]} onClick={e => e.stopPropagation()}> {children} </div> </div> )} </> ); };


### Setup Required

npm i --save-dev @webflow/webflow-cli @webflow/data-types @webflow/react


Example 3: Component with Complex Object Props

User prompt:


Convert to Webflow:

interface Product {id: string; name: string; price: number; image: string; category: 'electronics' | 'clothing' | 'home';}

interface ProductCardProps {product: Product; showBadge?: boolean;}

export const ProductCard = ({product, showBadge = true}: ProductCardProps) => (

**Response:**

Component Analysis: ProductCard

Complex Props Detected:

The product prop is a complex object that must be flattened for Webflow:

OriginalFlattened Props
product.id(Not needed in UI - remove)
product.nameproductName: props.Text()
product.priceproductPrice: props.Number()
product.imageproductImage: props.Image()
product.categoryproductCategory: props.Variant()
showBadgeshowBadge: props.Boolean()

Generated Files

ProductCard.webflow.tsx

import { declareComponent } from "@webflow/react";
import { props } from "@webflow/data-types";
import { ProductCard } from "./ProductCard";
import "./ProductCard.module.css";

export default declareComponent(ProductCard, {
  name: "ProductCard",
  description: "Product display card with image, name, price, and category",
  group: "Display",
  props: {
    productName: props.Text({
      name: "Product Name",
      defaultValue: "Product Title"
    }),
    productPrice: props.Number({
      name: "Price",
      defaultValue: 29.99
    }),
    productImage: props.Image({
      name: "Product Image"
    }),
    productCategory: props.Variant({
      name: "Category",
      options: ["electronics", "clothing", "home"],
      defaultValue: "electronics"
    }),
    showBadge: props.Boolean({
      name: "Show Category Badge",
      defaultValue: true
    })
  },
  options: {
    applyTagSelectors: true,
    ssr: true
  }
});

Updated ProductCard.tsx

import styles from "./ProductCard.module.css";

interface ProductCardProps {
  productName: string;
  productPrice: number;
  productImage?: { src: string; alt?: string };
  productCategory: 'electronics' | 'clothing' | 'home';
  showBadge?: boolean;
}

export const ProductCard = ({
  productName,
  productPrice,
  productImage,
  productCategory,
  showBadge = true
}: ProductCardProps) => (
  <div className={styles["card"]}>
    {productImage && (
      <img src={productImage.src} alt={productImage.alt || productName} />
    )}
    {showBadge && <span className={styles["badge"]}>{productCategory}</span>}
    <h3>{productName}</h3>
    <p>${productPrice.toFixed(2)}</p>
  </div>
);

Migration Notes:

  • The product object has been flattened into individual props
  • Each prop is now directly editable in Webflow Designer
  • product.id was removed as it's not displayed in the UI
  • Image prop now uses Webflow's Image type (provides {src, alt})
---

### Example 4: Component with styled-components

**User prompt:**

Convert this styled-components React component to Webflow:

// Button.tsx import styled from 'styled-components';

const StyledButton = styled.button<{variant: 'primary' | 'secondary'}>` padding: 12px 24px; border-radius: 8px; font-weight: 600; background: ${props => props.variant === 'primary'? '#3b82f6': '#e5e7eb'}; color: ${props => props.variant === 'primary'? 'white': '#1f2937'};

&:hover {opacity: 0.9;} `;

interface ButtonProps {label: string; variant?: 'primary' | 'secondary'; disabled?: boolean;}

export const Button = ({label, variant = 'primary', disabled = false}: ButtonProps) => ({label});

**Response:**

Component Analysis: Button

Styling Approach Detected: styled-components

styled-components requires a Shadow DOM decorator to work in Webflow.

Props Detected:

PropTypeScript TypeWebflow Mapping
labelstringprops.Text()
variant'primary' \'secondary'props.Variant()
disabledbooleanprops.Boolean()

No blocking issues - ready to convert!


Required Setup for styled-components

1. Install dependencies:

npm i @webflow/styled-components-utils styled-components
npm i -D @types/styled-components

2. Create/update src/globals.ts:

import { styledComponentsShadowDomDecorator } from "@webflow/styled-components-utils";
export const decorators = [styledComponentsShadowDomDecorator];

3. Update webflow.json:

{
  "library": {
    "name": "My Library",
    "components": ["./src/**/*.webflow.@(js|jsx|mjs|ts|tsx)"],
    "globals": "./src/globals.ts"
  }
}

Generated Files

Button.webflow.tsx

import { declareComponent } from "@webflow/react";
import { props } from "@webflow/data-types";
import { Button } from "./Button";
// No CSS import needed - styled-components handles styles

export default declareComponent(Button, {
  name: "Button",
  description: "Styled button with primary and secondary variants",
  group: "Interactive",
  props: {
    label: props.Text({
      name: "Label",
      defaultValue: "Click me"
    }),
    variant: props.Variant({
      name: "Variant",
      options: ["primary", "secondary"],
      defaultValue: "primary"
    }),
    disabled: props.Boolean({
      name: "Disabled",
      defaultValue: false,
      trueLabel: "Disabled",
      falseLabel: "Enabled"
    })
  },
  options: {
    applyTagSelectors: true,
    ssr: true
  }
});

No changes needed to Button.tsx

The component can remain as-is. The styled-components decorator in globals.ts will handle Shadow DOM style injection automatically.

Setup Checklist

  • Install @webflow/styled-components-utils
  • Create globals.ts with decorator
  • Update webflow.json to reference globals
  • Deploy with npx webflow library share
## Guidelines

### When to Recommend Component Redesign

Some components fundamentally don't fit the Webflow model:

1. **Heavy Context usage**: If component relies on app-wide context, suggest redesign
2. **Complex state machines**: May need simplification
3. **Tightly coupled components**: Each needs to be independent in Webflow
4. **Components that render portals**: Consider if portal is necessary

### Default Value Strategy

Always provide sensible defaults:
- Text props: Representative example text
- Numbers: Common/typical value
- Booleans: Most common use case
- Variants: Most popular option
- Images: Can be undefined (optional)
- Slots: No default needed

### Props Naming for Webflow

Make prop names designer-friendly:
- Use descriptive names: `buttonText` not `txt`
- Avoid abbreviations: `imageSource` not `imgSrc`
- Group related props with prefixes: `authorName`, `authorAvatar`, `authorBio`

### SSR Decision

Set `ssr: false` if component:
- Accesses `window`, `document`, `navigator`
- Uses `localStorage` or `sessionStorage`
- Manipulates DOM directly
- Uses libraries that require browser APIs
- Renders canvas, WebGL, or maps

平台分布

Claude

32.66%
按下载量换算573

Codex

32.25%
按下载量换算566

Cursor

17.64%
按下载量换算310

Gemini CLI

9.31%
按下载量换算163

安全审计

暂无安全审计结果可展示。

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

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

继续浏览同类 Skills