ascii-cli-logo-banner-python

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-python.

Trigger phrases include:

• "ascii-cli-logo-banner-python"
• "use ascii-cli-logo-banner-python"
• "Generate a startup banner with ascii-cli-logo-banner-python"
• "Use ascii-cli-logo-banner-python to output an ASCII logo + slogan (centered)"

Boundary

• Output copy-pastable text and layout rules only. Do not modify project code.
• Default output is width-safe and copy/paste safe (no trailing spaces).
• ANSI coloring is optional and MUST be applied to visible characters only (spaces are not colorized).
• This skill uses a built-in 5x5 font. It is not a full FIGlet engine.

How to use this skill

Inputs (recommended)

• brand (required)
• width (default 80; if < 60 use compact mode)
• 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 hero output)
• version/repo/docs/author (optional; only used when rule=true)
• colorMode (none | ansi256, default none; logo only)
• colorStart/colorEnd (0-255, defaults 33/129; only when colorMode=ansi256)

Outputs (required)

• bannerPlain: banner text (ASCII-only when colorMode=none)
• compactPlain: compact banner when width < 60
• plainTextFallback: if colorMode is enabled, also provide a no-color fallback (same layout)

Script

• scripts/generate_banner.py

Examples

• examples/banner-80.md
• examples/banner-compact.md
• examples/banner-slogan-centered.md
• examples/color-ansi256.md

Quality checklist

1. 80-column output does not wrap; no trailing spaces
2. Width < 60 uses compact mode
3. Color mode does not break alignment (spaces are not colorized)
4. Never prints secrets (tokens, internal URLs, personal data)

Keywords

English: ascii-cli-logo-banner-python, ascii, banner, logo, cli, terminal, startup, slogan, ansi256 Chinese: ascii-cli-logo-banner-python, ASCII startup banner, terminal banner, centered slogan, ANSI256 coloring

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 issue; it is recommended to use your editor's syntax checking
3. Environment variables: Ensure all necessary environment variables are set correctly, and do not hardcode sensitive information
4. Dependency conflicts: When multiple versions coexist, watch out for dependency conflicts and use a lock file to pin versions
5. Performance pitfalls: Pay attention to performance optimization in large-data scenarios and avoid common issues such as N+1 queries

Usage workflow

Step 1: Environment preparation

Ensure the development environment has the necessary dependencies and tools installed.

Step 2: Configuration initialization

Perform basic configuration according to project requirements.

Step 3: Using core features

Implement the core functionality according to the example code.

Step 4: Test verification

Run tests to ensure the functionality works properly.

Step 5: Deployment and launch

After development is complete, proceed with deployment and monitoring.