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/attention-sustaining-techniques.md
View on GitHub# Attention-sustaining techniques
How long-form pieces hold readers across 5,000+ words. The patterns that keep reader attention across the time investment, and the underlying observation: readers leave because pieces feel uniform.
The pieces that lose readers in long-form are the ones that feel monotone. Same paragraph length, same sentence rhythm, same density of claim, page after page. Even competent writing reads as exhausting under that pattern. The pieces that hold readers vary their density, register, and rhythm so the reader's attention has somewhere to recover and somewhere to engage.
---
## Density variation
Long-form pieces should alternate between argument-tight sections and breathing sections.
**Argument-tight sections.** Claim, evidence, claim, evidence. Specific, direct, intellectually demanding. The reader is doing work to follow the argument.
**Breathing sections.** Reflection, illustration, anecdote, restatement. Lower density of new claims; higher density of integration with what was just argued.
The pattern that holds. After an argument-tight section, a breathing section gives the reader room to absorb. After a breathing section, the reader returns to argument-tight work refreshed. Pieces that are argument-tight throughout exhaust readers; pieces that breathe throughout never feel substantive.
The audit. For each section, characterize it as argument-tight or breathing. If the sequence is all argument-tight, the piece is dense and exhausting. If the sequence is all breathing, the piece is shallow despite its length. The mix is the discipline.
---
## Register variation
Most long-form pieces sustain a primary register while shifting briefly to secondary registers for variation.
**Primary registers.**
- Analytical: claim-evidence-implication, measured tone, distance from the topic.
- Narrative: scene-driven, character-driven, time-progressive.
- Instructional: do-this-then-this, addressed to the reader directly.
- Declarative: positions stated, opinions committed, weight on conviction.
**Secondary registers.** Anecdotal moments inside an analytical piece. Reflective moments inside an instructional piece. A specific scene inside a declarative manifesto. A measured analytical section inside a narrative.
The pattern that holds. A whitepaper sustained in analytical register for 6,000 words exhausts readers; the same whitepaper with a mid-piece anecdote and a closing reflection lands harder. A long-form tutorial sustained in instructional register for 5,000 words feels mechanical; the same tutorial with a brief reflective section on common failures and a personal note from the writer feels human.
The discipline. Choose the primary register first; insert secondary-register moments at section transitions where the shift will refresh attention rather than disorient.
---
## Rhythm variation
Sentence and paragraph length variation matters more in long-form than in short.
**Sentence length.**
- Strings of 25-word sentences blur. The reader's eye glides over the text without the cognitive checkpoints short sentences create.
- Strings of 8-word sentences fragment. The text reads as choppy, and the reader's attention is interrupted constantly.
- The pattern that holds: medium sentences with occasional short punches and occasional layered longer constructions.
**Paragraph length.**
- Long paragraphs (8+ sentences) feel academic. Suitable for argument-tight sections; exhausting if sustained.
- Short paragraphs (1-2 sentences) feel staccato. Suitable for emphasis and for breaking dense passages; fragmenting if sustained.
- The pattern that holds: most paragraphs 3-5 sentences with occasional shorter ones for emphasis and occasional longer ones for layered argument.
**Heading rhythm.** H2 every 600-1,200 words on average. H3 within H2 sections to break navigation. Headings that come at uniform intervals feel mechanical; headings that follow the actual structural breaks feel natural.
The audit. Read the piece aloud. Does the rhythm vary, or does every sentence and paragraph land with the same beat? If the latter, the piece needs rhythm work even if every individual sentence is competent.
---
## Visual rhythm
Long-form pieces with no visual rhythm are walls of text; long-form pieces with too many breakouts feel like marketing collateral.
**The norm.** A visual element every 600-1,000 words on average. Visual elements include subheads, pull quotes, callouts, charts, diagrams, sidebars, tables, and images.
**Variation in type.** All-subheads-no-charts feels under-designed for the piece's length. All-charts-no-pull-quotes feels like a research dump. The visual rhythm should vary: a subhead, then 800 words of prose, then a chart, then 600 words of prose, then a pull quote, then 700 words of prose, then a callout, then 900 words and the next subhead.
**The earned-position rule.** Each visual element earns its place by carrying load the prose alone cannot. Decorative charts that restate the prose visually weaken the piece; charts that surface a pattern the prose can only summarize strengthen it. See `breakouts-and-visualization.md` for the discipline.
**Mobile reading reality.** Long-form on mobile gets read in landscape stretches. Subheads should be visible without scrolling on each major section transition; pull quotes should be visible early to preview the piece's depth; charts should be readable without horizontal scrolling.
---
## Mid-piece micro-thesis
Long-form readers' attention naturally dips around the 40-60% mark. Pieces that survive the dip have a structural move that refreshes engagement at that point.
**The micro-thesis pattern.** Around the midpoint, restate the central claim with new framing. The restatement does three things at once: it reorients readers who have been following sections, it gives drifting readers a checkpoint to re-engage, and it sets up the second half of the piece.
**Worked example.** A whitepaper opens with the claim "Most teams treating content marketing as a volume problem will continue to underperform." At the midpoint, after the structural argument and the first empirical layer, the writer restates: "The pattern across the data is consistent. The teams that broke the volume-first cycle did not produce more; they produced less, and committed harder to what they produced." The reader is reoriented; the second half of the piece can build on the restatement.
**Anti-pattern: the recap micro-thesis.** Restating "as we have seen so far, content marketing is changing" is filler, not micro-thesis. The micro-thesis should add framing or sharpen the claim, not recap.
**Where the micro-thesis sits structurally.** Often at the boundary between two body sections, especially the boundary between the first and second halves of a layered argument or the boundary between the third and fourth chapters of an ebook.
---
## Combining the techniques
A 6,000-word whitepaper using all five techniques.
- **Lede.** Contested-claim opener, declarative register, short paragraphs for opening punch.
- **Setup section.** Analytical register, medium-density argument, 3-5 sentence paragraphs.
- **First body section.** Argument-tight density, analytical register sustained, longer paragraphs as the argument layers.
- **Mid-piece micro-thesis.** A short paragraph that restates the claim with new framing. Brief register shift to declarative.
- **Second body section.** Argument-tight density, but with a worked example inserted as a breathing pause. Worked example shifts briefly to narrative register.
- **Counter-argument section.** Argument-tight again, analytical register, with the counter-arguments engaged seriously.
- **Synthesis.** Density lower, register declarative, paragraphs short and emphatic.
- **Closing.** Declarative, short, specific.
The piece reads as varied across its length even though it is a single sustained argument.
---
## Common attention-loss patterns
Patterns that show up when readers drop off mid-piece.
**The mid-piece sag.** Around the 50% mark, the piece becomes harder to follow. Cause: no micro-thesis, no rhythm variation, the reader is exhausted from sustained argument-tight density. Cure: add micro-thesis at the section boundary nearest the midpoint; insert a breathing section.
**The wall-of-text section.** A 1,500-word body section with no subheads, no visuals, no rhythm variation. Cause: the writer was deep in the argument and stopped attending to the reader. Cure: identify the natural sub-structure within the section, add subheads or visuals at the boundaries.
**The abstract drift.** The piece's specifics decrease as it progresses. Concrete examples in the early sections; vague generalizations in the later sections. Cause: the writer ran low on specific examples; padded with abstraction. Cure: cut to the depth where specificity holds; better a shorter piece with sustained specificity than a longer piece that drifts abstract.
**The energy-decline closing.** The closing reads as a writer who ran out of energy. Cause: writers fatigue before readers do. Cure: write the closing first or revise the closing last with fresh attention; the closing is too important to deliver tired.
---
## Methodology-level choices that stay in the public skill
The five techniques (density variation, register variation, rhythm variation, visual rhythm, mid-piece micro-thesis), the combining pattern, the common attention-loss patterns and their cures, the read-aloud audit.
## Implementation choices that stay internal
Specific draft-review tooling that flags rhythm patterns. Specific reading-time analytics that detect mid-piece drop-off in the team's content. Specific paragraph-length analyzers in the team's writing tool. Specific A/B testing of structural variants. The team's own conventions for visual-element budgets per long-form piece. These vary by team, stack, and analytics setup.
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 |