When to use this skill
CRITICAL TRIGGER RULE
- Use this skill ONLY when the user explicitly mentions the exact skill name:
ascii-text-art-library.
Trigger phrases include:
- "ascii-text-art-library"
- "use ascii-text-art-library"
- "Generate an ASCII template library with ascii-text-art-library"
- "Use ascii-text-art-library to output prompt boxes/separators/title styles"
Boundary
- Output templates + naming/selection rules only; do not modify repository files.
- ASCII-only by default to avoid ambiguous-width Unicode.
- Templates must be width-tunable (default 80 columns).
How to use this skill
Inputs
- width (default 80)
- language (zh | en, default zh)
- tone (serious | fun, default serious)
- categories (title/divider/info/warn/error/success/cta, default all)
- variantsPerCategory (default 2)
Outputs (required)
- templates: grouped by category (>= 2 variants per category)
- namingRules: e.g.
TITLE_COMPACT_A,WARN_BOX_B - usageRules: selection guidance + anti-spam thresholds
Script
scripts/generate_templates.py: generate a baseline template set for a given width (local preview)
Examples
examples/templates-80.md
Quality checklist
- Stable alignment at 80 columns; no trailing spaces
- Templates are semantically clear and not over-decorated
- Notice boxes support multi-line content and remain readable
Keywords
English: ascii-text-art-library, templates, ascii, divider, banner, notice box, warning, error, success, plain text Chinese: ascii-text-art-library, template library, ASCII, separator, title, prompt box, warning, error, success, plain text
Common Gotchas
- Version compatibility: pay attention to the compatibility between the framework version and dependency libraries; APIs may differ across versions
- Configuration file format: incorrect configuration file format is the most common problem; it is recommended to use your editor's syntax checking
- Environment variables: make sure all necessary environment variables are set correctly, and do not hard-code sensitive information
- Dependency conflicts: watch out for dependency conflicts when multiple versions coexist; use a lock file to pin versions
- Performance pitfalls: pay attention to performance optimization in large-data scenarios, and avoid common problems such as N+1 queries
Usage flow
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 sample code.
Step 4: Test verification
Run tests to ensure the functionality works properly.
Step 5: Deployment and launch
Deploy and monitor after development is complete.