readme-craft
Production-grade README.md patterns for any project type. Use when creating project documentation, writing README files, or improving existing docs. Covers hero sections, quick start examples, comparison tables, troubleshooting guides, and limitation transparency. Triggers on README, documentation, project setup, open source.
What this skill does
# README Craft For general technical writing patterns, see `technical-writer` skill. ## Common Failures - Installation first -> Lead with TL;DR and value prop - Describes what it IS -> Describe what problem it SOLVES - No examples -> One example per feature minimum - Hidden limitations -> Dedicated limitations section - Single install method -> Three+ pathways ## Golden Structure ### Tier 1: Hero Section ```markdown <p align="center"> <img src="logo.png" width="200" alt="Project Name"> </p> <p align="center"> <a href="..."><img src="https://img.shields.io/..." alt="CI"></a> <a href="..."><img src="https://img.shields.io/..." alt="Version"></a> <a href="..."><img src="https://img.shields.io/..." alt="License"></a> </p> <p align="center"> <b>One-line description of what problem this solves</b> </p> ```bash curl -sSL https://example.com/install.sh | bash ``` ``` Badge templates: see [references/badge-reference.md](references/badge-reference.md) ### Tier 2: TL;DR ```markdown ## TL;DR **Problem:** [Specific pain point users face] **Solution:** [How this tool solves it] | Feature | Benefit | |---------|---------| | Feature 1 | Quantified benefit | | Feature 2 | Quantified benefit | | Feature 3 | Quantified benefit | ``` ### Tier 3: Quick Start ```markdown ## Quick Start # 1. Install curl -sSL https://example.com/install.sh | bash # 2. Initialize mytool init # 3. Run core workflow mytool process input.txt --output result.json # 4. Verify mytool status ``` **Rule:** 5-10 commands demonstrating the core workflow. ### Tier 4: Reference Sections - Philosophy/Design decisions - Alternatives comparison - Installation (multiple methods) - Command reference - Configuration options - Architecture (for complex systems) ### Tier 5: Support Sections - Troubleshooting - Limitations - FAQ - Contributing - License ## Section Templates ### Comparison Table ```markdown ## Why [Tool] Over Alternatives? | Feature | [Tool] | Alternative A | Alternative B | |---------|--------|---------------|---------------| | Speed | 50ms | 200ms | 150ms | | Memory | 10MB | 50MB | 30MB | | Feature X | Yes | No | Partial | **Choose [Tool] when:** [specific use case] **Choose Alternative A when:** [specific use case] ``` ### Installation (Multiple Methods) ```markdown ## Installation ### Quick Install (Recommended) ```bash curl -sSL https://example.com/install.sh | bash ``` ### Package Managers ```bash # macOS brew install mytool # Linux apt install mytool # Debian/Ubuntu dnf install mytool # Fedora # Windows winget install mytool ``` ### From Source ```bash git clone https://github.com/user/mytool cd mytool make install ``` ``` ### Command Reference ```markdown ## Commands ### Global Flags | Flag | Description | |------|-------------| | `-v, --verbose` | Increase output verbosity | | `-q, --quiet` | Suppress non-error output | | `--config PATH` | Use custom config file | ### `mytool init` Initialize a new project. ```bash mytool init # Interactive setup mytool init --template minimal # Use template mytool init --force # Overwrite existing ``` ``` ### Troubleshooting ```markdown ## Troubleshooting ### Error: "Permission denied" **Cause:** Installation script lacks execute permissions. **Fix:** ```bash chmod +x install.sh ./install.sh ``` ### Error: "Command not found" **Cause:** Binary not in PATH. **Fix:** ```bash export PATH="$HOME/.local/bin:$PATH" # Add to ~/.bashrc or ~/.zshrc for persistence ``` ``` ### Limitations ```markdown ## Limitations **Current constraints:** | Limitation | Workaround | Planned Fix | |------------|------------|-------------| | Max 10MB files | Split large files | v2.0 | | No Windows GUI | Use WSL | Under review | | Single-threaded | Use multiple instances | v1.5 | **Out of scope:** - Feature X (use [Alternative] instead) - Feature Y (not planned) ``` ### FAQ ```markdown ## FAQ <details> <summary><b>Q: How does this compare to [Alternative]?</b></summary> [Tool] focuses on [specific strength], while [Alternative] excels at [different use case]. </details> ``` ## Pre-Publication Checklist **Hero:** - [ ] Logo/image present - [ ] Badges current and working - [ ] One-liner describes the problem solved - [ ] Quick install command visible **Content:** - [ ] TL;DR within first scroll - [ ] Every feature has an example - [ ] Code blocks are copy-paste ready - [ ] 3+ installation methods documented **Trust:** - [ ] Comparison with alternatives (honest) - [ ] Limitations documented - [ ] Top 5 errors in troubleshooting - [ ] All links verified ## Anti-Patterns | Do NOT | Do Instead | |--------|------------| | Start with installation | Start with value proposition | | "This tool is a..." | "This tool solves..." | | Screenshot-only demos | Executable code blocks | | Claim without example | Example per feature | | Hide limitations | Dedicated section | ## Reference Examples Study these for excellent README patterns: - **ripgrep** - Benchmark data, comparison matrices - **bat** - Feature highlights, visual demos - **starship** - Configuration presets, install matrix - **jq** - Tutorial progression, manual linking
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.