shader-retire

Archives shader assets and regenerates build files via scripts.

1|Updated Jan 12, 2026

Search Tags:#archive #asset management #development tools #shader #build scripts

Ready to run

npx skills add https://github.com/cwilliams5/Alt-Tabby --skill shader-retire

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shader-retire
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/shader-retire
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill shader-retire

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps manage shader assets by moving them from the active development set to a designated legacy archive, keeping the project organized.

Core Features & Use Cases

Shader Archiving: Moves shader files (.json, .glsl, .hlsl, textures) to a legacy/shaders_retired/ directory.
Metadata-Driven: Uses the shader's JSON metadata to identify associated texture files for archiving.
Automated Regeneration: Re-runs build scripts to update shader bundles and resource files after archiving.
Use Case: When a shader is no longer actively developed but needs to be preserved, use this Skill to cleanly remove it from the active directory and place it in long-term storage.

Quick Start

Use the shader-retire skill to retire the 'Matrix Rain' shader.

Frequently Asked Questions about shader-retire

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

FAQPage Schema

How do I archive shader files to a legacy directory?▼

Archiving shader files involves relocating .json, .glsl, .hlsl, and iChannel texture files to a legacy/shaders_retired/ directory. This cleanly removes shaders from active development while preserving them in long-term storage.

What is the best way to manage the shader lifecycle for retired assets?▼

Managing the shader lifecycle for retired assets involves relocating unused shader files to a designated legacy archive. This keeps the project organized by separating active development files from preserved shaders.

How does automated regeneration work after archiving shaders?▼

Automated regeneration executes build scripts like tools/shader_bundle.ps1 and tests/test.ps1 after archiving shaders. This updates shader bundles and resource files to accurately reflect the relocated assets and validate the changes.

Does shader archiving handle associated texture files automatically?▼

Shader archiving handles texture files automatically by using the shader's JSON metadata. It identifies and relocates associated iChannel texture files alongside the main shader code to the legacy directory.

Do I need PowerShell scripts to update shader bundles post-archival?▼

You need PowerShell scripts to update shader bundles post-archival. Executing tools/shader_bundle.ps1 and tests/test.ps1 is required to regenerate build artifacts and validate the project after moving shader files.

When should I move shaders to long-term storage instead of deleting them?▼

Move shaders to long-term storage when they are no longer actively developed but need to be preserved. This maintains project organization without permanently losing the shader code and associated assets.