⌘ K
10 templates · variables · shuffle

Generate a repo tagline

Fill in category, audience, tone, value — get six punchy one-liners suitable for GitHub bios, npm descriptions, and pitch decks.

Repo Tagline Generator
Variations
6
per shuffle
Avg length
46
chars
Total
279 B
10 templates
Seed
0
shuffles
input · variables
output · 6 variations
From developers, for developers. A CLI you'll actually enjoy.
Battery-included CLI for developers — type-safe out of the box.
CLI done right: type-safe, zero deps, and fast.
Tiny CLI. type-safe. fast.
A fast CLI for developers.
CLI, built for developers who care about type-safe.
Quick Start

How to draft a tagline

Set the seven variables, hit shuffle for fresh phrasing, copy the one you like.

  1. 01

    Define category

    What the project IS — CLI, library, design system.

    Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.

    nounGFMmarkedCommonMarklive
    input · markdowncategory · GFM
    CLI
    loaded · GFMGFM · ready
  2. 02

    Pick audience

    Who it's for — developers, designers, product teams.

    Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.

    whosoft-breaksoptionsconfiglive
    input · optionsaudience · live
    developers
    options applied · livelive
  3. 03

    Tone and value

    One adjective + one promise. Keeps the line specific.

    The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.

    voicepreviewscoped CSSrenderstable
    tone · renderedfast · ready
    fast · type-safe
    rendered · liverendered
  4. 04

    Shuffle and copy

    Hit shuffle until one clicks, then copy.

    Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.

    exportclipboard.md.htmlblob
    ✓ · exportedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Related toolsREADME GeneratorProfile READMEBadge GeneratorChangelogMD EditorCheatsheet
Use Cases

When to draft a tagline

GitHub bios, npm descriptions, decks, websites.

GitHub repo description

First line under the repo name — surface what it does fast. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

npm description

package.json description field shows in search results. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

Pitch deck

One slide, one line. Variations help you A/B before printing. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Landing page

Hero subtitle — give visitors the one-line story. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

Twitter bio

Project account bios — pithy works best. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Internal kickoff

Articulate the why in one sentence before building. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly
FAQ

Frequently asked questions

No — they're rule-based template fills. Shuffle picks six from a pool of ten.
Enough to spot patterns and pick a favourite, few enough to scan.
Not yet — but you can copy a generated line and tweak by hand.
GitHub limits descriptions to ~256 chars; npm shows ~150. Our templates land well under both.
No — the generator runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!