vendix-frontend

Create Angular 20 features with NgRx state and standalone components.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures Angular 20 + NgRx patterns and best practices to streamline frontend development, enabling teams to start projects with a solid architectural baseline.

Core Features & Use Cases

  • Feature folder structure: enforces apps/frontend/src/app/features/ layout with state/, components/, and pages/
  • NgRx feature state guidance: provides reducers, actions, selectors, and effects templates for scalable state management
  • Standalone components: demonstrates Angular 20 standalone components for modular and reusable UI pieces Use cases: when creating new features, migrating existing components to NgRx, or standardizing frontend architecture across teams

Quick Start

Start by creating a new feature folder under apps/frontend/src/app/features/, implement the state with reducers/actions/selectors/effects, and build a simple standalone component that consumes the feature state via selectors.

Frequently Asked Questions about vendix-frontend

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

FAQPage Schema
How do I structure NgRx feature state in an Angular project?

NgRx feature state in Angular is structured using a feature folder layout containing state/, components/, and pages/ directories. This standardizes reducers, actions, selectors, and effects to ensure scalable state management across projects.

What is the best way to organize Angular standalone components for scalable frontends?

Organizing Angular standalone components involves placing them within a standardized feature folder structure under apps/frontend/src/app/features/. This modular approach creates reusable UI pieces that consume feature state via selectors.

Can I use this blueprint to migrate existing components to NgRx?

Yes, you can migrate existing components to NgRx by applying the documented feature state templates. The blueprint provides reducers, actions, selectors, and effects patterns to align frontend architecture during component migration.

Do I need TypeScript to implement Angular 20 standalone components with this architecture?

TypeScript is required to implement Angular 20 standalone components and NgRx patterns. The architectural baseline relies on typed state management components like reducers and selectors to accelerate frontend development.

How does NgRx state management work with Angular 20 standalone components?

NgRx state management works with Angular 20 standalone components by having standalone components consume feature state via selectors. The state is implemented using reducers, actions, selectors, and effects within a dedicated state/ folder.

When should I standardize frontend architecture with NgRx patterns instead of local component state?

You should standardize frontend architecture with NgRx patterns when creating new features or aligning architecture across teams. This approach replaces local component state with scalable feature state to maintain a solid architectural baseline.