writing-readmes

Generate standardized READMEs for packages in monorepos and multi-package projects.

9|2|Updated Apr 13, 2024
One-click install
npx skills add https://github.com/JacobLey/leyman --skill writing-readmes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-readmes
Source: https://github.com/JacobLey/leyman/tree/main/.claude/skills/writing-readmes
Command: npx skills add https://github.com/JacobLey/leyman --skill writing-readmes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Every published package needs a readable README that serves two audiences: developers who need to understand what it does and how to use it, and AI agents that require precise API details. This skill provides a concise, actionable framework to create and maintain READMEs that are consistent across a monorepo.

Core Features & Use Cases

  • Standard README structure templates covering install, usage, API, and cross-package references.
  • Guidance on differentiating README content from WHY files, including when to create WHY-<PACKAGE>.md.
  • Rules for updating READMEs to reflect API changes and new features, ensuring consistency and ease of maintenance.

Quick Start

Draft a concise, developer-focused README for a new package that clearly communicates the purpose, usage, and API details.

Frequently Asked Questions about writing-readmes

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

FAQPage Schema
How do I structure a README for a published package?

To structure a package README, use a standard template covering install, usage, API details, and cross-package references. This ensures consistency and readability for both developers and AI agents across monorepos and multi-package projects.

What is the difference between a README and a WHY file?

A README explains what a package does and how to use it, while a WHY file documents the architectural decisions. You should create a WHY-<PACKAGE>.md file to separate design rationale from actionable API and usage documentation.

How do I maintain markdown documentation across a monorepo?

To maintain markdown documentation across a monorepo, apply standard README structure guidelines and update files whenever API changes or new features occur. This enforces consistency and eases maintenance across all published packages.

When should I update a package README?

You should update a package README whenever there are API changes or new features. Keeping documentation aligned with the codebase ensures the structure, usage, and maintenance rules remain accurate for developers and AI agents.

Does this README template work for multi-package projects?

Yes, this README template works for multi-package projects. It provides a concise, actionable framework to standardize documentation, including cross-package references, ensuring consistency across all packages in a monorepo environment.