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/breakouts-and-visualization.md
View on GitHub# Breakouts and visualization
Visual element types for long-form, the earned-position rule, the production-tax discipline, and the stock-image-header anti-pattern. The patterns that distinguish visual rhythm from visual clutter.
Long-form earns visual breakouts; blog posts often do not. A 1,500-word blog post can carry one image; a 5,000-word whitepaper can carry six or eight visual elements before they feel like clutter. The discipline is not visual count but earned position: which visuals carry argumentative load, and which are decoration.
---
## Visual element types
Six categories, each with different work to do.
**Charts and graphs.** Data visualization that conveys patterns the prose alone cannot convey efficiently. Line charts for time series, bar charts for comparisons, scatter plots for correlations, distributions for spread. The chart's value is showing the pattern; if the prose can summarize the pattern in one sentence and the chart adds nothing, the chart is decoration.
**Diagrams.** Relationships, flows, architectures, taxonomies that benefit from visual structure. Process diagrams, system architectures, hierarchical relationships, decision trees. The diagram's value is making structure visible; topics with simple linear structure rarely need diagrams.
**Pull quotes.** Moments where a single sentence deserves visual weight. Used sparingly for emphasis; one or two per long-form piece typical. The pull quote's value is signaling "this matters"; using pull quotes too often dilutes the signal.
**Sidebars.** Tangential but valuable context that does not fit the main thread. Background detail, related concepts, optional deeper coverage. The sidebar's value is letting the main thread stay focused while preserving context for readers who want it.
**Tables.** Comparison data, structured reference material. Side-by-side option comparisons, parameter listings, multi-axis evaluations. The table's value is making parallel data scannable; tables for non-parallel data are confusing.
**Inline callouts.** Definitions, warnings, "if you only read one section" pointers. Short, focused, specific. The callout's value is interrupting flow for a specific purpose; callouts without specific purpose are decoration.
---
## The earned-position rule
Each visual element earns its place by carrying argumentative load the prose alone cannot.
**Earned visuals.**
- A chart that shows a pattern the prose can only summarize in vague terms ("increasing over time" becomes specific with the line chart).
- A diagram that makes a complex relationship instantly visible (a system architecture; a process flow with decision points).
- A pull quote that captures a position the writer wants to stand alone for emphasis.
- A sidebar with context that would derail the main thread if inline.
- A table that makes parallel comparison instant when the prose would require careful reading.
**Decorative visuals.**
- A chart that restates a number the prose just stated (the chart adds visual interest, not information).
- A diagram of a relationship the prose described in one sentence ("the marketing funnel" diagrammed, when the prose said "marketing has stages").
- A pull quote of a sentence that did not deserve standalone weight.
- A sidebar with information that should have been cut entirely or integrated into the main thread.
- A table where the rows or columns are not actually parallel.
- A stock image at the top of the piece that signals only that the writer wanted a hero image.
The audit. For each visual, ask: does cutting this visual lose information or capability that the prose alone cannot replace? If yes, the visual is earned. If no, the visual is decoration.
---
## Production tax
Visual elements cost more than writers often estimate.
**Per-visual costs.**
- Design time. Even simple charts require choices about color, scale, labeling, formatting.
- Accessibility work. Charts need alt text or alternative-format descriptions; tables need proper header markup; complex visuals need text equivalents.
- Revision overhead. When the data changes, the chart changes. When the framing changes, the diagram changes. Visual elements that go stale because they were not updated when the underlying content changed are worse than no visuals.
- Production review. Editors review prose; design or production review visuals. Pieces with many visuals need more review cycles.
**The capacity audit.** Before committing to a visual count for a piece, check: does the team have the design capacity, the data-engineering capacity (for charts based on data), and the maintenance capacity to keep this number of visuals current? Pieces that ship with 12 visuals and decay because nobody updates them are worse than pieces that ship with 4 visuals that stay current.
**The MVP-visuals approach.** Plan the minimum viable visual count: which visuals are load-bearing for the argument, which would be nice to have, which would be decoration. Ship the load-bearing ones. Add nice-to-haves only if capacity permits and the piece is genuinely long enough to need more visual rhythm.
---
## The stock-image-header anti-pattern
Generic stock imagery at the top of a long-form piece signals the writer did not commission visual work for the piece.
**The pattern.** A whitepaper opens with a generic stock photo of "diverse business team meeting around laptop with charts." The image conveys nothing specific; readers tune it out within milliseconds.
**Why it fails.** Long-form's value proposition includes signaling that the work is serious. Stock imagery undermines the signal: a serious piece would have commissioned specific visual work or skipped the hero image. Stock imagery says "we wanted a hero image and did not invest in one."
**The cure options.**
- Commission specific visual work. Custom illustration matched to the piece's argument. Branded data visualization based on the piece's findings. Scene photography directly related to the piece's case study.
- Skip the hero image entirely. Long-form pieces can open without a hero image; many of the strongest editorial pieces do.
- Use a content-specific opening visual. The first chart in the piece appears at the top, doing dual duty as hero image and load-bearing visual.
The discipline. If the piece's hero image could be on any other piece on the same general topic, it is generic and should be cut or replaced.
---
## Chart conventions for long-form
Charts in long-form pieces have specific expectations.
**Title and caption.** Every chart should have a title that describes what the chart shows and a caption that explains the source of the data. Charts without titles or captions read as decoration.
**Source attribution.** The data behind the chart should be cited. "Source: 2024 Industry Survey, n=412, methodology in appendix" or similar. Charts without source attribution are unverifiable.
**Mobile readability.** Charts should be readable on mobile without horizontal scrolling. Wide charts should be redesigned for mobile or marked as "view on desktop for full detail." Charts that are unreadable on mobile lose mobile readers.
**Color and contrast.** Charts should pass accessibility contrast guidelines (WCAG AA minimum). Color-coded charts need either patterns or labels for readers with color-blindness. Charts that rely on color alone fail accessibility.
**Data integrity.** Truncated y-axes that exaggerate effects, cherry-picked time ranges, and apples-to-oranges comparisons violate the implicit chart contract. Long-form readers who notice deceptive charts lose trust in the entire piece.
---
## Diagram conventions for long-form
Diagrams should make structure visible without becoming the main attraction.
**Simplicity.** A diagram with 30 boxes and 50 arrows is a diagram nobody reads. Diagrams should be visually parse-able in seconds. Complex topics may need multiple simple diagrams rather than one comprehensive one.
**Labeling.** Every box, arrow, and group should be labeled clearly. Diagrams with unlabeled elements assume the reader can infer the labels from context, which often fails.
**Reading order.** Diagrams should have an obvious reading order (top to bottom, left to right, or numbered steps). Diagrams without obvious reading order leave readers uncertain how to traverse them.
**Mobile rendering.** Wide diagrams that work on desktop become unreadable on mobile. Either redesign for mobile, accept that mobile readers will scroll, or split into multiple smaller diagrams.
---
## Sidebar conventions
Sidebars should be visually distinct from the main thread but not overwhelming.
**Length.** Most sidebars run 100-300 words. Sidebars longer than 500 words probably should have been their own section in the main thread or their own piece.
**Visual treatment.** Background color or border that distinguishes the sidebar from main prose. Different typography weight or font (where the design system supports it).
**Skip-readability.** Sidebars should be skippable without losing the main argument. If the main argument depends on the sidebar's content, that content belongs in the main thread, not in a sidebar.
---
## Pull-quote discipline
Pull quotes should be earned moments, not decoration.
**Selection.** A pull quote is a sentence the writer wants to stand alone for emphasis. It should be a sentence whose weight justifies the visual treatment. Generic sentences pulled into pull-quote treatment dilute the device.
**Frequency.** One or two pull quotes per long-form piece is typical. Three or four can work for very long pieces (8,000+ words). More than that and the device loses meaning.
**Attribution within pull quotes.** Pull quotes from interviews or external sources need attribution; pull quotes of the writer's own sentences do not need attribution but should still earn the visual weight.
---
## Methodology-level choices that stay in the public skill
The six visual element types and their work, the earned-position rule, the production-tax discipline, the stock-image-header anti-pattern, the chart conventions, the diagram conventions, the sidebar and pull-quote discipline, the MVP-visuals approach.
## Implementation choices that stay internal
Specific design tokens for charts in the team's brand system. Specific charting libraries the team uses. Specific accessibility-checking automation. Specific design-review workflow for visual elements. Specific custom-illustration commissioning processes. Specific stock-photo blocklist or sourcing guidelines. The team's own visual-budget conventions per format. These vary by team, design capacity, 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 |