rico-resource-article
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseResource Recommendation Article Generator
资源推荐文章生成器
This skill helps you create high-quality resource recommendation articles through a multi-turn interactive workflow, ensuring accurate content, complete structure, and professional style.
本工具可通过多轮交互式工作流帮你创作高质量的资源推荐文章，确保内容准确、结构完整、风格专业。
Core Features
核心功能
- Intelligent Step-by-Step Generation: Collect candidates → User confirmation → Generate titles → Generate article
- Domain Adaptation: Auto-detect topic domain (Design/Development/Marketing/Product/Content) and apply professional terminology and writing style
- Broad Domain Support: Technical tools, design resources, development frameworks, online services, physical products, etc.
- Multiple Generation Modes: Smart step-by-step, one-shot, outline-based generation
- Professional Format Standards: Complete Front Matter and standard article structure
- Data Accuracy: Only use verifiable data (GitHub Stars, component counts, official metrics)
- 智能分步生成：收集候选资源 → 用户确认 → 生成标题选项 → 生成完整文章
- 领域适配：自动检测主题领域（设计/开发/营销/产品/内容），应用对应专业术语与写作风格
- 广泛领域支持：技术工具、设计资源、开发框架、在线服务、实体产品等
- 多种生成模式：智能分步生成、一键生成、基于大纲生成
- 专业格式标准：完整的Front Matter与标准文章结构
- 数据准确性：仅使用可验证数据（GitHub Stars、组件数量、官方指标）
Triggers
触发条件
This skill supports two trigger modes:
Mode 1: Explicit Command (rico article prefix)
- rico article [topic] / rico 文章 [主题]
- rico article 8 design tools / rico 文章 8个设计工具
Mode 2: Natural Language (explicit article intent required)
- "Generate a recommendation article about shadcn/ui"
- "写一篇工具推荐文章"
- "Create a resource list article"
Important: This skill ONLY triggers when user explicitly wants to generate an article.
Do NOT trigger for simple questions like "recommend 8 tools" or "有哪些好用的工具" - answer directly.
本工具支持两种触发模式：
模式1：明确命令（rico article前缀）
- rico article [主题] / rico 文章 [主题]
- rico article 8 design tools / rico 文章 8个设计工具
模式2：自然语言（需明确包含文章生成意图）
- "Generate a recommendation article about shadcn/ui"
- "写一篇工具推荐文章"
- "Create a resource list article"
重要提示：本工具仅在用户明确希望生成文章时触发。
请勿对“recommend 8 tools”或“有哪些好用的工具”这类简单问题触发，直接回复即可。
Examples
示例
Trigger examples:
- rico article 8 React hooks libraries
- rico 文章 10个设计工具
- Generate a recommendation article about shadcn/ui
- 写一篇 Figma 插件推荐文章
Do NOT trigger examples (just asking or conversing):
- "推荐 8 个组件库" - Answer directly
- "What are some good tools?" - Conversational inquiry
- "Generate 8 resources" - Unclear request without article intent
- "What plugins do you recommend?" - Question-only inquiry
- "生成 8 个资源" - 无明确文章生成意图的模糊请求
- "推荐几个好用的插件" - 单纯询问，不生成文章
触发示例：
- rico article 8 React hooks libraries
- rico 文章 10个设计工具
- Generate a recommendation article about shadcn/ui
- 写一篇 Figma 插件推荐文章
非触发示例（仅询问或对话）：
- "推荐 8 个组件库" - 直接回复
- "What are some good tools?" - 对话式询问
- "Generate 8 resources" - 无明确文章生成意图的模糊请求
- "What plugins do you recommend?" - 仅询问
- "生成 8 个资源" - 无明确文章生成意图的模糊请求
- "推荐几个好用的插件" - 单纯询问，不生成文章
🎯 Mode Selection and Priority
🎯 模式选择与优先级
Default Mode: Intelligent Step-by-Step Generation
Mode Selection Priority:
- User explicitly specifies mode → Use requested mode
- User provides outline list → Use Outline-Based Generation
- User only needs simple list → Use Quick Generation
- Default fallback → Intelligent Step-by-Step Generation
When in doubt, always use Intelligent Step-by-Step Generation as it ensures highest quality through user confirmation.
默认模式：智能分步生成
模式选择优先级:
- 用户明确指定模式 → 使用请求的模式
- 用户提供大纲列表 → 使用基于大纲生成模式
- 用户仅需简单列表 → 使用快速生成模式
- 默认 fallback → 智能分步生成
如有疑问，始终使用智能分步生成，通过用户确认确保最高文章质量。
🌟 Recommended Mode: Intelligent Step-by-Step Generation
🌟 推荐模式：智能分步生成
This is the smartest, most controllable generation mode, ensuring article quality through multi-turn interaction.
这是最智能、可控性最强的生成模式，通过多轮交互确保文章质量。
Workflow
工作流
User inputs topic and quantity
↓
Step 0: Domain Detection (Auto-detect topic domain)
↓
Step 1: Collect candidate items (URL + recommendation reason + differentiating features + verifiable data)
↓
User confirms candidate list
↓
Step 2: Generate 6 title options (pain-point, exploratory, recommendation)
↓
User selects title
↓
Step 3: Generate complete article with domain-specific writing style
↓
Step 4: Ask about screenshots (Optional - ALWAYS ask after article generation)用户输入主题与数量
↓
步骤0：领域检测（自动检测主题领域）
↓
步骤1：收集候选资源（URL + 推荐理由 + 差异化特性 + 可验证数据）
↓
用户确认候选列表
↓
步骤2：生成6个标题选项（痛点型、探索型、推荐型）
↓
用户选择标题
↓
步骤3：生成符合领域风格的完整文章
↓
步骤4：询问是否添加截图（可选 - 文章生成后必须询问）Step 0: Domain Detection
步骤0：领域检测
Auto-detect the topic domain and apply corresponding writing template
自动检测主题领域并应用对应写作模板
Detection Rules
检测规则
| Domain | Keywords (EN/CN) | Target Audience | Focus Areas |
|---|---|---|---|
| Design | Figma, Sketch, UI, UX, design system, component, mockup, prototype, 插件, 设计, 组件库, 设计系统 | Designers | 创意效率, 视觉质量, 设计规范, Design System, 交付流程 |
| Development | React, Vue, Angular, API, framework, library, TypeScript, npm, 框架, 库, 开发 | Developers | 技术栈, 性能优化, 代码质量, GitHub Stars, 社区生态 |
| Marketing | SEO, ROI, conversion, A/B test, analytics, email marketing, 转化率, 营销, 分析 | Marketers | ROI, 数据驱动, 转化效果, 受众分群, 自动化 |
| Product | Prototype, user research, roadmap, collaboration, 原型, 用户调研, 路线图 | Product Managers | 功能完整性, 团队协作, 用户价值, 决策支持 |
| Content | Writing, CMS, publishing, editing, 写作, 编辑, 发布 | Content Creators | 创作效率, 内容质量, 分发渠道, AI 辅助 |
| General | fallback | General Users | 易用性, 功能全面, 实用性 |
| 领域 | 关键词（中英） | 目标受众 | 关注重点 |
|---|---|---|---|
| 设计 | Figma, Sketch, UI, UX, design system, component, mockup, prototype, 插件, 设计, 组件库, 设计系统 | 设计师 | 创意效率, 视觉质量, 设计规范, Design System, 交付流程 |
| 开发 | React, Vue, Angular, API, framework, library, TypeScript, npm, 框架, 库, 开发 | 开发者 | 技术栈, 性能优化, 代码质量, GitHub Stars, 社区生态 |
| 营销 | SEO, ROI, conversion, A/B test, analytics, email marketing, 转化率, 营销, 分析 | 营销人员 | ROI, 数据驱动, 转化效果, 受众分群, 自动化 |
| 产品 | Prototype, user research, roadmap, collaboration, 原型, 用户调研, 路线图 | 产品经理 | 功能完整性, 团队协作, 用户价值, 决策支持 |
| 内容 | Writing, CMS, publishing, editing, 写作, 编辑, 发布 | 内容创作者 | 创作效率, 内容质量, 分发渠道, AI 辅助 |
| 通用 | 默认 fallback | 普通用户 | 易用性, 功能全面, 实用性 |
Detection Process
检测流程
1. Extract keywords from user topic
2. Match against domain keyword library
3. Calculate confidence score based on keyword matches
4. If confidence ≥80%: Auto-select domain and inform user
5. If confidence 50-79%: Ask user to confirm
6. If confidence <50%: Use General template1. 从用户主题中提取关键词
2. 匹配领域关键词库
3. 根据关键词匹配度计算置信度
4. 置信度≥80%：自动选择领域并告知用户
5. 置信度50-79%：询问用户确认
6. 置信度<50%：使用通用模板Example Interaction
交互示例
High Confidence (Auto-select):
markdown
undefined高置信度（自动选择）：
markdown
undefinedUser Input
用户输入
"生成一篇 Figma 插件推荐文章，推荐 6 个"
"生成一篇 Figma 插件推荐文章，推荐 6 个"
AI Response
AI 回复
🔍 检测到领域: Design (设计领域)
基于关键词 "Figma" + "插件"，将使用设计领域专业模板，侧重：
- ✅ 设计工作流集成
- ✅ 创意效率提升
- ✅ Design System 兼容性
[继续执行 Step 1: 收集候选项目...]
**Medium Confidence (Ask User):**
```markdown🔍 检测到领域: Design (设计领域)
基于关键词 "Figma" + "插件"，将使用设计领域专业模板，侧重：
- ✅ 设计工作流集成
- ✅ 创意效率提升
- ✅ Design System 兼容性
[继续执行 Step 1: 收集候选项目...]
**中等置信度（询问用户）：**
```markdownUser Input
用户输入
"生成一篇图片压缩工具推荐文章"
"生成一篇图片压缩工具推荐文章"
AI Response
AI 回复
🤔 检测到多个可能的领域方向
"图片压缩工具" 可以是：
- A. 面向设计师（设计工作流、批量处理、保持质量）
- B. 面向开发者（API 集成、自动化处理、性能优化）
请问您希望侧重哪个方向？(回复 A 或 B，或直接跳过使用通用模板)
---🤔 检测到多个可能的领域方向
"图片压缩工具" 可以是：
- A. 面向设计师（设计工作流、批量处理、保持质量）
- B. 面向开发者（API 集成、自动化处理、性能优化）
请问您希望侧重哪个方向？(回复 A 或 B，或直接跳过使用通用模板)
---Step 1: Collect Candidate Items
步骤1：收集候选资源
Based on user's topic requirements, collect matching projects/websites/tools and list them in the following format:
Candidate List Format:
**1. [Project Name]**
- URL: {{website link}}
- Recommendation reason: {{2-3 sentences explaining why it's worth recommending}}
- Differentiating features: {{How it differs from similar projects}}
- Data: {{Verifiable metrics - GitHub Stars, component counts, official numbers}}
**2. [Project Name]**
...⚠️ DATA ACCURACY RULES (CRITICAL):
1. Only Use Verifiable Data
- ✅ USE: GitHub Stars, GitHub Forks, NPM weekly downloads, Component/Template counts (from official site)
- ✅ USE: Contributor count, Last updated date, License type, Tech stack details
- ❌ DON'T USE: User counts, Customer numbers, Efficiency percentages, Fake metrics
- ❌ DON'T USE: "100万+ 用户", "效率提升 10 倍", "转化率提升 25%" (unless officially verified)
2. How to Collect Data
- Visit GitHub page → Get Stars, Forks, Contributors, Last Updated
- Visit official site → Get component/template counts, feature lists
- Visit NPM page → Get weekly/monthly download counts
- If unsure about data → Either omit or mark as "approximate"
⚠️ CRITICAL RULES (MUST FOLLOW):
1. NEVER Hallucinate Projects or URLs
- ❌ DO NOT invent or fabricate project names, URLs, or websites
- ❌ DO NOT create fake resources or fictional tools
- ✅ ONLY recommend real, verifiable projects that actually exist
- ✅ If unsure about a project's existence, either skip it or ask the user
2. Verify URLs Before Listing
- ✅ Ensure URLs are accessible and valid
- ✅ If a URL seems suspicious or broken, note it for user verification
- ❌ DO NOT include projects with broken or dubious URLs
Important: If you encounter these situations, ask the user first:
- Topic direction is unclear
- Insufficient candidate items (inform how many you found)
- Multiple related sub-topics discovered, need to confirm focus
- Certain project URLs need verification
- Unable to find enough real, verifiable candidates (tell user and ask for guidance)
After listing candidates, ALWAYS wait for user confirmation, tell the user:
Above are {{number}} candidate items. Please confirm:
1. Do you need to adjust any items?
2. Do you need to add or remove any items?
3. Reply 'y' or 'yes' to confirm and proceed根据用户的主题需求，收集匹配的项目/网站/工具，并按以下格式列出：
候选列表格式：
**1. [项目名称]**
- URL: {{网站链接}}
- 推荐理由: {{2-3句话说明推荐价值}}
- 差异化特性: {{与同类项目的区别}}
- 数据: {{可验证指标 - GitHub Stars、组件数量、官方数据}}
**2. [项目名称]**
...⚠️ 数据准确性规则（至关重要）：
1. 仅使用可验证数据
- ✅ 可使用：GitHub Stars、GitHub Forks、NPM周下载量、组件/模板数量（来自官网）
- ✅ 可使用：贡献者数量、最后更新日期、许可证类型、技术栈细节
- ❌ 禁止使用：用户数量、客户数、效率提升百分比、虚假指标
- ❌ 禁止使用："100万+ 用户"、"效率提升 10 倍"、"转化率提升 25%"（除非有官方验证）
2. 数据收集方式
- 访问GitHub页面 → 获取Stars、Forks、贡献者、最后更新时间
- 访问官网 → 获取组件/模板数量、功能列表
- 访问NPM页面 → 获取周/月下载量
- 若对数据存疑 → 要么省略，要么标记为"约略"
⚠️ 核心规则（必须遵守）：
1. 切勿虚构项目或URL
- ❌ 不得编造项目名称、URL或网站
- ❌ 不得创建虚假资源或虚构工具
- ✅ 仅推荐真实、可验证的存在项目
- ✅ 若不确定项目是否存在，要么跳过，要么询问用户
2. 列出前验证URL
- ✅ 确保URL可访问且有效
- ✅ 若URL可疑或失效，需告知用户验证
- ❌ 不得包含链接失效或可疑的项目
重要提示：遇到以下情况，先询问用户：
- 主题方向不明确
- 候选资源不足（告知已找到的数量）
- 发现多个相关子主题，需确认侧重点
- 某些项目URL需要验证
- 无法找到足够真实、可验证的候选资源（告知用户并请求指导）
列出候选资源后，必须等待用户确认，告知用户：
以上是{{数量}}个候选资源，请确认：
1. 是否需要调整任何资源？
2. 是否需要添加或删除资源？
3. 回复'y'或'yes'确认并继续Step 2: Generate Title Options
步骤2：生成标题选项
After user confirms the candidate list, generate 6 article titles in different styles based on these items:
undefined用户确认候选列表后，基于这些资源生成6种不同风格的文章标题：
undefinedPlease select your preferred title style:
请选择你偏好的标题风格：
A. Pain-Point Type
- A1. {{title}}
- A2. {{title}}
B. Exploratory Type
- B1. {{title}}
- B2. {{title}}
C. Recommendation Type
- C1. {{title}}
- C2. {{title}}
Please tell me which title you choose (e.g., A1), or suggest modifications.
**Title Style References:**
- **Pain-Point Type**: Say no to homogenization!, Break through bottlenecks!, Farewell to XXX
- **Exploratory Type**: Inspiration exploration!, In-depth analysis!, XXX exploration
- **Recommendation Type**: Curated, Essential, Must-know, Make XXX, XXX essentialsA. 痛点型
- A1. {{标题}}
- A2. {{标题}}
B. 探索型
- B1. {{标题}}
- B2. {{标题}}
C. 推荐型
- C1. {{标题}}
- C2. {{标题}}
请告知你选择的标题（例如：A1），或提出修改建议。
**标题风格参考：**
- **痛点型**：拒绝同质化！、突破瓶颈！、告别XXX
- **探索型**：灵感探索！、深度解析！、XXX探索
- **推荐型**：精选、必备、必知、打造XXX、XXX必备清单Step 3: Generate Complete Article
步骤3：生成完整文章
After user selects a title, generate the complete article.
First, determine the article folder path:
- Translate the Chinese title to a descriptive English slug
- Use lowercase, hyphen-separated format
- Inform the user: "Article will be saved to: "
{{article-slug}}/index.md - If using screenshots, they will be saved in the same folder
Example:
Title: 精选 4 款最受欢迎的渐变生成器，每个设计师都值得收藏
Slug: featured-4-most-popular-gradient-generators
Path: featured-4-most-popular-gradient-generators/index.mdThen proceed with generating the article content.
用户选择标题后，生成完整文章。
首先，确定文章文件夹路径：
- 将中文标题转换为描述性英文slug
- 使用小写、连字符分隔格式
- 告知用户："文章将保存至："
{{article-slug}}/index.md - 若添加截图，将保存至同一文件夹
示例：
标题：精选 4 款最受欢迎的渐变生成器，每个设计师都值得收藏
Slug: featured-4-most-popular-gradient-generators
路径: featured-4-most-popular-gradient-generators/index.md然后开始生成文章内容。
Article Structure Standards
文章结构标准
File Organization
文件组织
Article files should follow this structure:
{{article-slug}}/
└── index.md # Article content
├── screenshot-1.png # Screenshots (if any)
├── screenshot-2.png
└── ...Path Explanation:
- Articles are saved in current working directory
- Folder name: (e.g.,
{{article-slug}}/)featured-4-most-popular-gradient-generators/ - Article file: always
index.md - Screenshots: saved in the same folder as article
Cover Image Location (separate from article folder):
assets/blog/
└── cover-{{article-slug}}.jpg # Manually added cover imagesNaming rules:
- Article folder: lowercase English, hyphen-separated, descriptive and concise
- Example: ,
shadcn-ui-component-libraries/featured-4-most-popular-gradient-generators/ - Rule: Translate Chinese title to English, use lowercase, connect with hyphens
- Format: or similar descriptive pattern
[adjective]-[number]-[category]-[items] - Examples:
- "精选 4 款最受欢迎的渐变生成器" →
featured-4-most-popular-gradient-generators/ - "设计师必备的 8 个 Figma 插件" →
essential-8-figma-plugins-for-designers/ - "2026 年最佳 Vue 组件库" →
best-vue-component-libraries-2026/
- "精选 4 款最受欢迎的渐变生成器" →
- Example:
- File: always
index.md - Screenshots: saved in same folder as article, named after project (e.g., )
cssgradient-io.png
文章文件需遵循以下结构：
{{article-slug}}/
└── index.md # 文章内容
├── screenshot-1.png # 截图（如有）
├── screenshot-2.png
└── ...路径说明：
- 文章保存至当前工作目录
- 文件夹名称：（例如：
{{article-slug}}/）featured-4-most-popular-gradient-generators/ - 文章文件：固定为
index.md - 截图：保存至文章同一文件夹
封面图片位置（独立于文章文件夹）：
assets/blog/
└── cover-{{article-slug}}.jpg # 手动添加的封面图片命名规则：
- 文章文件夹：英文小写，连字符分隔，描述性简洁
- 示例：,
shadcn-ui-component-libraries/featured-4-most-popular-gradient-generators/ - 规则：将中文标题翻译为英文，小写，连字符连接
- 格式：或类似描述性格式
[形容词]-[数量]-[类别]-[资源] - 示例：
- "精选 4 款最受欢迎的渐变生成器" →
featured-4-most-popular-gradient-generators/ - "设计师必备的 8 个 Figma 插件" →
essential-8-figma-plugins-for-designers/ - "2026 年最佳 Vue 组件库" →
best-vue-component-libraries-2026/
- "精选 4 款最受欢迎的渐变生成器" →
- 示例：
- 文件：固定为
index.md - 截图：保存至文章同一文件夹，以项目名称命名（例如：）
cssgradient-io.png
1. Front Matter (Metadata)
1. Front Matter（元数据）
yaml
---
title: {{user selected title}}
publishDate: {{today's date: YYYY-MM-DD}}
read: {{estimated reading time in minutes, typically 6-12}}
description: {{English subtitle, concise summary for SEO}}
tags:
- {{English tag1}}
- {{English tag2}}
- {{Chinese tag1}}
- {{Chinese tag2}}
img: "/assets/blog/cover-{{article-slug}}.jpg"
img_alt: "{{Chinese description of cover image}}"
---Important Notes:
- img and img_alt are manually added cover images (not auto-generated)
- Image path should follow pattern:
/assets/blog/cover-{{article-slug}}.jpg - description should be in English, concise and SEO-friendly
- read is estimated reading time in minutes
- tags should include both Chinese and English keywords (4-6 items total)
yaml
---
title: {{用户选择的标题}}
publishDate: {{今日日期: YYYY-MM-DD}}
read: {{预估阅读时长（分钟），通常6-12分钟}}
description: {{英文副标题，简洁SEO摘要}}
tags:
- {{英文标签1}}
- {{英文标签2}}
- {{中文标签1}}
- {{中文标签2}}
img: "/assets/blog/cover-{{article-slug}}.jpg"
img_alt: "{{封面图片的中文描述}}"
---重要提示：
- img 和 img_alt 为手动添加的封面图片（非自动生成）
- 图片路径需遵循格式：
/assets/blog/cover-{{article-slug}}.jpg - description 需为英文，简洁且符合SEO
- read 为预估阅读时长（分钟）
- tags 需包含中英文关键词（总计4-6个）
2. Opening Paragraphs (3-4 paragraphs)
2. 开篇段落（3-4段）
- Paragraph 1: Present industry background and current status
- Paragraph 2: Explain core value and significance of the topic
- Paragraph 3: Introduce the content to be recommended in the article
- Paragraph 4 (optional): Explain why these resources are being recommended
- 第一段：介绍行业背景与现状
- 第二段：说明主题的核心价值与意义
- 第三段：介绍文章将推荐的内容
- 第四段（可选）：解释为何推荐这些资源
3. Body Content
3. 正文内容
Write content for each confirmed item in the following format:
markdown
undefined按以下格式为每个确认的资源撰写内容：
markdown
undefined{{number}}. {{Project Name}}
{{序号}}. {{项目名称}}
- 官网: {{URL}}
- 简介: {{Core positioning, main functions, problems solved}}, covering {{specific content scope}}, {{special features/characteristics}}.
- 优势: {{Why it's worth recommending, unique value, applicable scenarios, problems solved}}.
**Body Requirements:**
- Number of recommended items: As requested by user, typically 6-12
- Arrange in logical order (from basic to advanced, or from general to specialized)
- Description should explain core positioning and main content scope
- Advantages should highlight differentiated value and applicable scenarios
- Language should be professional but accessible, target reader appropriate
**Aggregation Platforms (if applicable):**
If there are aggregation platforms, list them separately:
```markdown
Additionally, here are {{number}} aggregation platforms that collect {{platform purpose}}:- 官网: {{URL}}
- 简介: {{核心定位、主要功能、解决的问题}}，覆盖{{具体内容范围}}，{{特殊特性}}
- 优势: {{推荐价值、独特价值、适用场景、解决的问题}}
**正文要求：**
- 推荐资源数量：按用户要求，通常6-12个
- 按逻辑顺序排列（从基础到进阶，或从通用到专业）
- 简介需说明核心定位与主要内容范围
- 优势需突出差异化价值与适用场景
- 语言专业但易懂，符合目标读者定位
**聚合平台（如适用）：**
若存在聚合平台，单独列出：
```markdown
此外，还有{{数量}}个聚合平台，用于{{平台用途}}：{{number}}. {{Project Name}}
{{序号}}. {{项目名称}}
...
undefined...
undefined4. Conclusion (2 parts)
4. 结语（两部分）
-
Subheading (## level-2 heading): Should elevate the theme, not too generic
- Example: ## Vibe Coding: Returning Design to "Creation" Itself
- Or: ## Componentized Inspiration: Focusing Creativity on the Core
-
Summary paragraphs (3-4 paragraphs):
- Explain the overall value of these resources
- Connect with current trends (e.g., AI assistance, automation)
- Provide usage recommendations
- Encourage reader action
Do not add author byline.
-
二级副标题：需升华主题，避免过于通用
- 示例：## Vibe Coding：让设计回归“创作”本身
- 或：## 组件化灵感：将创造力聚焦于核心
-
总结段落（3-4段）：
- 说明这些资源的整体价值
- 结合当前趋势（如AI辅助、自动化）
- 提供使用建议
- 鼓励读者行动
请勿添加作者署名。
Step 4: Ask About Screenshots (ALWAYS ask after article generation)
步骤4：询问是否添加截图（文章生成后必须询问）
After article generation is complete, ALWAYS ask the user:
markdown
✅ Article generated successfully! Saved to: `{{article-slug}}/index.md`
📸 Would you like to add screenshots for the recommended websites?
Quick Options:
- Type "n" or "no" - Skip screenshots
- Type "y" or "yes" - Use default service (ScreenshotOne)
- Type "u" or "urlscan" - Use urlscan.io (requires API key)
Default size: 1600×900 (16:9) - Best for blog articlesIf user says "no" or "n": Skip and end the workflow.
If user says "yes" or "y": Proceed to screenshot process (see 📸 Optional: Add Screenshots section below).
If user wants custom size: Accept and proceed with specified dimensions.
文章生成完成后，必须询问用户：
markdown
✅ 文章生成成功！保存至：`{{article-slug}}/index.md`
📸 是否为推荐的网站添加截图？
快速选项：
- 输入"n"或"no" - 跳过截图
- 输入"y"或"yes" - 使用默认服务（ScreenshotOne）
- 输入"u"或"urlscan" - 使用urlscan.io（需要API密钥）
默认尺寸：1600×900（16:9）- 最适合博客文章若用户回复"no"或"n"： 跳过并结束工作流。
若用户回复"yes"或"y"： 进入截图流程（见下方📸 可选：添加截图章节）。
若用户需要自定义尺寸： 接受并使用指定尺寸。
📌 Other Generation Modes
📌 其他生成模式
Mode 1: One-Shot Generation
模式1：一键生成
For scenarios where user knows exactly what they want and doesn't need multiple confirmations.
Workflow:
- Understand user's topic
- Collect candidate items directly
- Generate one attention-grabbing title
- Generate complete article
Article Format: Same as above (Front Matter + intro + body + conclusion)
适用于用户明确知道需求，无需多次确认的场景。
工作流：
- 理解用户主题
- 直接收集候选资源
- 生成一个吸睛标题
- 生成完整文章
文章格式：与上述一致（Front Matter + 引言 + 正文 + 结语）
Mode 2: Outline-Based Generation
模式2：基于大纲生成
For scenarios where user has already provided a candidate list.
Workflow:
- Read the outline provided by user
- Write description and advantages for each item
- Generate title
- Generate complete article
Additional Handling:
- If outline includes category tags (e.g., 3D, Animated, Minimal), reflect them in the "Advantages" section of corresponding items
- If outline includes URLs, verify link validity
- Adjust item count based on outline content
适用于用户已提供候选列表的场景。
工作流：
- 读取用户提供的大纲
- 为每个资源撰写简介与优势
- 生成标题
- 生成完整文章
额外处理：
- 若大纲包含分类标签（如3D、Animated、Minimal），在对应资源的“优势”部分体现
- 若大纲包含URL，验证链接有效性
- 根据大纲内容调整资源数量
Mode 3: Quick Generation
模式3：快速生成
Generate only the recommendation list, without intro, conclusion, or Front Matter.
markdown
undefined仅生成推荐列表，无引言、结语或Front Matter。
markdown
undefined{{number}}. {{Project Name}}
{{序号}}. {{项目名称}}
- 官网: {{URL}}
- 简介: {{1-2 sentences}}
- 优势: {{1-2 sentences}}
**Note:** Images are not included in quick generation mode. Users can manually add screenshots if needed.
---- 官网: {{URL}}
- 简介: {{1-2句话}}
- 优势: {{1-2句话}}
**注意：** 快速生成模式不包含图片。用户可手动添加截图。
---Writing Style Requirements
写作风格要求
- Professional: Accurate terminology, clear logic
- Practical: Each recommendation has clear use cases and value points
- Readable: Moderate paragraph length, avoid lengthy discourse
- Natural: Avoid common AI writing issues (excessive parallelism, vague descriptions, three-part rule, negative parallelism, vague attribution)
- Original: Avoid copying official introductions, rephrase in your own words
- 专业：术语准确，逻辑清晰
- 实用：每个推荐都有明确的使用场景与价值点
- 易读：段落长度适中，避免冗长论述
- 自然：避免常见AI写作问题（过度排比、模糊描述、三段式结构、负面排比、模糊归因）
- 原创：避免复制官方介绍，用自己的话重述
Avoid Common AI Writing Issues
避免常见AI写作问题
Issue 1: Excessive Parallelism
- ❌ "It has efficiency, flexibility, and scalability."
- ✅ "It's efficient and flexible, with easy scalability."
Issue 2: Vague Descriptions
- ❌ "This component library is very powerful and feature-rich."
- ✅ "Contains 200+ components, covering forms, data display, navigation, and other scenarios."
Issue 3: Three-Part Rule
- ❌ "Not only... but also... and..." / "Whether... or... all..."
- ✅ Use natural, varied sentence structures
Issue 4: Negative Parallelism
- ❌ "It doesn't need complex configuration, additional dependencies, or learning curve."
- ✅ "Simple configuration, zero dependencies, fast to get started."
Issue 5: Vague Attribution
- ❌ "Many people believe..." / "It is well known that..."
- ✅ Directly state opinions or provide specific data sources
问题1：过度排比
- ❌ "它具备高效性、灵活性与可扩展性。"
- ✅ "它高效灵活，且易于扩展。"
问题2：模糊描述
- ❌ "这个组件库非常强大，功能丰富。"
- ✅ "包含200+组件，覆盖表单、数据展示、导航等场景。"
问题3：三段式结构
- ❌ "不仅...而且...还..." / "无论...还是...都..."
- ✅ 使用自然、多样的句式结构
问题4：负面排比
- ❌ "它不需要复杂配置、额外依赖或学习成本。"
- ✅ "配置简单、零依赖、快速上手。"
问题5：模糊归因
- ❌ "很多人认为..." / "众所周知..."
- ✅ 直接陈述观点或提供具体数据来源
Special Notes
特殊说明
Content Guidelines
内容指南
- Tags should include Chinese and English keywords, 4-6 items
- URLs must be accurate and clickable
- Avoid exaggerated promotion, maintain objectivity and professionalism
- Do not add author byline
- Images are optional - users can manually add screenshots to the generated article if needed
- 标签需包含中英文关键词，4-6个
- URL必须准确可点击
- 避免夸大宣传，保持客观专业
- 请勿添加作者署名
- 图片为可选 - 用户可手动为生成的文章添加截图
⚠️ Safety and Compliance Rules (CRITICAL)
⚠️ 安全与合规规则（至关重要）
1. Prohibited Content
- ❌ DO NOT recommend pirated, cracked, or illegal software/resources
- ❌ DO NOT promote copyright-infringing content
- ❌ DO NOT recommend resources that violate terms of service
- ❌ DO NOT include adult content, gambling, or illegal activities
- ✅ ONLY recommend legitimate, legal, and ethical resources
2. Accuracy Requirements
- ❌ DO NOT hallucinate or fabricate projects, URLs, or websites
- ❌ DO NOT create fictional resources or tools
- ✅ ONLY recommend real, verifiable projects
- ✅ If insufficient real candidates exist, inform the user and ask for guidance
3. Verification
- ✅ Verify that recommended resources actually exist
- ✅ Ensure URLs are accessible and safe
- ❌ DO NOT include suspicious or broken URLs without warning the user
4. Disclosure
- ✅ If you're uncertain about a resource's legitimacy, note it
- ✅ If knowledge base has no matching content, tell user honestly
- ❌ DO NOT make up recommendations to satisfy the request
1. 禁止内容
- ❌ 不得推荐盗版、破解或非法软件/资源
- ❌ 不得推广侵犯版权的内容
- ❌ 不得推荐违反服务条款的资源
- ❌ 不得包含成人内容、赌博或非法活动
- ✅ 仅推荐合法合规的资源
2. 准确性要求
- ❌ 不得虚构项目、URL或网站
- ❌ 不得创建虚假资源或工具
- ✅ 仅推荐真实、可验证的项目
- ✅ 若真实候选资源不足，告知用户并请求指导
3. 验证要求
- ✅ 验证推荐资源确实存在
- ✅ 确保URL可访问且安全
- ❌ 不得包含可疑或失效的URL，除非告知用户
4. 披露要求
- ✅ 若不确定资源合法性，需注明
- ✅ 若知识库无匹配内容，如实告知用户
- ❌ 不得编造推荐内容满足请求
Mode Selection Guide
模式选择指南
| User Need | Recommended Mode | Reason |
|---|---|---|
| "Recommend X items... and generate an article" | Intelligent Step-by-Step | Let user participate in confirmation, highest quality |
| "Generate a recommendation article about XXX" | Intelligent Step-by-Step | Multi-turn interaction ensures accuracy |
| Provided an outline list | Outline-Based Generation | Quick completion, user confirmed content |
| Only need recommendation list | Quick Generation | Concise and efficient |
| Clear topic and quantity | One-Shot Generation | Fast output |
| 用户需求 | 推荐模式 | 理由 |
|---|---|---|
| "推荐X个资源...并生成文章" | 智能分步生成 | 让用户参与确认，质量最高 |
| "生成一篇关于XXX的推荐文章" | 智能分步生成 | 多轮交互确保准确性 |
| 已提供大纲列表 | 基于大纲生成 | 快速完成，用户已确认内容 |
| 仅需推荐列表 | 快速生成 | 简洁高效 |
| 主题与数量明确 | 一键生成 | 输出快速 |
Complete Example
完整示例
User Input:
用户输入:
"Write a recommendation article about shadcn/ui component libraries, recommend 8"
"Write a recommendation article about shadcn/ui component libraries, recommend 8"
AI Step 1: Collect Candidate Items
AI 步骤1：收集候选资源
Here are 8 collected shadcn/ui component libraries:
**1. [Aceternity UI]**
- URL: https://ui.aceternity.com/
- Recommendation reason: Hottest component library in shadcn/ui ecosystem, 120k+ developers using it
- Differentiating features: Deeply integrated with Framer Motion, extensive visual effects components
**2. [Kibo UI]**
- URL: https://www.kibo-ui.com/
- Recommendation reason: Fills gaps in shadcn/ui's advanced components
- Differentiating features: Provides color picker, rich text editor and other advanced components
...
Above are 8 candidate items. Please confirm:
1. Do you need to adjust any items?
2. Do you need to add or remove any items?
3. Reply 'y' or 'yes' to confirm and proceed以下是收集到的8个shadcn/ui组件库：
**1. [Aceternity UI]**
- URL: https://ui.aceternity.com/
- 推荐理由：shadcn/ui生态中最热门的组件库，12万+开发者使用
- 差异化特性：与Framer Motion深度集成，拥有丰富的视觉效果组件
**2. [Kibo UI]**
- URL: https://www.kibo-ui.com/
- 推荐理由：填补了shadcn/ui在高级组件上的空白
- 差异化特性：提供颜色选择器、富文本编辑器等高级组件
...
以上是8个候选资源，请确认：
1. 是否需要调整任何资源？
2. 是否需要添加或删除资源？
3. 回复'y'或'yes'确认并继续User: y
用户: y
AI Step 2: Generate Title Options
AI 步骤2：生成标题选项
undefinedundefinedPlease select your preferred title style:
请选择你偏好的标题风格：
A. Pain-Point Type
- A1. Say No to Homogenization! 8 Curated Shadcn/UI Component Libraries
- A2. Break Through Design Bottlenecks! 8 Must-Try Shadcn/UI Extension Libraries
B. Exploratory Type
- B1. Inspiration Exploration! 8 Shadcn/UI-Focused Component Libraries
- B2. In-Depth Analysis: 8 Efficiency-Boosting Shadcn/UI Resources
C. Recommendation Type
- C1. 8 Shadcn/UI Component Libraries to Double Development Efficiency
- C2. Developer Essentials: 8 Quality Shadcn/UI Extension Libraries
Please tell me which title you choose (e.g., A1), or suggest modifications.
undefinedA. 痛点型
- A1. 拒绝同质化！8款精选Shadcn/UI组件库
- A2. 突破设计瓶颈！8款必试Shadcn/UI扩展库
B. 探索型
- B1. 灵感探索！8款聚焦Shadcn/UI的组件库
- B2. 深度解析：8款提升效率的Shadcn/UI资源
C. 推荐型
- C1. 8款Shadcn/UI组件库，让开发效率翻倍
- C2. 开发者必备：8款优质Shadcn/UI扩展库
请告知你选择的标题（例如：A1），或提出修改建议。
undefinedUser: A1
用户: A1
AI Step 3: Generate Complete Article
AI 步骤3：生成完整文章
File structure:
content/shadcn-ui-component-libraries/
└── index.mdContent:
markdown
---
title: Say No to Homogenization! 8 Curated Shadcn/UI Component Libraries
publishDate: 2026-03-03
read: 8
description: Top 8 Awesome Shadcn UI Component Libraries
tags:
- Shadcn UI
- Component Libraries
- UI组件库
- 组件库推荐
img: "./cover-shadcn-ui.jpg"
img_alt: "8 Curated Shadcn/UI Component Libraries"
---
shadcn/ui is one of the hottest component systems today...文件结构:
content/shadcn-ui-component-libraries/
└── index.md内容:
markdown
---
title: 拒绝同质化！8款精选Shadcn/UI组件库
publishDate: 2026-03-03
read: 8
description: Top 8 Awesome Shadcn UI Component Libraries
tags:
- Shadcn UI
- Component Libraries
- UI组件库
- 组件库推荐
img: "./cover-shadcn-ui.jpg"
img_alt: "8款精选Shadcn/UI组件库"
---
shadcn/ui是目前最热门的组件系统之一...1. Aceternity UI
1. Aceternity UI
- 官网: https://ui.aceternity.com/
- 简介: Hottest component library in shadcn/ui ecosystem with 120k+ developers, covering 200+ production-quality components...
- 优势: Deeply integrated with Framer Motion and Tailwind CSS, providing glow cards, text gradients, 3D globe and other unique visual components...
...
---- 官网: https://ui.aceternity.com/
- 简介: shadcn/ui生态中最热门的组件库，12万+开发者使用，包含200+生产级组件...
- 优势: 与Framer Motion和Tailwind CSS深度集成，提供发光卡片、文字渐变、3D地球等独特视觉组件...
...
---📸 Optional: Add Screenshots
📸 可选：添加截图
After article generation, offer users the option to add screenshots for recommended websites.
文章生成后，为用户提供为推荐网站添加截图的选项。
When to Ask
询问时机
Ask after article generation is complete:
markdown
✅ Article generated successfully!
Would you like to add screenshots for the recommended websites?
Quick Options:
- Type "n" or "no" - Skip screenshots
- Type "y" or "yes" - Use default service (ScreenshotOne)
- Type "u" or "urlscan" - Use urlscan.io (requires API key)
Current default: ScreenshotOne (JPG format, smaller file size)
Default size: 1600×900 (16:9) - 适合博客文章
💡 **自定义截图尺寸 / Customize Screenshot Size:**
Just mention it when requesting / 在请求时直接说明:
- "Use 1920×1080" / "用 1920×1080 截图"
- "Screenshot at 1440×900" / "截图尺寸 1440×900"文章生成完成后询问：
markdown
✅ 文章生成成功！
是否为推荐的网站添加截图？
快速选项：
- 输入"n"或"no" - 跳过截图
- 输入"y"或"yes" - 使用默认服务（ScreenshotOne）
- 输入"u"或"urlscan" - 使用urlscan.io（需要API密钥）
当前默认：ScreenshotOne（JPG格式，文件更小）
默认尺寸：1600×900（16:9）- 适合博客文章
💡 **自定义截图尺寸 / Customize Screenshot Size:**
在请求时直接说明即可 / Just mention it when requesting:
- "使用 1920×1080" / "用 1920×1080 截图"
- "Screenshot at 1440×900" / "截图尺寸 1440×900"Service Selection
服务选择
If user chooses "yes" (uses default) or selects a specific service:
If user selected "yes" (default service):
markdown
Using default service: ScreenshotOne
✓ Fast (2-5 seconds per screenshot)
✓ 100 free screenshots/month
✗ Requires API keyIf user wants to compare services:
markdown
Available screenshot services:
【ScreenshotOne】
✓ Fast (2-5 seconds)
✓ 100 free screenshots/month
✗ Requires API key
【urlscan.io】
✓ Free: 5,000 Public Scans/day
✓ Free: 1,000 Unlisted Scans/day
✓ Free: 50 Private Scans/day
✗ Requires API key
✗ Slower than ScreenshotOne
Default: ScreenshotOne (configured in .env)若用户选择"yes"（使用默认）或指定服务：
若用户选择"yes"（默认服务）：
markdown
使用默认服务：ScreenshotOne
✓ 快速（每张截图2-5秒）
✓ 每月免费100张截图
✗ 需要API密钥若用户希望对比服务：
markdown
可用截图服务：
【ScreenshotOne】
✓ 快速（2-5秒）
✓ 每月免费100张截图
✗ 需要API密钥
【urlscan.io】
✓ 免费：每日5000次公开扫描
✓ 免费：每日1000次未列出扫描
✓ 免费：每日50次私有扫描
✗ 需要API密钥
✗ 比ScreenshotOne慢
默认：ScreenshotOne（在.env中配置）Configuration Check
配置检查
IMPORTANT: Always check .env file first before asking user
Step 1: Check if .env file exists and has API key
Check order:
1. .rico-skills/.env (project-level)
2. ~/.rico-skills/.env (user-level)
If API key found → Use it directly ✓
If not found → Go to Step 2Step 2: If no API key configured
markdown
Checking ScreenshotOne configuration...
⚠️ API Key not found in .env file
Get your free API key:
1. Visit: https://screenshotone.com/
2. Sign up (free, 2 minutes)
3. Copy your API Key
Choose how to configure:
[A] 💾 Create .env file (Recommended) - Key will be saved for future use
[B] 🔑 Enter API key now (One-time) - Key will only be used for this session
[C] ⏭️ Skip screenshots - Add manually later
Please reply A, B, or C:If user selects [A] - Create .env file:
markdown
Great! I'll create the .env file for you.
Please enter your API Key: [wait for user input]
✓ Creating .rico-skills/.env file...
✓ Saving API key...
✓ Configuration complete! Key saved for future use.
Now proceeding with screenshots...If user selects [B] - One-time use:
markdown
Please enter your API Key (will be used for this session only): [wait for user input]
✓ Key received. Proceeding with screenshots...
(Note: You'll need to enter the key again next time)If user selects [C] - Skip:
markdown
✓ Skipping screenshots. You can add them manually later.
Manual screenshot guide:
- Save screenshots to: say-goodbye-to-stock-photos-3-ai-image-generators/
- Recommended size: 1600×900 (16:9)
- Naming: {website-name}.pngFor urlscan.io (same flow):
markdown
Checking urlscan.io configuration...
⚠️ API Key not found in .env file
Get your free API key:
1. Visit: https://urlscan.io/user/ (login required)
2. Go to Settings → API Keys
3. Copy your API Key
Choose how to configure:
[A] 💾 Create .env file (Recommended) - Save for future use
[B] 🔑 Enter API key now (One-time) - Use for this session only
[C] ⏭️ Skip screenshots - Add manually later
Please reply A, B, or C:After saving to .env, show confirmation:
markdown
✓ API key saved to .rico-skills/.env
Your configuration:
- Service: ScreenshotOne
- API Key: sk_•••••••••••••••• (hidden)
- Default size: 1600×900
This key will be automatically used for future screenshot requests.重要提示：询问用户前务必先检查.env文件
步骤1：检查.env文件是否存在且包含API密钥
检查顺序:
1. .rico-skills/.env（项目级）
2. ~/.rico-skills/.env（用户级）
若找到API密钥 → 直接使用 ✓
若未找到 → 进入步骤2步骤2：若无API密钥配置
markdown
正在检查ScreenshotOne配置...
⚠️ .env文件中未找到API密钥
获取免费API密钥：
1. 访问: https://screenshotone.com/
2. 注册（免费，2分钟）
3. 复制你的API密钥
选择配置方式：
[A] 💾 创建.env文件（推荐）- 密钥将保存供未来使用
[B] 🔑 立即输入API密钥（一次性）- 密钥仅用于本次会话
[C] ⏭️ 跳过截图 - 后续手动添加
请回复A、B或C：若用户选择[A] - 创建.env文件：
markdown
好的！我将为你创建.env文件。
请输入你的API密钥：[等待用户输入]
✓ 正在创建.rico-skills/.env文件...
✓ 正在保存API密钥...
✓ 配置完成！密钥已保存供未来使用。
现在开始生成截图...若用户选择[B] - 一次性使用：
markdown
请输入你的API密钥（仅用于本次会话）：[等待用户输入]
✓ 已收到密钥。开始生成截图...
（注意：下次使用需重新输入密钥）若用户选择[C] - 跳过：
markdown
✓ 已跳过截图。你可后续手动添加。
手动截图指南：
- 将截图保存至：say-goodbye-to-stock-photos-3-ai-image-generators/
- 推荐尺寸：1600×900（16:9）
- 命名：{网站名称}.pngurlscan.io流程相同：
markdown
正在检查urlscan.io配置...
⚠️ .env文件中未找到API密钥
获取免费API密钥：
1. 访问: https://urlscan.io/user/（需登录）
2. 进入设置 → API Keys
3. 复制你的API密钥
选择配置方式：
[A] 💾 创建.env文件（推荐）- 保存供未来使用
[B] 🔑 立即输入API密钥（一次性）- 仅用于本次会话
[C] ⏭️ 跳过截图 - 后续手动添加
请回复A、B或C：保存至.env后，显示确认信息：
markdown
✓ API密钥已保存至.rico-skills/.env
你的配置：
- 服务：ScreenshotOne
- API密钥：sk_••••••••••••••••（已隐藏）
- 默认尺寸：1600×900
该密钥将自动用于未来的截图请求。Screenshot Dimensions
截图尺寸
Default Screenshot Size: 1600×900 (16:9)
This is the optimal size for most blog and article layouts, providing:
- Clear visibility of website details
- Good aspect ratio for responsive design
- Reasonable file size for web loading
Customize Screenshot Size:
If you need different dimensions, specify when requesting screenshots:
markdown
Example requests:
- "使用 1920×1080 尺寸截图"
- "用 1440×900 截图"
- "截图尺寸设为 1200×800"
- "Take screenshots at 1920×1080"Available Sizes:
| Size | Aspect Ratio | Best For |
|---|---|---|
| 1920×1080 | 16:9 | Full HD displays |
| 1600×900 | 16:9 | Default - Blog posts |
| 1440×900 | 16:10 | Mac-style displays |
| 1200×800 | 3:2 | Tablets, smaller screens |
| 1200×600 | 2:1 | Wide banners |
| 1200×900 | 4:3 | Traditional displays |
Note: urlscan.io has limited size options (typically 1920×1080 or similar). For custom sizes, use ScreenshotOne or manual screenshot tools.
默认截图尺寸：1600×900（16:9）
这是大多数博客和文章布局的最佳尺寸，具备：
- 清晰展示网站细节
- 适合响应式设计的宽高比
- 合理的文件大小，利于网页加载
自定义截图尺寸：
若需要不同尺寸，在请求截图时指定：
markdown
示例请求：
- "使用 1920×1080 尺寸截图"
- "用 1440×900 截图"
- "截图尺寸设为 1200×800"
- "Take screenshots at 1920×1080"可用尺寸：
| 尺寸 | 宽高比 | 最佳用途 |
|---|---|---|
| 1920×1080 | 16:9 | 全高清显示器 |
| 1600×900 | 16:9 | 默认 - 博客文章 |
| 1440×900 | 16:10 | Mac风格显示器 |
| 1200×800 | 3:2 | 平板、小屏幕 |
| 1200×600 | 2:1 | 宽横幅 |
| 1200×900 | 4:3 | 传统显示器 |
注意： urlscan.io尺寸选项有限（通常为1920×1080或类似）。如需自定义尺寸，使用ScreenshotOne或手动截图工具。
Screenshot Process
截图流程
Once configured:
For ScreenshotOne:
markdown
Found 8 URLs to screenshot
[1/8] Capturing https://ui.aceternity.com/...
Waiting for screenshot...
✓ aceternity-ui.png (2.3s)
[2/8] Capturing https://www.kibo-ui.com/...
✓ kibo-ui.png (1.8s)
...
✓ Screenshots completed: 8/8
Saved to: ./ (current directory)For urlscan.io:
markdown
Found 8 URLs to screenshot
[1/8] Submitting scan for https://ui.aceternity.com/...
Scan UUID: abc123-def456-ghi789
Waiting for scan to complete...
Downloading screenshot...
✓ aceternity-ui.png (8.2s)
[2/8] Submitting scan for https://www.kibo-ui.com/...
Scan UUID: xyz789-uvw456-rst123
Waiting for scan to complete...
Downloading screenshot...
✓ kibo-ui.png (7.5s)
...
✓ Screenshots completed: 8/8
Saved to: ./ (current directory)配置完成后：
ScreenshotOne流程：
markdown
找到8个需要截图的URL
[1/8] 正在捕获https://ui.aceternity.com/...
等待截图生成...
✓ aceternity-ui.png（2.3秒）
[2/8] 正在捕获https://www.kibo-ui.com/...
✓ kibo-ui.png（1.8秒）
...
✓ 截图完成：8/8
保存至：./（当前目录）urlscan.io流程：
markdown
找到8个需要截图的URL
[1/8] 正在提交https://ui.aceternity.com/的扫描请求...
扫描UUID: abc123-def456-ghi789
等待扫描完成...
正在下载截图...
✓ aceternity-ui.png（8.2秒）
[2/8] 正在提交https://www.kibo-ui.com/的扫描请求...
扫描UUID: xyz789-uvw456-rst123
等待扫描完成...
正在下载截图...
✓ kibo-ui.png（7.5秒）
...
✓ 截图完成：8/8
保存至：./（当前目录）Update Article with Screenshots
更新文章添加截图
After screenshots are saved, ALWAYS update the article to include images.
For each recommended item, insert the screenshot image after the heading:
Before (without screenshot):
markdown
undefined截图保存后，务必更新文章添加图片。
为每个推荐资源，在标题后插入截图：
添加前：
markdown
undefined1. Aceternity UI
1. Aceternity UI
- 官网: https://ui.aceternity.com/
- 简介: ...
**After (with screenshot):**
```markdown- 官网: https://ui.aceternity.com/
- 简介: ...
**添加后：**
```markdown1. Aceternity UI
1. Aceternity UI
- 官网: https://ui.aceternity.com/
- 简介: ...
**Image insertion rules:**
1. Insert image immediately after the item heading (`### N. Project Name`)
2. Use format: ``
3. Alt text should be the project name or brief description
4. Image files should be in the same directory as index.md
**After updating the article, show confirmation:**
```markdown
✓ Article updated with 3 screenshots
Updated sections:
- Section 1: meshgradients-com.jpg
- Section 2: csshero-mesher.jpg
- Section 3: nicepkg-mesh-gradient.jpg- 官网: https://ui.aceternity.com/
- 简介: ...
**图片插入规则：**
1. 图片紧跟在资源标题（`### N. 项目名称`）之后
2. 使用格式：``
3. 替代文本为项目名称或简短描述
4. 图片文件与index.md在同一目录
**更新文章后，显示确认信息：**
```markdown
✓ 文章已更新，添加3张截图
更新章节：
- 章节1: meshgradients-com.jpg
- 章节2: csshero-mesher.jpg
- 章节3: nicepkg-mesh-gradient.jpgScreenshot File Naming
截图文件命名
Screenshots are saved in the same directory as the article:
shadcn-ui-component-libraries/
├── index.md # Article content
├── aceternity-ui.png # Screenshot 1
├── kibo-ui.png # Screenshot 2
├── ...
└── footer-design.png # Screenshot 8Naming rule:
{project-name}.png- Extracted from domain or project name
- Lowercase, hyphen-separated
- Example: ,
aceternity-ui.pngkibo-ui.png
截图保存至文章同一目录：
shadcn-ui-component-libraries/
├── index.md # 文章内容
├── aceternity-ui.png # 截图1
├── kibo-ui.png # 截图2
├── ...
└── footer-design.png # 截图8命名规则：
{项目名称}.png- 从域名或项目名称提取
- 小写，连字符分隔
- 示例：,
aceternity-ui.pngkibo-ui.png
Error Handling
错误处理
If screenshots fail:
markdown
⚠️ Some screenshots failed:
- kibo-ui.png: Timeout (30s)
- footer-design.png: API rate limit
✓ Successful: 6/8
❌ Failed: 2/8
You can manually add these screenshots later if needed.若截图失败：
markdown
⚠️ 部分截图失败：
- kibo-ui.png: 超时（30秒）
- footer-design.png: API速率限制
✓ 成功：6/8
❌ 失败：2/8
你可后续手动添加这些截图。Manual Screenshot Guide
手动截图指南
If users prefer manual screenshots or hit API limits:
markdown
undefined若用户偏好手动截图或触发API限制：
markdown
undefinedManual Screenshot Guide
手动截图指南
System Tools
系统工具
- Mac: Cmd+Shift+4 (select area)
- Windows: Win+Shift+S (select area)
- Mac: Cmd+Shift+4（选择区域）
- Windows: Win+Shift+S（选择区域）
Online Tools
在线工具
- Screenshot.guru: https://screenshot.guru/
- Screenshot.rocks: https://screenshot.rocks/
- Screenshot.guru: https://screenshot.guru/
- Screenshot.rocks: https://screenshot.rocks/
Recommended Dimensions
推荐尺寸
- Default: 16:9 (1600×900)
- Alternatives: 16:10, 3:2, 2:1, 4:3
- 默认：16:9（1600×900）
- 其他选项：16:10, 3:2, 2:1, 4:3
File Organization
文件组织
Save screenshots in the same directory as the article:
- Article:
content/shadcn-ui-component-libraries/index.md - Screenshots:
content/shadcn-ui-component-libraries/*.png
This keeps related files together and makes management easier.
undefined将截图保存至文章同一目录：
- 文章:
content/shadcn-ui-component-libraries/index.md - 截图:
content/shadcn-ui-component-libraries/*.png
这样可将相关文件集中管理，便于维护。
undefined