shader-remove

Remove shaders and associated files from the project directory.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill shader-remove
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shader-remove
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/shader-remove
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill shader-remove

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the removal of shaders and all their related files from the project, ensuring a clean and organized codebase.

Core Features & Use Cases

  • Comprehensive Removal: Deletes shader source files (.glsl, .hlsl), metadata (.json), and associated iChannel textures.
  • Automated Regeneration: Updates shader bundles and cleans up resources after removal.
  • Use Case: When refactoring or removing unused shaders, this Skill ensures all related assets are cleaned up efficiently, preventing clutter and potential build issues.

Quick Start

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

Frequently Asked Questions about shader-remove

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

FAQPage Schema
How do I remove shaders and associated files from my project directory?

To remove shaders and associated files, this Skill deletes shader source files like .glsl and .hlsl, metadata .json files, and iChannel textures. It resolves shaders by display name, disk name, or filename, and automatically regenerates shader bundles to maintain a clean asset pipeline.

What is the best way to clean up unused shader assets and prevent build issues?

Cleaning up unused shader assets is best handled by automating the removal of shader source files, metadata, and iChannel textures. This Skill ensures all related assets are deleted efficiently and runs tests afterward to prevent potential build issues caused by lingering references.

How does deleting a shader affect iChannel textures and shader bundle generation?

Deleting a shader automatically removes its associated iChannel textures and triggers shader bundle regeneration. This ensures the project directory remains organized and free of orphaned texture files after the shader source and metadata are deleted.

Can I resolve and delete shaders by display name, disk name, or filename?

You can resolve and delete shaders by display name, disk name, or filename. This allows flexible targeting when removing specific shader source files and their associated metadata from the project directory during codebase cleanup.

Do I need to manually run tests after removing shader source files and metadata?

You do not need to manually run tests after removing shader source files and metadata. This Skill automatically runs tests and regenerates shader bundles as part of the cleanup process to verify the codebase remains stable after asset removal.