vendix-frontend-standard-module

Standardize admin list UI modules with mobile-first layouts and Angular Signals.

5|Updated Aug 23, 2025
One-click install
npx skills add https://github.com/Rzyfront/Vendix --skill vendix-frontend-standard-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vendix-frontend-standard-module
Source: https://github.com/Rzyfront/Vendix/tree/main/skills/vendix-frontend-standard-module
Command: npx skills add https://github.com/Rzyfront/Vendix --skill vendix-frontend-standard-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes reusable admin UI modules to accelerate frontend development and ensure consistent UX across admin areas.

Core Features & Use Cases

  • Provides a mobile-first, sticky-header layout with 4 stats cards, a search/filter header, and a data table for admin lists.
  • Enables rapid creation or refactoring of modules in STORE_ADMIN or ORG_ADMIN contexts by reusing a proven pattern.
  • Supports responsive data views and a consistent UI surface for dashboards and list views.

Quick Start

Create a new admin list module following the standard layout pattern: include a 4-card stats header, a search/header area, and a responsive data view. Adapt the module to your entity (e.g., Products, Users) and wire it into your data services and routes for STORE_ADMIN or ORG_ADMIN.

Frequently Asked Questions about vendix-frontend-standard-module

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

FAQPage Schema
How do I build a standard admin dashboard layout in Angular?

To build a standard admin dashboard layout in Angular, use a mobile-first, sticky-header structure with a 4-card stats header, a search and filter area, and a responsive data table. This pattern accelerates frontend development for admin lists.

Can I use Angular Signals for admin list views?

Yes, you can use Angular Signals for admin list views. The standard admin UI module pattern enforces Angular Signals-based logic for new features to manage state and data reactively across responsive data views.

What is the standard pattern for refactoring STORE_ADMIN or ORG_ADMIN list modules?

The standard pattern for refactoring STORE_ADMIN or ORG_ADMIN list modules involves applying a mobile-first layout with 4 stats cards, a search and filter header, and a responsive data table. This ensures consistent UX across admin areas.

How do I create a responsive data table for an Angular admin module?

To create a responsive data table for an Angular admin module, apply the standardized UI pattern which includes a mobile-first layout, sticky headers, and a search filter area. Adapt the module to your specific entity and wire it into data services.

Does this admin UI module pattern work for both STORE_ADMIN and ORG_ADMIN contexts?

Yes, this admin UI module pattern works for both STORE_ADMIN and ORG_ADMIN contexts. It is specifically applied when creating or refactoring admin list views to provide a consistent UI surface across different admin areas.