vis-classic-guide

Document NullPlayer vis_classic architecture, profile management, and persistence keys.

108|9|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/ad-repo/nullplayer --skill vis-classic-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vis-classic-guide
Source: https://github.com/ad-repo/nullplayer/tree/main/skills/vis-classic-guide
Command: npx skills add https://github.com/ad-repo/nullplayer --skill vis-classic-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Vis Classic Guide helps developers and operators understand NullPlayer's vis_classic rendering pipeline, profile management, persistence keys, and bundled INI profiles, enabling reliable modification and debugging.

Core Features & Use Cases

  • Comprehensive documentation of architecture, bootstrapping, and profile catalog workflow.
  • Clear references to implementation details and bundled resources for vis_classic integration.
  • Quick-start guidance to regenerate catalogs, validate changes, and troubleshoot vis_classic behavior.

Quick Start

Open the vis_classic-guide skill and run the profile catalog generator to refresh the Vis Classic profile catalog.

Frequently Asked Questions about vis-classic-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug vis_classic rendering issues in NullPlayer?

Debug vis_classic rendering by consulting architecture and bootstrapping documentation to trace profile responses across the main window and spectrum window. Bundled references and INI profiles ensure changes are traceable during troubleshooting.

What is the vis_classic profile catalog and when do I need to regenerate it?

The vis_classic profile catalog defines available skins and profiles for NullPlayer. Regenerate the catalog using the profile catalog generator when adding or modifying profiles to ensure the rendering pipeline reflects current bundled INI files.

How do I import and export vis_classic profiles for skin assignment?

Manage vis_classic profiles by referencing the bundled INI profiles and persistence keys documentation. The guide details the import/export workflow and profile catalog generation to ensure reliable skin assignment across rendering windows.

Can I use vis_classic documentation to trace changes across the main window and spectrum window?

Yes, vis_classic documentation maps architecture and persistence keys for both the main window and spectrum window. This allows developers to trace profile responses and debug rendering behavior accurately during modifications.

Why are my vis_classic profile changes not persisting in NullPlayer?

Profile persistence issues often stem from outdated catalog entries or incorrect persistence keys. Use the guide to verify persistence key configurations and run the profile catalog generator to refresh and validate bundled INI profiles.

Does the vis_classic guide require any external dependencies for bootstrapping?

No external dependencies are required. The vis_classic guide operates independently using bundled scripts, references, and INI profiles to document the bootstrapping process and profile catalog workflow for NullPlayer integration.