When the user wants to add, optimize, or audit social share buttons (share article to X, LinkedIn, Facebook, etc.). Also use when the user mentions "share buttons," "social share," "share to X," "share to LinkedIn," "social sharing," "share icons," "share widget," "native share," "Web Share API," or "share intent URLs." For link previews, use open-graph.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Guides implementation of share buttons that let users share the current page (article, post, product) to social platforms. Distinct from social profile links (footer links to your brand's X, LinkedIn, etc.) — share buttons share this content.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Fewer, better-placed buttons outperform scattered placement. Research: removing 80% of buttons and repositioning the remaining 20% at high-emotion moments can 3× conversion on share actions.
| Placement | Best For | Notes |
|---|---|---|
| After first paragraph | Most articles | Catches speed-readers; visible early |
| Sticky sidebar | Long-form (desktop) | Always visible; consider hiding on mobile |
| Below title / hero | Short posts | High visibility |
| End of article | All | Natural completion point; pair with CTA |
| Mid-article (after key insight) | Long content | Place at friction points (after surprising stat, before CTA) |
Avoid: Dozens of icons; every platform when audience uses 2–3. Choose 3–5 platforms that match your audience (e.g. B2B: X, LinkedIn; B2C: X, Facebook, WhatsApp).
Use platform share/intent URLs so users share with one click:
| Platform | Share URL pattern |
|---|---|
| X (Twitter) | https://twitter.com/intent/tweet?url={url}&text={text} |
https://www.linkedin.com/sharing/share-offsite/?url={url} | |
https://www.facebook.com/sharer/sharer.php?u={url} | |
https://wa.me/?text={url}%20{text} | |
| Telegram | https://t.me/share/url?url={url}&text={text} |
Encode url and text with encodeURIComponent(). Use page title or a short pre-written message for text — platform-specific prompts with pre-written messages perform ~4× better than generic icons.
Use official brand assets. Minimum sizes and color rules:
| Platform | Min size | Colors | Notes |
|---|---|---|---|
| 16px | Blue #1877F2 or monochrome | No rotation, animation without permission | |
| X (Twitter) | 32px | Black or white only | Use current X logo, not deprecated bird |
| 21px height | Blue #0A66C2 or monochrome | Use "in" bug for icons | |
| 29×29px | Black, white, or official gradient | Glyph for social icons |
Source icons from official brand resource centers. Outdated or non-compliant icons reduce perceived shareability.
| Item | Guideline |
|---|---|
| Format | SVG preferred (scalable, small); PNG/WebP with fallback |
| Performance | Lightweight; avoid heavy share plugins that slow LCP |
| Accessibility | aria-label="Share on X"; keyboard accessible |
| Mobile | Touch targets ≥44×44px; consider native share API (navigator.share) on mobile |
On supported browsers, navigator.share lets users share via system dialog (includes more apps). Fallback to intent links when unsupported:
if (navigator.share) {
navigator.share({ title, url, text }).catch(() => {});
} else {
window.open(shareUrl, '_blank', 'noopener');
}
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
中文简介正在准备中。当前显示原文说明。
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
中文简介正在准备中。当前显示原文说明。
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
中文简介正在准备中。当前显示原文说明。
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
中文简介正在准备中。当前显示原文说明。
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
中文简介正在准备中。当前显示原文说明。
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
中文简介正在准备中。当前显示原文说明。