gea-framework

Compiles JSX to efficient DOM patches for Gea applications with proxy-based stores and router support.

1.2k|46|Updated Mar 18, 2026

Search Tags:#store #router #jsx #ssr #reactive-ui #gea-framework

Ready to run

npx skills add https://github.com/dashersw/gea --skill gea-framework

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gea-framework
Source: https://github.com/dashersw/gea/tree/main/.cursor/skills/gea-framework
Command: npx skills add https://github.com/dashersw/gea --skill gea-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Gea Framework provides a complete, lean toolkit for building reactive JavaScript UIs without a virtual DOM, combining a compile-time JSX transformer, proxy-based stores, and a built-in router to ship tiny runtimes and surgical DOM updates.

Core Features & Use Cases

Reactive stores and components written in familiar class/function styles
Compile-time JSX transforms via Vite plugin, with event delegation and delta patches
Built-in Router, SSR support, and optional mobile primitives for fast, scalable apps
Use cases include single-page apps, SSR pages, and multi-store workflows across domains

Quick Start

Create a new Gea project, install dependencies, and start the development server to begin building reactive components.

Frequently Asked Questions about gea-framework

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

FAQPage Schema

How do I build reactive UIs without a virtual DOM?▼

You can build reactive UIs without a virtual DOM by using a compile-time JSX transformer that generates efficient DOM patches, combined with proxy-based stores for surgical DOM updates. This approach ships a tiny runtime and avoids diffing overhead.

What is the best way to manage state in a lean JavaScript SPA?▼

Managing state in a lean JavaScript SPA is handled through proxy-based stores that trigger surgical DOM updates directly. This reactive store model eliminates the need for a heavy virtual DOM diffing layer, keeping the runtime footprint minimal.

Does Gea support server-side rendering for reactive components?▼

Yes, Gea supports server-side rendering (SSR) alongside its built-in router for fast, scalable applications. SSR workflows integrate directly with the proxy-based stores and compile-time JSX transforms to enable complete front-end rendering.

Can I use JSX with Vite for compile-time DOM patching?▼

Yes, you can use JSX with Vite for compile-time DOM patching. The framework utilizes a Vite plugin to transform JSX at compile time, applying event delegation and delta patches to achieve efficient, surgical updates without a virtual DOM.

How do I set up routing for a single-page app without external dependencies?▼

Routing for a single-page app without external dependencies is handled by the built-in router. It integrates natively with the reactive stores and compile-time JSX components to provide complete navigation workflows out of the box.

When should I avoid using a virtual DOM for front-end development?▼

You should avoid a virtual DOM when you need lean, highly reactive applications with tiny runtimes and surgical DOM updates. If your project prioritizes minimal overhead over the flexibility of a heavy diffing layer, a compile-time JSX approach is more suitable.