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-figletjs.
Trigger phrases include:
- "ascii-cli-logo-banner-figletjs"
- "use ascii-cli-logo-banner-figletjs"
- "Generate TAAG/FIGlet large text with ascii-cli-logo-banner-figletjs"
- "Use ascii-cli-logo-banner-figletjs to call horizontalLayout / verticalLayout"
Boundary
- Output copy-pastable text and layout rules only. Do not modify project code.
- FIGlet/TAAG style is driven by FIGfont (.flf) rendering and layout “smushing/kerning” options.
- ANSI coloring is optional and MUST not break alignment (spaces are not colorized).
- Dependency note:
figletnpm package is commonly used as the Node interface and is powered byfiglet.js.
How to use this skill
Inputs (recommended)
- brand (required)
- width (default 80; if
< 60use compact mode) - font (default Standard)
- horizontalLayout (default | full | fitted | controlled smushing | universal smushing)
- verticalLayout (default | full | fitted | controlled smushing | universal smushing)
- whitespaceBreak (true|false, default true)
- slogan/hint (optional; centered lines under the logo)
- 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 (no-color)
- coloredText: when
colorMode=ansi256, provide colored logo output - plainTextFallback: when colored, also provide a no-color fallback (same layout)
Script
scripts/figlet_banner.mjs
Examples
examples/taag-figlet.mdexamples/color-ansi256.md
Quality checklist
- Layout options are honored (horizontal/vertical layout)
- 80-column output does not wrap; no trailing spaces
- Color mode does not break alignment (spaces are not colorized)
- Never prints secrets (tokens, internal URLs, personal data)
Keywords
English: ascii-cli-logo-banner-figletjs, figlet, figlet.js, FIGfont, taag, ascii, banner, smushing, kerning, ansi256 Chinese: ascii-cli-logo-banner-figletjs, FIGlet large text, TAAG, FIGfont fonts, horizontal layout, vertical layout, ANSI256 coloring
Common Gotchas
- Version compatibility: Pay attention to the compatibility between the framework version and dependency libraries; APIs may differ across versions
- Configuration file format: Configuration file format errors are the most common issue; it is recommended to use your editor's syntax checking
- Environment variables: Ensure all necessary environment variables are set correctly, and do not hardcode sensitive information
- Dependency conflicts: When multiple versions coexist, watch out for dependency conflicts and use a lock file to pin versions
- 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 sample code.
Step 4: Test verification
Run tests to ensure the functionality works properly.
Step 5: Deployment and release
After development is complete, proceed with deployment and monitoring.