anthropics/skills180kfrontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
前端开发
Multi-style article creation skill. Supports 5 writing styles (deep analysis, practical guide, story-driven, opinion, news brief), including complete workflow: material collection → outline → content → formatting. Activated when users mention "write article", "write post", "create", or "draft".
把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。
读取 https://funcoding.ai/skills/freestylefly/wesight/article-writer/install.md ,按里面的步骤帮我安装这个 Skill。
| Style ID | Name | Characteristics | Word Count | Use Cases |
|---|---|---|---|---|
deep-analysis | 深度分析 | Rigorous structure, data-backed | 2000-4000 words | Trend analysis, in-depth reporting |
practical-guide | 实用指南 | Clear steps, highly actionable | 1500-3000 words | Tool tutorials, how-to guides |
story-driven | 故事驱动 | Conversational, emotional resonance | 1500-2500 words | Personal stories, case reviews |
opinion | 观点评论 | Sharp opening, pros/cons argumentation | 1000-2000 words | Hot takes, controversial topics |
news-brief | 新闻简报 | Inverted pyramid, fact-focused | 500-1000 words | Breaking news, information roundups |
Obtain topic information from:
planned in content_calendar.jsonExtract key information:
If user hasn't specified, recommend based on topic:
| Topic Characteristics | Recommended Style |
|---|---|
| Involves data, trends, underlying causes | deep-analysis |
| "How to", "tutorial", "steps" | practical-guide |
| Involves people, experiences, insights | story-driven |
| Involves controversy, hot topic commentary | opinion |
| Breaking events, quick information | news-brief |
Confirm the style choice with the user.
Use content-planner's search script to collect reference materials:
node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "topic keywords" -n 10
Also use web-search skill for additional materials.
Organize material list:
Generate an outline based on the selected style using the corresponding structure template.
## 引入 (200-300字) — 反直觉数据/现象开头
## 背景 (300-500字) — 事件/现象的来龙去脉
## 分析维度1 (400-600字) — 核心论点 + 数据支撑
## 分析维度2 (400-600字) — 对比/反面论证
## 分析维度3 (400-600字) — 深层原因 + 影响预测
## 总结与展望 (200-300字) — 核心观点 + CTA
## 开头 (100-200字) — 痛点共鸣 + 承诺
## 前置准备 (200-300字)
## 步骤1 (300-500字) — 具体操作 + 常见坑
## 步骤2 (300-500字) — 具体操作 + 关键参数
## 步骤3 (300-500字) — 具体操作 + 验证方法
## 进阶技巧 (200-300字)
## 总结 (100-200字) — FAQ + CTA
## 开头 (150-200字) — 场景切入 + 悬念
## 背景铺垫 (200-300字) — 人物/背景/冲突
## 转折1 (300-400字) — 关键事件 + 感受
## 转折2 (300-400字) — 新尝试 + 结果
## 高潮 (200-300字) — 核心洞察
## 结尾 (150-200字) — 启发 + CTA
## 锐利开头 (100-150字) — 直接亮观点
## 现象描述 (200-300字) — 主流观点
## 正面论证 (300-400字) — 我的论点 + 数据
## 反面回应 (200-300字) — 预设反驳 + 反驳
## 深度思考 (200-300字) — 本质 + 影响
## 总结 (100-150字) — 重申观点 + CTA
## 核心信息 (100-200字) — What/When/Where/Who
## 事件详情 (200-300字)
## 背景 (100-200字)
## 反应 (100-200字)
## 编者按 (50-100字)
This is a mandatory approval gate and cannot be skipped.
Present the outline to the user and ask for confirmation or modification requests.
After approval, write content paragraph by paragraph following the outline.
Universal Writing Rules:
Use stories instead of preaching
Use analogies and metaphors
Support with data but don't pile it on
State opinions directly, avoid ambiguity
Use short sentences and line breaks
Data integrity rules:
[数据待确认] and confirm with userWeChat Formatting Hard Rules:
Markdown Formatting Standards:
##), no deep nestingSave the article as Markdown:
Filename format: drafts/YYYYMMDD_[topic-slug].md
---
title: Article Title
date: YYYY-MM-DD
style: deep-analysis
summary: Article summary (within 100 words)
---
## Opening
Content...
✅ Title — Sparks curiosity or resonance
✅ Opening — First 100 words are engaging
✅ Body — Has 2-3 clear viewpoints
✅ Cases — Uses stories not preaching
✅ Formatting — Easy to read (short paragraphs, bold, subheadings)
✅ Word Count — Within style-specified range
✅ CTA — Ending has action prompt
Use these psychological strategies:
| Strategy | Description | Example |
|---|---|---|
| Suspense | Spark curiosity | "为什么我放弃了年薪50万的工作" |
| Benefit | Clarify reader gains | "掌握这3个技巧,效率提升200%" |
| Pain Point | Hit reader anxiety | "别让这个习惯毁了你的职业生涯" |
| Numbers | Specific and tangible | "50%的人都误解了这个真相" |
| Rhetorical | Stimulate thinking | "你真的了解AI吗?" |
| Contrast | Create contrast | "BAT vs 创业公司:差别在哪" |
Score on 3 dimensions (Attractiveness 40%, Shareability 30%, SEO 30%) and present top 3 to user.
content_calendar.json provides topic input
anthropics/skills180kGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
前端开发
anthropics/skills180kSuite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
前端开发
addyosmani/agent-skills103kGuides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
前端开发
addyosmani/agent-skills103kBuilds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
前端开发
addyosmani/agent-skills103kOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
前端开发
nexu-io/open-design100kOpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.
前端开发