Content Strategy Patterns

Classify technical documentation content using the Diátaxis model.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/HermeticOrmus/LibreCopy-Claude-Code --skill content-strategy-patterns-hermeticormus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Content Strategy Patterns
Source: https://github.com/HermeticOrmus/LibreCopy-Claude-Code/tree/main/plugins/content-strategy/skills/content-strategy-patterns
Command: npx skills add https://github.com/HermeticOrmus/LibreCopy-Claude-Code --skill content-strategy-patterns-hermeticormus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating clear, effective documentation by providing established frameworks and best practices for organizing and classifying content.

Core Features & Use Cases

  • Diátaxis Framework: Classifies content into Tutorial, How-To, Reference, and Explanation types to meet specific user needs.
  • ROT Analysis: Helps identify content for review (Redundant, Outdated, Trivial) during audits.
  • Single-Source Publishing: Demonstrates techniques for reusing content snippets across multiple documents.
  • Navigation Best Practices: Offers guidance on structuring site navigation for optimal user experience (Rule of 7, 3-click rule).
  • Versioning Strategies: Outlines different approaches to managing content across product versions.
  • Documentation Metrics: Defines key metrics for measuring documentation success.
  • Anti-Patterns: Highlights common mistakes in organizing and writing documentation.

Quick Start

Apply the Diátaxis framework to classify an article by asking what the user is trying to achieve.

Frequently Asked Questions about Content Strategy Patterns

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

FAQPage Schema
How do I classify technical documentation using the Diátaxis framework?

The Diátaxis framework classifies technical documentation into Tutorial, How-To, Reference, and Explanation types based on what the user is trying to achieve. Apply it to an article by determining the user's specific learning need to ensure clarity and impact.

What is ROT analysis and how is it used in a content audit?

ROT analysis is a content audit method used to identify documentation marked as Redundant, Outdated, or Trivial. It helps reviewers pinpoint existing content that requires removal or revision to optimize overall content organization and maintain accuracy.

What are the best practices for structuring technical documentation navigation?

Structuring technical documentation navigation relies on the Rule of 7 and the 3-click rule to optimize depth and breadth. These best practices ensure users can browse site menus efficiently without encountering overwhelming lists or buried reference material.

How do I measure the success of my content strategy and documentation metrics?

Measuring documentation success involves tracking key metrics defined by your content strategy to evaluate clarity and impact. These metrics help assess how effectively your technical writing meets user needs and supports product engagement over time.

What are common anti-patterns in technical writing and content organization?

Common anti-patterns in technical writing include misclassifying content types, ignoring navigation depth limits, and neglecting versioning strategies. Highlighting these frequent mistakes helps teams avoid structuring documentation in ways that confuse users or fragment information.

Can I reuse content snippets across multiple documents with single-source publishing?

Single-source publishing demonstrates techniques for reusing content snippets across multiple technical documents. This approach streamlines versioning strategies and updates by maintaining a central source, ensuring consistent documentation delivery across various formats.