react-vite

Build React+Vite apps in a pnpm monorepo using a delegated design subagent workflow.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/binan-maker/QRS --skill react-vite-binan-maker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: react-vite
Source: https://github.com/binan-maker/QRS/tree/main/.local/skills/react-vite
Command: npx skills add https://github.com/binan-maker/QRS --skill react-vite-binan-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This set of guidelines standardizes and accelerates the creation of React + Vite web applications inside a pnpm monorepo by delegating frontend design work to a dedicated subagent, ensuring consistent processes and collaboration.

Core Features & Use Cases

  • Design-subagent delegation: The frontend is authored by an asynchronous design subagent, while the core app architecture and tooling stay in scope for the primary agent.
  • Monorepo-first workflow: Clear rules for using a pnpm workspace with shared references and design assets.
  • First-build governance: Mandates using the design subagent for the initial frontend build to ensure a consistent look and UI standards.

Quick Start

Trigger the design subagent to start the initial frontend build within the monorepo and follow the classification workflow to determine frontend ownership.

Frequently Asked Questions about react-vite

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

FAQPage Schema
How do I build a React and Vite frontend inside a pnpm monorepo?▼

To build a React and Vite frontend inside a pnpm monorepo, trigger the design subagent to handle the initial frontend build while the primary agent manages the core app architecture, shared workspace tooling, and references.

What is a design subagent workflow for frontend builds?▼

A design subagent workflow delegates asynchronous frontend design authoring to a dedicated subagent, keeping the core app architecture and tooling in scope for the primary agent to ensure consistent UI standards and collaboration.

Can I use this workflow for multi-package monorepos with shared references?▼

Yes, this workflow is designed for multi-package pnpm monorepos, providing clear rules for using a pnpm workspace with shared references and design assets across different packages.

Do I need to mandate the design subagent for the first build process?▼

Yes, first-build governance mandates using the design subagent for the initial frontend build to ensure a deterministic process and a consistent look across the entire React and Vite application.

What's the best way to delegate frontend design in a React Vite monorepo?▼

The best way to delegate frontend design in a React Vite monorepo is triggering the asynchronous design subagent for initial UI builds, while following the classification workflow to determine frontend ownership and maintain shared tooling.

Why does the primary agent keep core app architecture in scope during frontend builds?▼

The primary agent keeps core app architecture in scope during frontend builds to separate structural concerns, allowing the design subagent to focus strictly on UI standards while the primary agent manages workspace tooling.