---
name: tagline
description: Use when creating or rewriting a repository tagline or short product description from repository evidence or a supplied product brief.
---

# Tagline

Read the shared [workflow and source gate](../write/references/workflow.md) and [editorial guidance](../write/references/editorial.md). Inspect the actual product/package before writing.

Accept `--variants N` (default three) and `--max-chars N` in addition to shared options. A user-specified character limit uses Unicode code-point counting (for example JavaScript `Array.from(text).length`); do not invent a platform limit or promise its counting behavior without verification.

Write `tagline.md` with one recommended line and two meaningfully distinct alternatives unless another count is requested. Target eight to twelve words for the recommended line only when that fits the product. Use category plus job, action plus supported outcome, or an evidenced differentiator; alternatives change emphasis rather than synonyms. Add a separate slightly fuller repository description and one sentence explaining the recommendation outside reusable copy.

Map each candidate to its supporting claims in private records; a sentence linking the source capability and output is enough for the transformation map. Check actual character counts when constrained, product/category comprehension, and every factual implication. Do not invent popularity, speed, superiority, or deployment readiness. Do not change repository metadata without authorization.