tech-writer

Generate API references, ADRs, and READMEs in markdown.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/0xRayAI/xray --skill tech-writer-0xrayai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-writer
Source: https://github.com/0xRayAI/xray/tree/main/src/skills/tech-writer
Command: npx skills add https://github.com/0xRayAI/xray --skill tech-writer-0xrayai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of maintaining high-quality technical documentation by providing a structured framework for writing API docs, ADRs, and READMEs that stay in sync with your codebase.

Core Features & Use Cases

  • Standardized Documentation: Generate consistent API references, architecture decision records (ADRs), and developer-friendly READMEs.
  • Documentation as Code: Maintain documentation alongside source code to ensure version alignment and facilitate peer review via pull requests.
  • Use Case: When introducing a new architectural change, use this Skill to draft an ADR that captures the context, options, and rationale, ensuring the team remains aligned on the decision-making process.

Quick Start

Use the tech-writer skill to generate a standard README file for the current project directory including a quick start section and installation instructions.

Frequently Asked Questions about tech-writer

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

FAQPage Schema
How do I generate a project README with installation instructions?

To generate a project README, this Skill produces a standard markdown file including a quick start section and installation instructions tailored for developers. It structures your repository context into a developer-friendly format.

What is an architecture decision record and when do I need one?

An architecture decision record (ADR) captures the context, options, and rationale behind an architectural change. You need an ADR when introducing structural changes to ensure your team remains aligned on the decision-making process.

How do I write API references that stay in sync with my codebase?

You can write API references that stay in sync by applying documentation-as-code principles, maintaining markdown files alongside source code to ensure version alignment and facilitate peer review via pull requests.

Does this documentation approach work with markdown-based repository workflows?

Yes, this documentation approach requires adherence to markdown-based documentation-as-code principles for seamless integration into repository workflows. It enforces consistent terminology, active voice, and code-centric formatting.

What is the best way to maintain consistent terminology across developer documentation?

The best way to maintain consistent terminology is to use a structured framework that enforces active voice and code-centric formatting across API docs, ADRs, and READMEs. This eliminates friction and standardizes all technical references.

When should I not use documentation-as-code for technical writing?

You should not use documentation-as-code if your project requires non-markdown formats or operates outside standard repository workflows. This Skill specifically enforces markdown-based formatting and version alignment via pull requests.