new-guide

Draft user-facing documentation using Diátaxis framework quadrant templates.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/phanijapps/engram --skill new-guide-phanijapps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-guide
Source: https://github.com/phanijapps/engram/tree/main/.claude/skills/new-guide
Command: npx skills add https://github.com/phanijapps/engram --skill new-guide-phanijapps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill solves the common frustration of poorly structured documentation by enforcing the Diátaxis framework, ensuring that tutorials, how-to guides, reference pages, and explanations remain distinct and effective.

Core Features & Use Cases

  • Audience-Centric Scaffolding: Automatically gates drafting behind an audience contract to ensure the guide serves a specific reader posture.
  • Quadrant Enforcement: Prevents the common anti-pattern of blending theory with instructions, ensuring content stays within its intended scope.
  • Use Case: Use this when you need to create a new how-to guide for a specific product feature, ensuring it follows the established repository standards for tone, structure, and cross-linking.

Quick Start

Invoke the new-guide skill to draft a how-to guide for rotating an API token by providing the topic and target audience.

Frequently Asked Questions about new-guide

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

FAQPage Schema
What is the Diátaxis framework for technical writing?

The Diátaxis framework structures technical writing into four distinct quadrants—tutorials, how-to guides, reference pages, and explanations—to ensure documentation remains purpose-driven and serves specific reader needs effectively.

How do I write a how-to guide without mixing in theory?

To write a how-to guide without mixing in theory, apply quadrant enforcement from the Diátaxis framework, which prevents blending explanations with instructions and keeps content strictly within its intended scope.

How do I structure technical documentation for a specific audience?

Structure technical documentation for a specific audience by establishing an audience contract first, which defines the reader's posture and ensures the guide serves their exact needs before drafting any content.

Does the Diátaxis framework work for all types of user guides?

The Diátaxis framework works for user guides by categorizing them into tutorials, how-to guides, reference pages, and explanations, ensuring each type maintains its distinct purpose and structure.

What's the best way to create a tutorial versus a reference page?

The best way to create a tutorial versus a reference page is to use quadrant-based templates that enforce the Diátaxis framework, keeping learning-focused tutorials separate from reference material.

When should I not use a how-to guide format for documentation?

You should not use a how-to guide format when the content is reference material or conceptual explanation, as the Diátaxis framework requires keeping these quadrants distinct to maintain documentation integrity.