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/section-weight-calibration.md
View on GitHub# Section weight calibration
How long sections should be relative to each other, varying by format. The audit pattern that catches structural imbalance, and the underlying principle that section weight should match argumentative load.
Most long-form pieces fail at section weight before they fail at any other dimension. A 6,000-word whitepaper with seven sections of similar length signals that the writer treated each H2 as a quota rather than as an argument-bearing unit. The pieces that read as publication-quality are the ones where some sections breathe and others compress, where argumentative load is reflected in word count, and where filler sections were cut rather than evened out.
---
## The underlying principle
Section weight should match how much argumentative load the section is bearing.
Throat-clearing introductions get cut or compressed. Setup sections that orient the reader without making the argument yet are short. Body sections that are doing the actual work of the piece are longest. Closings are specific and tight. When section weights deviate from this, the piece is either padded (sections doing too little for their length) or under-developed (sections doing too much for their length).
The audit is straightforward. For each section, ask: what argumentative work is this section doing, and is the word count proportional to that work? Sections doing little work that take up much space are filler. Sections doing much work that take up little space are under-developed.
---
## Whitepaper / research report typical weights
For a 5,000-word whitepaper or research report.
- **Introduction.** 8-12%. Roughly 400-600 words. Thesis stated, scope set, why the piece exists.
- **Methodology or framing.** 10-15%. Roughly 500-750 words. How the analysis works, what data the argument rests on, what the reader should know about how the writer arrived at the position.
- **Body.** 60-70%. Roughly 3,000-3,500 words. Divided into 3-5 weighted sections. The actual argument or findings. The largest body sections are the load-bearing ones; smaller body sections support or transition.
- **Implications.** 10-15%. Roughly 500-750 words. What the argument means for the reader's situation.
- **Closing.** 3-5%. Roughly 150-250 words. Specific call, reframed thesis, or open question.
---
## Case study typical weights
For a 3,000-word case study.
- **Setup and context.** 15-20%. Roughly 450-600 words. The company, the problem, why the problem mattered, what was at stake.
- **Solution narrative.** 50-60%. Roughly 1,500-1,800 words. What the team did, in sequence, with the decision points that mattered.
- **Outcomes.** 15-20%. Roughly 450-600 words. Quantified results, what worked beyond expectations, what did not work as planned.
- **Reflection.** 5-10%. Roughly 150-300 words. What the team would change, what limits the case's applicability.
The case-study weight discipline. The setup and the outcomes can be roughly even; the solution narrative is the longest section because it is doing the most work; the reflection is short because it is concentrated honest assessment.
---
## Manifesto typical weights
For a 3,500-word manifesto.
- **Position.** 5-10%. Roughly 175-350 words. What is believed, stated early and clearly. Manifestos that bury the position lose readers before the argument starts.
- **Argument.** 70-80%. Roughly 2,450-2,800 words. Why, with the layers building intensity. The argument's later layers should be more intense, more specific, or more confrontational than the earlier layers; intensity that flattens loses momentum.
- **Call.** 10-15%. Roughly 350-525 words. What should change as a result of accepting the position, who should change it, what the writer asks of the reader.
The manifesto weight discipline. Position is short and load-bearing. Argument is long and intensifies. Call is specific and demands action or position-taking from the reader.
---
## Definitive guide typical weights
For a 7,000-word definitive guide.
- **Introduction.** 5-8%. Roughly 350-560 words. What the guide covers, who it serves, what reading it costs and pays.
- **Body across taxonomic sections.** 80-85%. Roughly 5,600-5,950 words. Each category in the taxonomy treated with parallel structure. The categories should be roughly even in length unless the taxonomy itself implies asymmetry (some categories are more important than others).
- **Closing and additional resources.** 7-10%. Roughly 490-700 words. Synthesis, recommendation about which categories matter most, pointers to next steps.
The definitive-guide weight discipline. Most of the weight is in the body categories. The introduction is short because the guide's value is in the taxonomy treatment, not in extended setup. The closing's value is synthesis, not recap.
---
## Long-form tutorial typical weights
For a 5,000-word long-form tutorial.
- **Setup.** 10-15%. Roughly 500-750 words. What the reader will achieve, what they need to start, what the success state looks like.
- **Sequential steps.** 70-80%. Roughly 3,500-4,000 words. Each step its own subsection. Steps doing more work get more words; trivial steps stay short. The temptation to even out step lengths produces tutorials that feel padded on simple steps and rushed on hard ones.
- **Troubleshooting and edge cases.** 10-15%. Roughly 500-750 words. What goes wrong, what to do about it, when the reader has likely diverged from the success path.
The tutorial weight discipline. Steps are weighted by actual difficulty, not by parallel structure. The troubleshooting section is load-bearing because tutorials fail at the failure-points; documenting them is the difference between a tutorial that works and one that strands readers.
---
## Ebook typical weights
For a 20,000-word ebook with 8 chapters.
- **Introduction.** 3-5%. Roughly 600-1,000 words. Why the ebook exists, who it serves, how the chapters fit together.
- **Each chapter.** 10-13%. Roughly 2,000-2,600 words per chapter. Chapter weights can vary; a load-bearing chapter at the center may run 3,500 words while a transitional chapter runs 1,500. The variation should reflect actual content load, not arbitrary balancing.
- **Closing chapter or synthesis.** 5-8%. Roughly 1,000-1,600 words. What the body of work amounts to.
The ebook weight discipline. Chapter weights match chapter load; introduction and closing earn their place by doing connective work the body chapters cannot.
---
## The 3x audit
A practical heuristic for catching section-weight problems.
Compare any two sections bearing similar argumentative load. If one is more than 3x the length of the other, the piece is structurally unbalanced. Three responses:
1. **Split the long section.** If the long section is genuinely doing 3x the work, it is probably actually two or three sections that should be separated for the reader's navigation.
2. **Deepen the short section.** If the long section's length is correct, the short section is probably under-developed and the argument it is making is being skipped.
3. **Acknowledge the imbalance.** If the asymmetry reflects an actual content reality (one category in the taxonomy genuinely matters 3x as much as another), the piece can keep the imbalance but should signal it to the reader so the structure does not feel arbitrary.
---
## Common section-weight failures
Patterns that show up repeatedly in long-form drafts.
**Even-section padding.** All H2s come out within 10% of each other in word count. Signal: writer is treating section length as a quota. Cure: identify which sections are actually load-bearing and let them grow while cutting the filler ones back.
**Front-loaded setup.** Introduction is 25% of the piece. Signal: writer was not confident enough in the thesis to commit it early; spent the first quarter of the piece warming up. Cure: cut the introduction by half, lead with the thesis.
**Body imbalance.** One body section is 50% of the piece while three others are 10% each. Signal: either the long section is actually multiple sections that should be separated, or the short sections are filler that should be cut.
**Missing closing.** Closing is 1-2% of the piece. Signal: writer ran out of energy. Cure: rewrite the closing to actual proportional weight; specific call, reframed thesis, or open question.
**Throat-clearing across sections.** Each section starts with 100-200 words of "as we discussed in the previous section" before getting to the section's actual work. Signal: writer is over-managing reader navigation. Cure: trust the reader; cut the recap paragraphs.
**Bullet inflation.** A section's word count comes mostly from bulleted lists where each bullet is one expanded sentence. Signal: writer is using bullets to inflate length without doing the integration work. Cure: rewrite the bullets as prose if the integration matters; cut to a tighter list if the items are genuinely parallel.
---
## Methodology-level choices that stay in the public skill
The underlying principle (weight matches argumentative load), the format-specific weight profiles, the 3x audit, the common section-weight failure patterns and their cures.
## Implementation choices that stay internal
Specific word-count tracking tools the team uses to audit drafts. Specific outline templates with weight targets per section in the team's writing system. Specific reviewer dashboards that surface section-weight imbalance for editorial review. The team's own conventions for which formats run shorter or longer than the typical 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 |