ascii-cli-logo-banner

When to use this skill

CRITICAL TRIGGER RULE

• Use this skill ONLY when the user explicitly mentions the exact skill name: ascii-cli-logo-banner.

Use this skill when the user says they want:

• A startup banner / logo / welcome screen for a CLI or service

Trigger phrases include:

• "ascii-cli-logo-banner"
• "use ascii-cli-logo-banner"
• "Use ascii-cli-logo-banner"
• "Use ascii-cli-logo-banner to generate a startup banner"
• "Use ascii-cli-logo-banner to make an ASCII logo"

Boundary

• This skill is a routing/selection entry point. It does not provide its own generator implementation.
• For built-in (no external font engine): use ascii-cli-logo-banner-python.
• For TAAG/FIGlet style (FIGfont spec, smushing layouts): use ascii-cli-logo-banner-figletjs.

How to use this skill

Inputs (recommended)

• brandName (required)
• version (optional)
• author (optional)
• repoUrl / docsUrl (optional)
• width (default 80)
• slogan (optional, centered line under the logo)
• hint (optional, centered line under the slogan)
• glyph (ascii | block, default ascii)
• center (default true)
• rule (default true; set false for logo-only hero output)
• style (block | outline | thin, default block)
• colorMode (none | ansi256, default none; logo only in scripts)
• includeCta (default true)

Outputs (required)

• bannerPlain: ASCII-only full banner (logo area + info block + horizontal rule)
• compactPlain: compact banner for width < 60 (single-line title + rule + 1-2 info lines)
• plainTextFallback: no-color fallback when ANSI is enabled (same structure as bannerPlain)
• embedNotes: 3-5 embedding notes (CLI start / service start / README / tickets)

Steps

1. Decide width and fallback:
   • Default width=80
   • If width < 60, output compactPlain and skip the big-letter logo
2. Generate an ASCII-only logo:
   • Avoid full-width characters and ambiguous-width Unicode
   • Ensure each line is <= width
3. Compose the banner structure (recommended order):
   • Logo area (or a single-line title in compact mode)
   • Horizontal rule: exactly width characters (- or =)
   • Info block: Name / Version / Repo / Docs / Author (only include fields provided)
   • Optional CTA: e.g. Run: <command> or Docs: <url>
4. Optional ANSI coloring (must not break alignment):
   • Colorize visible characters only; do not colorize spaces
   • Always provide plainTextFallback

Script (optional)

• Use ascii-cli-logo-banner-python for the Python implementation.
• Use ascii-cli-logo-banner-figletjs for the figlet.js/FIGfont implementation.

Examples

• See examples in the two implementation skills:
  • ascii-cli-logo-banner-python/examples/*
  • ascii-cli-logo-banner-figletjs/examples/*

Quality checklist

1. Does not wrap or misalign at 80 columns; no trailing spaces
2. Copy-pastes cleanly into logs/email/tickets
3. Never prints secrets (tokens, internal URLs, personal data)

Keywords

English: ascii, banner, logo, cli, terminal, startup, welcome, plain text, ansi, no-color Chinese: ASCII, startup banner, terminal banner, CLI logo, welcome page, plain text, ANSI coloring, no-color fallback

Common Gotchas

1. Version compatibility: Pay attention to compatibility between framework versions and dependency libraries; APIs may differ across versions
2. Configuration file format: Configuration file format errors are the most common problem; it is recommended to use your editor's syntax checking
3. Environment variables: Make sure all necessary environment variables are set correctly, and do not hard-code sensitive information
4. Dependency conflicts: When multiple versions coexist, watch out for dependency conflicts; use a lock file to pin versions
5. Performance pitfalls: In large-data scenarios, pay attention to performance optimization and avoid common problems such as N+1 queries

Usage workflow

Step 1: Environment preparation

Make sure the necessary dependencies and tools are installed in the development environment.

Step 2: Configuration initialization

Perform basic configuration according to project requirements.

Step 3: Using core features

Implement the core features according to the example code.

Step 4: Testing and verification

Run tests to ensure the functionality works properly.

Step 5: Deployment and launch

After completing development, proceed with deployment and monitoring.