diataxis:readme

Generate repository README landing pages that map readers to deeper documentation.

2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/jayteealao/agent-skills --skill diataxis-readme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diataxis:readme
Source: https://github.com/jayteealao/agent-skills/tree/main/plugins/sdlc-workflow/skills/readme-writer
Command: npx skills add https://github.com/jayteealao/agent-skills --skill diataxis-readme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write README front doors that orient readers and route them to deeper docs, without becoming a tutorial or full reference manual.

Core Features & Use Cases

  • Creates a concise repository landing page with project name, elevator pitch, audience, and a clear documentation map.
  • Guides readers to tutorials, how-tos, references, and explanations as needed.
  • Works for open source projects, libraries, and small teams needing a scalable docs homepage.

Quick Start

Generate a README landing page skeleton with sections and a clear map to deeper documentation.

Frequently Asked Questions about diataxis:readme

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

FAQPage Schema
How do I write a README that routes readers to deeper documentation?

To write a README that routes readers to deeper documentation, generate a concise landing page skeleton with an elevator pitch, core features, and a clear map linking to tutorials, how-tos, and references.

What is the Diataxis framework for structuring a repository landing page?

The Diataxis framework structures a repository landing page as a front door that orients readers, routing them to distinct documentation types like tutorials, how-tos, references, and explanations rather than acting as a full manual.

Can I use this approach to generate a README for a small team or open source project?

Yes, you can use this approach for open source projects, libraries, and small teams needing a scalable documentation homepage that orients readers without becoming a tutorial or full reference manual.

What sections should a GitHub README include as a project front door?

A GitHub README acting as a project front door should include a problem statement, project name, elevator pitch, target audience, core features, a quick-start example, and a documentation map.

When should I avoid putting tutorials directly in my README landing page?

You should avoid putting tutorials directly in your README landing page when the goal is to orient readers and route them to deeper docs, keeping the front door concise rather than acting as a full reference manual.