菜单
Use when writing marketing copy, landing pages, email subject lines, CTAs, headlines, UX microcopy, or A/B test variants. Covers proven copywriting frameworks (AIDA, PAS, BAB, 4Ps), headline formulas, conversion-focused writing, tone and voice guidelines, and copy testing strategies.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when managing Laravel Forge servers, sites, deployments, SSL, databases, queue workers, scheduled jobs, security rules, and server provisioning. Covers Forge CLI, API, deployment scripts, Nginx templates, daemon management, and zero-downtime deployments.
Project-specific Ansible operations template — customize with your inventory, playbook catalog, deployment workflows, and host group details
Use when implementing or auditing accessibility features. Covers WCAG 2.1 AA/AAA compliance, ARIA roles and attributes, keyboard navigation, screen reader support, color contrast, focus management, and accessible component patterns.
Use when evaluating AI/LLM systems — benchmark design, automated evaluation pipelines, human evaluation protocols, A/B testing, hallucination detection, factuality checking, bias testing, safety evaluation (red teaming), latency/cost metrics, eval datasets, regression testing for prompts, and model comparison frameworks.
Use when building KPI frameworks, designing dashboards, analyzing marketing performance, setting up attribution models, or creating automated reports. Covers Google Analytics 4, social media analytics, funnel analysis, cohort analysis, A/B test analysis, ROI calculation, competitive benchmarking, and stakeholder reporting.
Use when designing or implementing REST APIs. Covers RESTful conventions, versioning, pagination, filtering, error handling, rate limiting, HATEOAS, OpenAPI documentation, and API security best practices.
| name | copywriting-patterns |
| description | Use when writing marketing copy, landing pages, email subject lines, CTAs, headlines, UX microcopy, or A/B test variants. Covers proven copywriting frameworks (AIDA, PAS, BAB, 4Ps), headline formulas, conversion-focused writing, tone and voice guidelines, and copy testing strategies. |
| user-invocable | true |
| allowed-tools | ["Read","Write","Edit","Grep","Glob"] |
Best for structured persuasion (landing pages, ads):
A — ATTENTION: Bold headline addressing the pain. Stop the scroll.
I — INTEREST: Relevant facts, stories, or data. Show understanding.
D — DESIRE: Paint the outcome. Benefits + social proof + specificity.
A — ACTION: One clear CTA. Remove friction. Create genuine urgency.
Best for problem-aware but not solution-aware audiences:
P — PROBLEM: State the problem clearly in the reader's language.
A — AGITATE: Make the pain vivid. Show consequences of inaction.
S — SOLUTION: Present your solution as the relief, tied to the pain points.
Best for transformation stories and case studies:
B — BEFORE: Describe the current painful state.
A — AFTER: Describe the ideal future state.
B — BRIDGE: Show how your product bridges the gap.
Best for sales pages and product marketing:
Promise: Specific, compelling big benefit
Picture: Help the reader visualize the outcome
Proof: Evidence (data, testimonials, case studies)
Push: Reason to act now + clear CTA
Problem -> Amplify -> Story/Solution -> Transformation -> Offer -> Response
| Framework | Best For | Audience Awareness |
|---|---|---|
| AIDA | Landing pages, ads | Varies |
| PAS | Email, blog intros | Problem-aware |
| BAB | Case studies, testimonials | Problem-aware |
| 4Ps | Feature/product pages | Solution-aware |
| PASTOR | Long-form sales pages | Unaware to problem-aware |
HOW-TO: "How to [outcome] without [objection]"
NUMBERED LIST: "[N] [noun] that [verb] [outcome]"
QUESTION: "Are you still [painful activity]?"
DIRECT BENEFIT: "The fastest way to [desired outcome]"
SOCIAL PROOF: "How [customer] [achieved result] in [timeframe]"
NEGATIVE: "Stop [mistake] before it [consequence]"
CURIOSITY GAP: "We analyzed [N] [things]. Here is what we found."
SPECIFIC RESULT: "[Exact result] in [exact timeframe] — here is how"
Testing: One variable at a time. Min 100 observations/variant. Run 7+ days. Winner must beat control by 10%+.
Rules:
Placement: Hero section (above fold) + after social proof + bottom of page.
1. HERO: Headline (benefit) + subheadline + CTA + visual
2. SOCIAL PROOF: Customer logos or key metric
3. PROBLEM: 2-3 pain points in their language
4. SOLUTION: How you solve each pain point
5. FEATURES: 3-4 feature-benefit pairs (lead with benefit)
6. TESTIMONIAL: Name, role, company + specific metric
7. HOW IT WORKS: 3-step process
8. PRICING/CTA: Pricing table or repeated CTA
9. FAQ: Top 5-7 objections, concise answers
10. FINAL CTA: Restate benefit + CTA button
[Product] has [feature] so you can [benefit], which means [outcome the reader cares about].
| Objection | Response Pattern |
|---|---|
| "Too expensive" | Reframe as investment: "For less than the cost of one error..." |
| "No time to switch" | Address migration: "Most teams are running in 2 weeks" |
| "Too small/big" | Show range with proof: "Teams of 5 and 500 use it" |
| "What if it fails?" | Risk reversal: "Free 30 days, cancel with one click" |
| "Current system works" | Quantify hidden cost: "15 hours/month on manual work" |
CURIOSITY: "The one thing your competitors are doing differently"
BENEFIT: "Cut your [process] time in half"
PERSONALIZATION: "[First name], your [month] report is ready"
URGENCY (real): "[Offer] expires [day]"
SOCIAL PROOF: "How [customer] [achieved result]"
QUESTION: "Still managing [task] in spreadsheets?"
Rules: 30-50 characters optimal. Front-load the key word. No ALL CAPS. Preview text complements, not repeats.
Formula: [What happened] + [Why] + [What to do next]
Formula: [What this area will contain] + [How to get started]
| Channel | Formality | Example |
|---|---|---|
| Legal/Terms | High | "The Service Provider shall..." |
| Product docs | Medium | "To create an invoice, navigate to..." |
| Blog post | Medium | "Here is a smarter way to handle..." |
| Landing page | Medium | "Get paid faster with automated..." |
| Email campaign | Low-Med | "Hi Sarah, quick update on..." |
| Social media | Low | "Month-end closing in 2 hours. Yes, really." |
| Error message | Medium | "Something went wrong. Try refreshing." |
Clarity: Understandable to unfamiliar reader? Every sentence necessary? No ambiguity? Persuasion: Clear value prop? Benefits not just features? Social proof? Single clear CTA? Voice: Tone matches channel/audience? Active voice? Varied sentence length? SEO: Headline includes keyword? Meta description compelling? Headings structured H1>H2>H3? Accuracy: Claims factual? Statistics sourced? Product details current? Pricing correct? Accessibility: Inclusive language? Acronyms defined? Scannable (short paragraphs, bullets)?