markdown-formatting
Format AI outputs into consistent, readable Markdown for PRs, issues, docs, and notes
What this skill does
# Markdown Formatting Skill Apply consistent Markdown formatting to all outputs. Structure content for readability and professionalism. ## When to Use Activate when producing: - PR descriptions and issue bodies - Documentation and guides - Notes and summaries - Any structured text output ## Core Principles 1. **Lead with the point** - TL;DR or summary first, details after 2. **Use structure** - Headings, lists, and whitespace aid scanning 3. **Be consistent** - Same patterns across all outputs 4. **Respect context** - PRs need checklists, docs need examples ## Formatting Rules ### Document Structure ``` # Title (standalone documents only) Brief summary or TL;DR (1-2 sentences) ## Section Heading Content organized by topic... ``` ### Headings - Use `##` for main sections (reserve `#` for document title) - Use `###` sparingly for subsections - Never skip levels (no `##` to `####`) ### Lists - Use `-` for unordered lists (not `*`) - Use `1.` for ordered/sequential steps - Nest with 2-space indent - Keep list items parallel in structure ### Code - Inline: backticks for `commands`, `filenames`, `variables` - Blocks: triple backticks with language identifier - Always specify language: ```typescript, ```bash, ```json ### Emphasis - **Bold** for key terms, warnings, important points - *Italics* sparingly for emphasis or introducing terms - Never combine bold and italics ### Links - Descriptive text: `[installation guide](url)` not `[click here](url)` - Reference issues/PRs with `#123` format ## Templates ### PR Description ```markdown ## Summary [One-line description of the change] ## Changes - [Change 1] - [Change 2] ## Test Plan - [ ] [Test case 1] - [ ] [Test case 2] ``` ### Issue Body ```markdown ## Problem [What is wrong or missing] ## Steps to Reproduce 1. [Step 1] 2. [Step 2] ## Expected [What should happen] ## Actual [What actually happens] ``` ## Anti-patterns - Walls of text without structure - Inconsistent list markers (`*`, `-`, `+` mixed) - Code blocks without language identifiers - Headings used as emphasis - Trailing whitespace or excessive blank lines
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.