rampstackco/claude-skills / skills/long-form-content-frameworks
long-form-content-frameworks
VerifiedPatterns for individual long-form content pieces. Case studies, whitepapers, research reports, definitive guides, manifestos, ebooks, long-form tutorials. The structural disciplines that distinguish publication-quality long-form from bloggy-long padding or academic bloat. Different from pillar-content-architecture (which covers hub structure); this skill covers individual deep-dive pieces. Triggers on long-form content, case study writing, whitepaper, research report, definitive guide, ebook, manifesto, long-form tutorial, deep-dive article, anchor piece, foundational article, structural archetypes. Also triggers when a piece is over 3,000 words and the team is unsure how to structure it, when a long-form draft feels padded or saggy, or when a flagship asset needs the depth to actually earn the length.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 369 B |
| SKILL.md | skill md | 29.4 KB |
| references/attention-sustaining-techniques.md | markdown | 9.7 KB |
| references/breakouts-and-visualization.md | markdown | 10.4 KB |
| references/citation-and-source-authority.md | markdown | 10.4 KB |
| references/closing-patterns.md | markdown | 12.0 KB |
| references/common-long-form-failures.md | markdown | 11.6 KB |
| references/format-decision-framework.md | markdown | 10.6 KB |
| references/lede-patterns-for-long-form.md | markdown | 9.9 KB |
| references/section-weight-calibration.md | markdown | 9.4 KB |
| references/structural-archetype-patterns.md | markdown | 10.4 KB |
references/lede-patterns-for-long-form.md
View on GitHub# Lede patterns for long-form
Five patterns that work, four that fail, and the underlying frame: the first paragraph of a long-form piece is the writer's only sales pitch for the next 30+ minutes of the reader's attention.
Long-form ledes do different work than blog-post ledes. A blog-post lede answers the user's likely query in the first 200 words for SEO. A long-form lede earns attention for the time investment ahead. Both can be true at once (an SEO-driven long-form piece needs to do both), but the long-form discipline is the harder of the two: the lede that answers a query in 200 words is not necessarily the lede that earns 30 minutes of reader attention.
---
## The underlying frame
Treat the first 150-250 words of a long-form piece as the writer's pitch to the reader. The reader is deciding, paragraph by paragraph, whether the time investment is going to be worth it. The lede has to:
- Establish that the writer has something specific to say (not a survey).
- Set the thesis or central question the body will deliver.
- Earn enough attention to get the reader past the first H2.
If the lede does not do these three things, readers leave at the first H2 boundary, before the body has a chance to deliver.
---
## Pattern 1: The contested-claim opener
**Shape.** A surprising or contested position stated cleanly, then the rest of the piece argues for it.
**Fits.** Manifestos. Opinionated whitepapers. Position pieces. Long-form analysis where the writer has a specific view.
**Example shape.** "Most teams treating content marketing as a volume problem will continue to underperform their budget through the end of the decade. The discipline that produces durable content programs is the one most teams skip: deciding what NOT to publish."
**Why it works.** The reader's response is "wait, why?" The piece exists to answer that. The contested claim earns the reader's attention because the reader is now invested in seeing whether the argument holds.
**The discipline.** The contested claim must actually be defensible across the piece. Lede claims that the body fails to support produce broken contracts; readers feel deceived.
---
## Pattern 2: The problem-with-stakes opener
**Shape.** A problem stated with the stakes made tangible. The reader sees themselves or their situation in the problem and wants the solution.
**Fits.** Case studies. Problem-solution pieces. Long-form tutorials. Manifestos with a clear opposition.
**Example shape.** "Three months after the migration, organic traffic was down 38%, the team had spent four hundred hours on the project, and nobody could explain where the loss was coming from. The migration had been planned for six months. Every checklist item had been completed. And the search-console graph was still pointing the wrong direction."
**Why it works.** Stakes ground the abstract. The reader feels the problem before reading any solution, which earns attention for the solution that follows.
**The discipline.** The stakes must be real, not invented for dramatic effect. Inflated stakes ("the future of marketing is at stake") read as filler. Specific stakes ("the migration cost $400K and three quarters of trust with the executive team") read as honest.
---
## Pattern 3: The data-anomaly opener
**Shape.** A piece of data that does not fit the consensus, framed as the question the piece will answer.
**Fits.** Research reports. Analytical whitepapers. Evidence-driven long-form.
**Example shape.** "The median programmatic SEO program in 2025 generated more than 80% of its traffic from fewer than 5% of its pages. The pattern held across e-commerce, B2B SaaS, marketplaces, and travel. This piece is about why."
**Why it works.** The data point creates a specific question. The reader wants the answer. The body's job is to deliver the answer with the analytical depth the question deserves.
**The discipline.** The data point must be load-bearing. If the body's argument does not actually flow from the opening data, the lede was decoration rather than scaffolding.
---
## Pattern 4: The scene opener
**Shape.** A specific moment, person, or scene that grounds the abstract topic. The reader enters the piece through a concrete situation, and the abstract argument follows.
**Fits.** Narrative-arc pieces. Magazine-style longform. Pieces where human stakes are part of the argument. Some manifestos.
**Example shape.** "On a Tuesday morning in September 2024, two engineers stood in front of a whiteboard covered in arrows and tried to explain to the new VP what the data pipeline actually did. The VP had been at the company three weeks. The whiteboard had been there four years. Neither of them could finish a sentence without contradicting the other."
**Why it works.** Specific scenes hold attention. Readers complete narrative-arc pieces at higher rates than other archetypes; the scene opener uses that pull from the first paragraph.
**The discipline.** The scene must connect to the piece's argument. Scene openers that are decorative ("imagine you are a marketer in 2026...") rather than load-bearing waste reader attention on prelude.
---
## Pattern 5: The orientation opener
**Shape.** What this piece covers, who it is for, what reading it costs and what it delivers. Orientation, not throat-clearing.
**Fits.** Definitive guides. Long-form tutorials. Reference-type long-form where the reader's first question is "is this the right resource for me."
**Example shape.** "This guide is for engineering leaders deciding whether to migrate from a service mesh to a sidecar-less alternative. It assumes familiarity with Kubernetes and basic mesh concepts. Reading it costs about 30 minutes. It will not cover the original arguments for adopting a mesh; that is a different question. It will cover the migration decision: when it makes sense, what to expect, what fails."
**Why it works.** Reference-type readers self-select on relevance. The orientation opener saves the wrong reader's time and earns the right reader's attention. Pieces that the right reader does not finish often fail because the wrong readers came in and the right readers left.
**The discipline.** The orientation must be honest. Guides that overpromise relevance ("for anyone interested in cloud infrastructure") draw wrong readers; guides that underpromise lose right readers.
---
## Failure 1: The throat-clear opener
**Shape.** "Content marketing has changed dramatically over the past decade. In this article, we will explore how to..."
**Why it fails.** Filler signal. The reader knows the piece is about content marketing because of the title; restating it wastes attention. The "in this article we will explore" frame is a tour, not an argument; readers respond to arguments more than to tours.
**The cure.** Cut the throat-clear paragraphs entirely. The piece's actual first sentence is usually the third or fourth paragraph of the throat-clear draft.
---
## Failure 2: The dictionary-definition opener
**Shape.** "According to Merriam-Webster, X is defined as..."
**Why it fails.** Signals an unwillingness to commit a position. The reader assumes the writer does not have a specific framing of their own and is hiding behind the dictionary's framing. For long-form, this is fatal: long-form earns reader attention through specific framing.
**The cure.** State the writer's framing. If the writer needs to disambiguate the term, do so in their own words after stating their position.
---
## Failure 3: The history-of-the-topic opener
**Shape.** Three or four paragraphs of background before the argument starts.
**Why it fails.** Long-form readers tolerate background but only after they know why they should care. Front-loading background means the reader leaves before the thesis lands. The history-of-the-topic opener typically reflects the writer's research process leaking into the piece structure: the writer learned the history while researching, so they put it first, even though the reader does not need it first.
**The cure.** Move history into the body where it supports specific claims. Lead with the thesis or the question the piece answers.
---
## Failure 4: The "in this article we will discuss" tour opener
**Shape.** "In this article, we will discuss A, then B, then C, then D, then conclude with E."
**Why it fails.** Flattens the piece into an outline before the writer has earned attention. Tours signal a writer who is not confident the body will hold the reader, so they preview it. The preview itself is what loses the reader: outlines are less interesting than the argument they describe.
**The cure.** Trust the body to deliver. If the piece needs a navigation aid, use a table of contents or jump links, not an opening tour.
---
## The lede audit
A short framework for auditing a draft lede.
1. **Does the first paragraph establish a specific position, problem, data point, scene, or orientation?** If it does general throat-clearing instead, cut.
2. **By the end of the first 250 words, has the thesis or central question of the piece been stated?** If not, the lede is too long.
3. **Does the lede earn the reader's next 30 minutes?** Read the lede as a stranger to the topic. Would you keep reading? If you would skim, the lede is filler.
4. **Does the body deliver on the lede's promise?** Some failed ledes are technically fine but make promises the body does not keep. The audit happens after the body is drafted: does the lede's framing match what the piece actually argues?
---
## Methodology-level choices that stay in the public skill
The five patterns and the four failures, the underlying frame, the lede audit, the format-tendency mapping, and the lede-body integrity discipline.
## Implementation choices that stay internal
Specific lede templates the team has built. Specific draft-review tooling that flags throat-clearing language patterns automatically. Specific A/B testing of lede variants against engagement metrics. The team's own conventions for lede-length norms within the bands. These vary by team and tooling.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |