tufte-integration-of-modes

Analyze document architecture to integrate verbal and visual evidence.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/jpoindexter/tufte-skills --skill tufte-integration-of-modes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tufte-integration-of-modes
Source: https://github.com/jpoindexter/tufte-skills/tree/main/skills/tufte-integration-of-modes
Command: npx skills add https://github.com/jpoindexter/tufte-skills --skill tufte-integration-of-modes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common failure in technical and analytical documentation where evidence is segregated by production convenience (e.g., text in one section, figures in another) rather than by the logic of the argument, causing cognitive load and loss of coherence for the reader.

Core Features & Use Cases

  • Document Architecture Audit: Evaluates whether your report, deck, or interface structure forces readers to chase links between disparate parts to reconstruct a single argument.
  • Evidence Integration Strategy: Provides principles for co-locating words, numbers, and images to ensure the visual evidence directly supports the narrative.
  • Use Case: Use this skill when auditing a complex dashboard or technical report to identify where "Book Operating System" patterns (like excessive navigation instructions or separated appendices) are undermining the clarity of your evidence.

Quick Start

Invoke the tufte integration of modes skill to audit this document for evidence fragmentation and suggest a more coherent layout.

Frequently Asked Questions about tufte-integration-of-modes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is evidence fragmentation in document design?

Tufte's principles of multimodal integration eliminate document fragmentation by co-locating words, numbers, and images so visual evidence directly supports the narrative, ensuring readers do not chase links between disparate parts to reconstruct a single argument.

How do I audit a technical report for mode-separation issues?

You audit a technical report for mode-separation issues by analyzing its document architecture to identify where navigation-heavy apparatus and separated appendices force readers to chase links, then applying evidence integration strategies to co-locate verbal and visual data.

Can I use this approach to fix a complex dashboard layout?

Yes, you can use this approach to fix a complex dashboard layout by auditing it for "Book Operating System" patterns, like excessive navigation instructions, that undermine the clarity of your evidence and segregate visual data from the analytical narrative.

What's the best way to integrate visual evidence with text in technical guides?

The best way to integrate visual evidence with text in technical guides is to co-locate words, numbers, and images according to the logic of the argument, rather than separating them by production convenience, ensuring the visual evidence directly supports the narrative.

When should I not use multimodal integration in document architecture?

You should not use multimodal integration when your document architecture relies on a "Book Operating System" pattern that requires excessive navigation instructions or separated appendices, as eliminating these structures may compromise the intended analytical integrity of your evidence.