markdown-pro
Professional Markdown documentation skill for creating polished README files, changelogs, contribution guides, and technical documentation. Use for: (1) README generation with badges and sections, (2) Automated changelog from git history, (3) Table of contents generation, (4) Contribution guidelines, (5) Technical documentation formatting, (6) Code documentation with syntax highlighting
What this skill does
# Professional Markdown Documentation
## Overview
This skill provides comprehensive guidance for creating professional, well-structured Markdown documentation. It covers README files, changelogs, contribution guides, and technical documentation with modern formatting, badges, and best practices.
## Core Capabilities
### README Generation
- Project overview and description
- Installation instructions
- Usage examples with code blocks
- API documentation
- Badges and shields
- Feature highlights
- Screenshots and demos
### Changelog Automation
- Semantic versioning format
- Git history parsing
- Automated release notes
- Breaking changes highlighting
- Contributor attribution
### Technical Documentation
- Clear section hierarchy
- Code syntax highlighting
- API reference formatting
- Table of contents
- Cross-referencing
- Collapsible sections
## README Structure Best Practices
### Essential Sections
**1. Header with Badges**
```markdown
# Project Name
[](LICENSE)
[](releases)
[](builds)
Brief one-line description of what the project does.
```
**2. Table of Contents** (for longer READMEs)
```markdown
## Table of Contents
- [Features](#features)
- [Installation](#installation)
- [Usage](#usage)
- [API Reference](#api-reference)
- [Contributing](#contributing)
- [License](#license)
```
**3. Features Section**
```markdown
## Features
- **Feature 1**: Clear description with benefits
- **Feature 2**: What problems it solves
- **Feature 3**: Unique selling points
- Cross-platform support (Windows, macOS, Linux)
- Comprehensive test coverage (>90%)
```
**4. Installation Instructions**
```markdown
## Installation
### Prerequisites
- Python 3.8 or higher
- pip package manager
### Quick Start
```bash
pip install package-name
```
### From Source
```bash
git clone https://github.com/username/repo.git
cd repo
pip install -e .
```
```
**5. Usage Examples**
```markdown
## Usage
### Basic Example
```python
from package import Module
# Initialize
client = Module(api_key="your-key")
# Perform operation
result = client.process(data)
print(result)
```
### Advanced Usage
See [examples/](examples/) directory for more detailed use cases.
```
**6. API Documentation**
```markdown
## API Reference
### `Module.process(data, options=None)`
Process input data with optional configuration.
**Parameters:**
- `data` (str|dict): Input data to process
- `options` (dict, optional): Configuration options
- `verbose` (bool): Enable verbose output (default: False)
- `format` (str): Output format - 'json', 'yaml', 'xml' (default: 'json')
**Returns:**
- `dict`: Processed results with metadata
**Raises:**
- `ValueError`: If data is invalid
- `APIError`: If API request fails
**Example:**
```python
result = client.process(
data={"key": "value"},
options={"verbose": True, "format": "json"}
)
```
```
**7. Contributing Section**
```markdown
## Contributing
We welcome contributions! Please see [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
### Quick Contribution Guide
1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request
```
**8. License and Credits**
```markdown
## License
This project is licensed under the MIT License - see [LICENSE](LICENSE) file for details.
## Acknowledgments
- Thanks to [Contributor Name] for feature X
- Inspired by [Project Name](link)
- Built with [Technology Stack]
```
## Changelog Format
### Semantic Versioning Structure
```markdown
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- New feature description
### Changed
- Modification to existing feature
### Deprecated
- Features that will be removed
### Removed
- Deleted features
### Fixed
- Bug fixes
### Security
- Security improvements
## [1.2.0] - 2025-01-15
### Added
- User authentication system (#123)
- Export to CSV functionality (#145)
- Dark mode support (#156)
### Changed
- Updated UI components for better responsiveness (#134)
- Improved error messages (#142)
### Fixed
- Fixed memory leak in background processor (#139)
- Resolved login timeout issue (#148)
## [1.1.0] - 2024-12-01
### Added
- Initial release with core features
```
## Markdown Formatting Best Practices
### Code Blocks with Syntax Highlighting
```markdown
```python
def hello_world():
"""Print hello world message."""
print("Hello, World!")
```
```javascript
function helloWorld() {
console.log("Hello, World!");
}
```
```bash
# Install dependencies
npm install
# Run tests
npm test
```
```
### Tables
```markdown
| Feature | Description | Status |
|---------|-------------|--------|
| Auth | User authentication | โ
Complete |
| API | RESTful API endpoints | โ
Complete |
| Docs | Documentation | ๐ง In Progress |
| Tests | Unit & Integration | โ Planned |
```
### Collapsible Sections
```markdown
<details>
<summary>Click to expand advanced configuration</summary>
## Advanced Options
Configure advanced settings:
```yaml
advanced:
cache_size: 1000
timeout: 30
retry_attempts: 3
```
</details>
```
### Alert Boxes
```markdown
> **Note**: This feature requires Python 3.8 or higher.
> **Warning**: This operation is irreversible!
> **Important**: Always backup your data before upgrading.
```
### Links and References
```markdown
<!-- External link -->
[Documentation](https://docs.example.com)
<!-- Internal link -->
See [Installation](#installation) section.
<!-- Reference-style links -->
Check out [project homepage][homepage] and [documentation][docs].
[homepage]: https://example.com
[docs]: https://docs.example.com
```
### Images
```markdown
<!-- Standard image -->

<!-- Image with alt text and title -->

<!-- Linked image -->
[](https://youtube.com/watch?v=example)
```
## Badge Creation
### Common Badge Patterns
```markdown
<!-- License -->

<!-- Version -->

<!-- Build Status -->

<!-- Coverage -->

<!-- Language -->

<!-- Platform -->

```
## Helper Scripts
### Generate Table of Contents
Use the helper script to automatically generate TOC from headers:
```bash
python scripts/markdown_helper.py toc README.md
```
### Generate Changelog from Git
Automatically create changelog entries from git history:
```bash
python scripts/markdown_helper.py changelog --since v1.0.0 --output CHANGELOG.md
```
### Validate Markdown Links
Check for broken links in documentation:
```bash
python scripts/markdown_helper.py validate docs/
```
## Templates
### Professional README Template
See `examples/README_template.md` for a complete, production-ready README template with all recommended sections.
### Changelog Template
See `examples/CHANGELOG_template.md` for a properly formatted changelog following Keep a Changelog format.
### Contributing Guidelines
See `examples/CONTRIBUTING.md` for contributor guidelines template including code of conduct, development setup, and PR process.
## Best PracticRelated 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.