Why use a text banner?
A banner works best in source code when it marks a genuinely important boundary: generated code, a subsystem, a protocol stage, or a file that developers should not edit manually.
Choose a compact style and keep the output inside the project’s normal line limit. Small and Ogre are useful when an 80- or 100-column formatter is enforced.
A safe starting pattern
/*
____ ___ ____ _____
/ ___/ _ \| _ \| ____|
| | | | | | |_) | _|
| |__| |_| | _ <| |___
\____\___/|_| \_\_____|
*/Choose the wrapper for the language
Use a block comment for JavaScript, TypeScript, Go, Rust, Java, C, or C++. Use a hash-prefixed export for Shell, Python, Ruby, or YAML. The generator escapes accidental closing sequences.
Let formatters pass over it
Some formatters reflow long comments. Place decorative headers only where the formatter preserves verbatim blocks, or exclude that small region with the formatter’s documented directive.
Generate your version
Open the full gallery, enter the final text, set the target width, then copy the output with the wrapper that matches this workflow.