From majestic-engineer
Crafts production-grade README.md files with hero sections, TL;DR, quick starts, comparison tables, troubleshooting, and limitations. Use for project docs, README writing, or open source setup.
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineerThis skill uses the workspace's default tool permissions.
For general technical writing patterns, see `technical-writer` skill.
Drafts, rewrites, or validates README.md files using gold-standard patterns like problem-led hooks, prior art acknowledgment, show-don't-claim demos, and trust blocks. Invoke via /readme, --rewrite, or --validate.
Guides crafting READMEs with processes and templates for OSS, personal, internal, and config projects matched to audience and task (create, update, review).
Provides README.md templates and standards for generating, improving, or checking project documentation compliance. Activates on README creation, audits, or best practices mentions.
Share bugs, ideas, or general feedback.
For general technical writing patterns, see technical-writer skill.
<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 |
## 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.
## 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
### Quick Install (Recommended)
```bash
curl -sSL https://example.com/install.sh | bash
# macOS
brew install mytool
# Linux
apt install mytool # Debian/Ubuntu
dnf install mytool # Fedora
# Windows
winget install mytool
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
Cause: Binary not in PATH.
Fix:
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
<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>
Hero:
Content:
Trust:
| 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 |
Study these for excellent README patterns: