/rico-resource-article

name: rico-resource-article
description: |
  Resource recommendation article generator with multi-turn workflow and domain adaptation.
  Creates structured articles with verifiable data, proper formatting, and professional style.
  Use when user explicitly requests to generate/write/create a recommendation article (生成/写/创建 + 推荐文章/资源列表).
  Must include both action + article intent. Don't trigger on simple questions like "推荐几个工具".

Resource 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)

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.

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 个资源" - 无明确文章生成意图的模糊请求
• "推荐几个好用的插件" - 单纯询问，不生成文章

---

🎯 Mode Selection and Priority

**Default Mode**: Intelligent Step-by-Step Generation

**Mode Selection Priority**: 1. **User explicitly specifies mode** → Use requested mode 2. **User provides outline list** → Use Outline-Based Generation 3. **User only needs simple list** → Use Quick Generation 4. **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.

---

🌟 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)

Step 0: Domain Detection

**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 | 易用性, 功能全面, 实用性 |

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 template

Example Interaction

**High Confidence (Auto-select):**

### User Input
"生成一篇 Figma 插件推荐文章，推荐 6 个"

### AI Response
🔍 **检测到领域: Design (设计领域)**

基于关键词 "Figma" + "插件"，将使用设计领域专业模板，侧重：
- ✅ 设计工作流集成
- ✅ 创意效率提升
- ✅ Design System 兼容性

[继续执行 Step 1: 收集候选项目...]

**Medium Confidence (Ask User):**

### User Input
"生成一篇图片压缩工具推荐文章"

### AI Response
🤔 **检测到多个可能的领域方向**

"图片压缩工具" 可以是：
- A. 面向设计师（设计工作流、批量处理、保持质量）
- B. 面向开发者（API 集成、自动化处理、性能优化）

请问您希望侧重哪个方向？(回复 A 或 B，或直接跳过使用通用模板)

---

Step 1: Collect Candidate Items

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, N