frontend-architecture

Standardize React-based Electron renderer architecture decisions for pages, state, routing, and API integration.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/mavi78/evrak-kayit-app --skill frontend-architecture-mavi78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-architecture
Source: https://github.com/mavi78/evrak-kayit-app/tree/main/.agent/skills/frontend-architecture
Command: npx skills add https://github.com/mavi78/evrak-kayit-app --skill frontend-architecture-mavi78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a standardized guide for designing and documenting the frontend architecture of the React renderer in an Electron app. It helps teams maintain consistent page creation flows, state management, API integration, routing, and authorization decisions.

Core Features & Use Cases

  • Documentation of folder structures and code organization for renderer processes.
  • Guidelines for state management, data flow, routing, and API integration.
  • Consistent decisions when adding new pages or updating architecture.

Quick Start

Review and apply the frontend architecture guidelines when starting a new page or changing the renderer structure.

Frequently Asked Questions about frontend-architecture

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

FAQPage Schema
How do I structure a React frontend architecture for an Electron renderer?

React frontend architecture for an Electron renderer requires standardized folder conventions, defined component boundaries, and consistent integration patterns for routing and API data flow to maintain code structure.

What is the best way to manage state and data flow in a React Electron app?

Managing state and data flow in a React Electron app involves defining consistent guidelines for state boundaries and API integration. This ensures standardized architecture decisions when adding new pages or updating structures.

How do I add a new page to a React Electron renderer without breaking code structure?

Adding a new page to a React Electron renderer requires following predefined folder structures and architecture guidelines. This standardizes page creation flows and enforces consistency across routing and authorization decisions.

Does this frontend architecture framework support specific routing and API integration patterns?

Yes, this frontend architecture framework enforces consistency for routing and API integration patterns. It provides structured guidelines to maintain standardized renderer processes and data flow within React.

When do I need standardized architecture guidelines for a React Electron renderer?

You need standardized architecture guidelines for a React Electron renderer when starting a new page, changing the renderer structure, or defining state management to ensure consistent code organization and architecture decisions.