ascii-terminal-animation-pack

When to use this skill

CRITICAL TRIGGER RULE

• Use this skill ONLY when the user explicitly mentions the exact skill name: ascii-terminal-animation-pack.

Trigger phrases include:

• "ascii-terminal-animation-pack"
• "use ascii-terminal-animation-pack"
• "Using ascii-terminal-animation-pack to Create Terminal Animations"
• "Using ascii-terminal-animation-pack to Generate a Matrix Rain Demo"

Boundary

• Animations must be explicitly triggered demos. Never default to animated output in normal logs.
• Must provide an ASCII-only static poster frame for README/tickets.
• Must provide disable guidance: skip animations for non-interactive / redirected output.

How to use this skill

Inputs

• theme (matrix | waves | custom, default matrix)
• width (default 80)
• height (default 24)
• fps (default 10)
• durationSeconds (default 3)
• loop (default false)
• colorMode (none | ansi256, default ansi256)

Outputs (required)

• animationSpec (refresh rules, FPS, loop policy, disable conditions)
• staticPosterFrame (ASCII-only)
• safetyNotes (exit/disable guidance, avoid log spam)

Script

• scripts/matrix_demo.py: best-effort matrix rain demo (short-run, TTY-only)

Examples

• examples/spec.md
• examples/poster.md

Quality checklist

1. Non-spam by default: short duration, easy exit, disabled for non-interactive output
2. Static frame is ASCII-only and copy/paste safe
3. Animated output should not mix with normal application logs (recommend separate command or stream)

Keywords

English: ascii-terminal-animation-pack, terminal animation, ascii animation, matrix rain, demo, fps, non-interactive Chinese: ascii-terminal-animation-pack, terminal animation, ASCII motion effects, matrix rain, demo, frame rate, non-interactive disabled

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 the 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, pay attention to 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 problems such as N+1 queries

Usage Workflow

Step 1: Environment Preparation

Ensure 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 functionality according to the example code.

Step 4: Test Verification

Run tests to ensure the functionality works properly.

Step 5: Deployment and Release

After completing development, proceed with deployment and monitoring.