gmira-arsenal

Repair and standardize shadcn registry components in Next.js and React projects.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/OthmanAdi/gmira --skill gmira-arsenal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gmira-arsenal
Source: https://github.com/OthmanAdi/gmira/tree/main/skills/gmira-arsenal
Command: npx skills add https://github.com/OthmanAdi/gmira --skill gmira-arsenal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires framer-motion, lenis, lucide-react, gsap, and includes references (resource) components.

What problem does it solve?

This skill solves the issue of generic, poorly-optimized AI-generated web components by providing a rigorous workflow to repair, customize, and integrate shadcn registry components into a professional-grade design system.

Core Features & Use Cases

  • Component Repair: Automatically fixes broken import paths, missing dependencies, and unresolved package issues common in registry components.
  • Visual Taming: Audits and removes welded constants and additive shader effects that cause components to look generic or blown-out, ensuring they adhere to your specific design brief.
  • Use Case: When you add a WebGL hero component that renders as a generic rainbow blob, use this skill to audit the shader, promote hardcoded values to props, and align the output with your brand palette.

Quick Start

Use the gmira-arsenal skill to install and audit the dither-prism-hero component to ensure it respects the project design system.

Frequently Asked Questions about gmira-arsenal

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

FAQPage Schema
How do I fix broken import paths and missing dependencies in shadcn registry components?

To fix broken shadcn registry components, resolve missing dependencies and correct import paths. This skill standardizes the repair workflow by auditing unresolved package issues and standardizing integration into your Next.js project.

Why does my WebGL hero component render as a generic rainbow blob instead of my brand colors?

Your WebGL hero component renders as a generic rainbow blob due to hardcoded visual constants and additive shader effects. You must audit the shader, remove welded constants, and promote those values to dynamic props to align with your design palette.

How do I remove hardcoded visual constants from AI-generated UI components?

To remove hardcoded visual constants from AI-generated UI components, perform a visual taming audit. This process eliminates welded values and blown-out effects, ensuring the component adheres to your specific design brief instead of generic patterns.

Does this component repair workflow work with Next.js and React projects?

Yes, this component repair and visual refinement workflow specifically applies to Next.js and React projects. It handles the integration of complex WebGL, canvas, and interactive UI elements while satisfying dependency resolution requirements.

What's the best way to integrate complex WebGL and canvas elements into a shadcn design system?

The best way to integrate complex WebGL and canvas elements into a shadcn design system is to standardize their installation and visual refinement. This prevents generic AI-generated patterns by correcting import paths and eliminating hardcoded visual constants.