prowler-ui

Enforce Prowler UI component structure and styling with shadcn/ui and Tailwind.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/adbertram/Devolutions-CIEM --skill prowler-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prowler-ui
Source: https://github.com/adbertram/Devolutions-CIEM/tree/main/prowler/skills/prowler-ui
Command: npx skills add https://github.com/adbertram/Devolutions-CIEM --skill prowler-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prowler UI development suffers from inconsistent patterns across components, legacy HeroUI usage, and fragmented conventions. This Skill consolidates Prowler-specific UI patterns to guide consistent folder placement, actions/adapters, and shared types/hooks/lib usage.

Core Features & Use Cases

  • UI pattern guidance: Aligns on shadcn/ui usage with Tailwind for new and migrated Prowler UI components.
  • Legacy compatibility: Provides rules for integrating with legacy HeroUI components without breaking consistency.
  • Usage guidance: Helps teams structure ui/ with proper folders, actions, adapters, and shared types.

Quick Start

Use the prowler-ui skill when creating or updating Prowler UI components to ensure alignment with shadcn/ui, Tailwind, and existing conventions.

Frequently Asked Questions about prowler-ui

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

FAQPage Schema
How do I structure Prowler UI components to align with shadcn/ui and Tailwind?

To align Prowler UI components with shadcn/ui and Tailwind, apply codified patterns for consistent folder placement, actions, adapters, and shared types within the ui/ directory to enforce frontend tech-stack alignment.

What is the best way to migrate legacy HeroUI components without breaking consistency?

Migrating legacy HeroUI components requires applying specific integration rules that enforce consistent component structure and styling, ensuring new shadcn/ui patterns coexist with existing legacy code without breaking frontend conventions.

How do I organize actions and adapters within the ui/ folder for Prowler frontend development?

Organizing actions and adapters within the ui/ folder involves following clear component placement rules that separate shared types, hooks, and lib utilities, ensuring consistent Prowler UI frontend patterns across the directory structure.

Does this Prowler UI skill enforce strict tech-stack alignment for new component creation?

Yes, Prowler UI development enforces strict frontend tech-stack alignment by codifying shadcn/ui integration, Tailwind styling, and clear folder placement rules to guide consistent component structure when building or updating UI components.

When should I apply these UI patterns during Prowler frontend development?

Apply these UI patterns when creating new or updating existing Prowler UI components within the ui/ folder, ensuring immediate alignment with shadcn/ui, Tailwind, shared hooks, and legacy HeroUI integration conventions.