メニュー
Generates high-converting landing page copy through a structured interview and section-by-section writing process. Triggers when the user asks to write landing page copy, create a landing page, write marketing copy for a product, or generate conversion-optimized web copy.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Stages the changes produced in this session, excludes junk and secrets, and generates a conventional commit. Triggered when the user runs /devx-git:ci or asks to commit.
Updates the current branch onto an origin branch via rebase, with a recoverable backup, safe conflict resolution, and recovery steps. Use when the user runs /rebase or asks to rebase/update their branch onto main (or another origin branch).
Audits an agent, tool loop, or inference request across six dimensions (prompt engineering, tools definition, context engineering, cache usage, evaluation, guardrails) and produces a scored gap analysis with severity ratings and concrete remediations. Framework-agnostic; recognizes patterns from Anthropic SDK, OpenAI SDK, Vercel AI SDK, and OpenAI Agents SDK. Triggers on: audit my agent, review tool loop, audit inference request, agentic engineering review, audit prompt, review agent code, check prompt caching, evaluate guardrails.
Rewrites a given prompt or agent definition by applying Anthropic prompt-engineering best practices — clarity and directness, context and motivation, XML structure, role assignment, long-context layout, output format control, communication-style calibration, and parallel-tool-call affordance. Produces a before/after with per-change rationale. Triggers on: optimize this prompt, improve my prompt, rewrite prompt, prompt optimization, refine system prompt, tune agent prompt, polish prompt for production.
Analyzes project architecture and generates ASCII state machine and sequence diagrams. Use for explaining a project, analyzing architecture, tracing an entrypoint, showing a state machine, or generating a sequence diagram.
Audits a project's agentic harness (CLAUDE.md, AGENTS.md, .claude/rules, .claude/settings.json) and refactors it into a layered, path-scoped configuration that loads only what is relevant. Rewrites CLAUDE.md and AGENTS.md as a thin critical-rules layer, segments domain rules with `paths:` frontmatter, and adds deny-first permission guardrails. Use for: fixing the harness, auditing claude.md, refactoring agentic configuration, improving agent rules, segmenting rules by path, reviewing settings.json, harness review, or when claude.md is too long.
| name | writing-landing-page-copy |
| description | Generates high-converting landing page copy through a structured interview and section-by-section writing process. Triggers when the user asks to write landing page copy, create a landing page, write marketing copy for a product, or generate conversion-optimized web copy. |
Copy this checklist and track progress:
Workflow Progress:
- [ ] Phase 1: Discovery interview completed
- [ ] Phase 1: Brief confirmed by user
- [ ] Phase 2: Sections selected
- [ ] Phase 3: Copy generated for all selected sections
- [ ] Phase 4: Review pass completed
- [ ] Phase 4: User approved final copy
Conduct a detailed interview before writing any copy. Use AskUserQuestion to gather information in 2-3 rounds.
Ask these questions together:
After gathering answers, summarize the brief back to the user for confirmation before writing.
Present the available sections and let the user choose which to generate. Default to all.
| # | Section | Purpose |
|---|---|---|
| 1 | Hero | First impression - headline, subheadline, CTA |
| 2 | Trust Bar | Authority logos and social proof |
| 3 | Loss Aversion | Pain amplification before solution |
| 4 | Benefits | Outcome-focused value (rule of 3) |
| 5 | Process | How it works in 3 steps |
| 6 | Features | Technical proof and specs |
| 7 | Pricing | Plans, tiers, value framing |
| 8 | Testimonials | Social proof with specifics |
| 9 | FAQ | Objection handling |
| 10 | Final CTA | Closing push with urgency |
Use AskUserQuestion with multiSelect to let the user pick sections. Offer "All sections" as the first option.
Generate each selected section following the detailed guidelines in section-guide.md.
For each section, apply the conversion psychology principles from psychology.md.
ALWAYS use this exact structure for each section:
---
## [Section Name]
> **Psychology**: [Which principle this section leverages]
### Headline
[Main headline text]
### Subheadline / Supporting
[Supporting text]
### Body
[Section body copy]
### CTA (if applicable)
[Button text] | [Supporting microcopy]
---
Apply standard copywriting best practices: clarity over cleverness, benefit-led headlines, specific numbers and timeframes, active voice, scannable formatting, ICP-appropriate language.
Discovery brief (input): Product: ShipFast, CI/CD for small teams. ICP: engineering leads at startups. Problem: slow, fragile pipelines. Differentiator: zero-config auto-detection. CTA: start free trial.
Generated Hero section (output):
---
## Hero
> **Psychology**: Self-Interest (WIIFM) + Social Proof
### Headline
Ship 3x faster without breaking production
### Subheadline / Supporting
The CI/CD platform built for teams that move fast. Set up in 5 minutes, not 5 sprints.
### CTA
Start building free | No credit card required
---
For more complete examples covering all sections, see examples.md.
After generating all sections, run this validation:
Review Checklist:
- [ ] Tone is consistent across all sections
- [ ] All CTAs point to the same primary goal
- [ ] FAQ addresses the top 3 objections from discovery
- [ ] No section duplicates messaging from another
- [ ] Numbers/metrics are specific, not vague
- [ ] Every headline passes the "so what?" test
If issues found, revise the affected sections and re-check. Use AskUserQuestion to ask which refinements the user wants.