frontend-development

Designs consistent frontend patterns across React, Vue, Svelte, and Angular projects.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/dige04/hieu-ccsetup --skill frontend-development-dige04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-development
Source: https://github.com/dige04/hieu-ccsetup/tree/main/config/skills/frontend-development
Command: npx skills add https://github.com/dige04/hieu-ccsetup --skill frontend-development-dige04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend teams often struggle to maintain consistent architecture, patterns, and conventions when working across multiple frameworks; this Skill provides a unified reference to align React, Vue, Svelte, and Angular development.

Core Features & Use Cases

  • Cross-framework component patterns and patterns for state, routing, data fetching, and styling
  • Framework-specific best practices (React, Vue, Svelte, Angular) plus a framework-agnostic blueprint for governance
  • Real-world usage guidance for building scalable frontends across teams and projects

Quick Start

Create and adopt a single source of truth for frontend architecture across React, Vue, Svelte, and Angular to accelerate project delivery.

Frequently Asked Questions about frontend-development

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

FAQPage Schema
How do I maintain consistent frontend architecture across React, Vue, Svelte, and Angular?

To maintain consistent frontend architecture across React, Vue, Svelte, and Angular, adopt a framework-agnostic blueprint that provides unified cross-cutting patterns for routing, data fetching, styling, and state management to keep teams aligned.

What's the best way to standardize component patterns in a multi-framework project?

The best way to standardize component patterns in a multi-framework project is to apply a unified reference for frontend development that outlines framework-specific best practices alongside shared coding standards and governance rules.

How does cross-framework frontend governance work for scalable teams?

Cross-framework frontend governance works by establishing a single source of truth for architecture decisions, alias conventions, and a recommended file structure, ensuring scalable frontends remain consistent across diverse teams and projects.

When do I need a framework-agnostic blueprint for frontend development?

You need a framework-agnostic blueprint for frontend development when your teams work across multiple frameworks like React, Vue, Svelte, and Angular, struggling to maintain consistent conventions, file structures, and cross-cutting concerns.

Can I use a single reference for both framework selection and cross-cutting concerns like routing and styling?

Yes, you can use a single reference to guide framework selection while standardizing cross-cutting concerns like routing, data fetching, and styling, providing specific patterns for React, Vue, Svelte, and Angular simultaneously.