react-vite

Coordinate React + Vite frontend builds with a design subagent in a pnpm monorepo.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/YSheldon/Prompt-Log --skill react-vite-ysheldon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-vite
Source: https://github.com/YSheldon/Prompt-Log/tree/main/.local/skills/react-vite
Command: npx skills add https://github.com/YSheldon/Prompt-Log --skill react-vite-ysheldon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide standardizes how to build React + Vite applications inside a pnpm-based monorepo, emphasizing a design subagent as the primary workflow partner to accelerate frontend delivery.

Core Features & Use Cases

  • Establishes a clear architectural approach for React + Vite projects within a monorepo.
  • Defines when to delegate frontend design to the design subagent and how to coordinate with optional backends.
  • Provides a step-by-step process for first-build workflows, codegen references, and design handoff.

Quick Start

Start the design subagent to perform the initial frontend build within the monorepo.

Frequently Asked Questions about react-vite

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

FAQPage Schema
How do I structure a React and Vite application inside a pnpm monorepo?

To structure a React and Vite application inside a pnpm monorepo, follow standardized architectural guidelines that define the required frontend architecture, codegen references, and API surface planning.

What is a design subagent and how does it accelerate frontend delivery?

A design subagent is a delegated workflow partner that accelerates frontend delivery by handling the initial frontend build and design handoff processes within a monorepo.

How do I coordinate frontend design handoffs when building a Vite app?

You coordinate frontend design handoffs by delegating frontend design tasks to the design subagent, establishing a clear workflow for first-build processes and API surface planning.

Does this React and Vite workflow require a backend to function?

No, a backend is not strictly required; the workflow defines how to coordinate with optional backends while primarily emphasizing the design subagent as the main workflow partner.

What are the limitations of using a design subagent for frontend builds?

The approach limits flexibility by standardizing React and Vite builds strictly within a pnpm monorepo, requiring adherence to codified architectural guidance and specific design handoff processes.