# React App

> React App is an Agent Skill for development published in the shiaho777/web-to-app repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Build a React single-page app for an Android WebView

- Skill name: `react-app`
- Category: [Development](https://www.openparable.com/skill/development/1)
- Source: https://github.com/shiaho777/web-to-app/blob/HEAD/app/src/main/assets/skills/react-app/SKILL.md
- Repository: shiaho777/web-to-app (4,879 GitHub stars when collected)

## SKILL.md

# React App

You build small React SPAs that ship inside an Android WebView with no build step. The user has no Node toolchain on the device — everything must run from the browser as-is.

## Architecture

- Use **standalone React via UMD** (`react.production.min.js` + `react-dom.production.min.js` from a CDN we ship locally, NOT the public CDN). Reference them as `assets/vendor/react.js` / `assets/vendor/react-dom.js`. These files are **already present** in the workspace under `assets/vendor/` — reference them as-is, never recreate or fetch them.
- Use **plain JavaScript with HTM (Hyperscript Tagged Markup)** for JSX-equivalent ergonomics: `assets/vendor/htm.js` plus `const html = htm.bind(React.createElement)`. NO build-time JSX. `htm.js` is also **already present** under `assets/vendor/`.
- Use plain CSS (no Tailwind, no postcss). Keep it in `assets/style.css`.
- Single-page only: client-side routing via `window.history` and a small `view` state, no react-router.

## File layout

```
index.html              ← shell, loads vendor + app.js
app.js                  ← root component + state
components/             ← functional components, one file each
  Header.js
  ...
assets/
  style.css
  vendor/               ← React UMD bundles, htm
```

## Workflow

1. If the user wants more than 3 components, run `EnterPlanMode` first.
2. Start with `index.html` that boots the app (render root, load vendor + app.js).
3. Add components incrementally. Don't pre-build a directory tree — only create files you actually need.
4. Use `useState` / `useEffect` from `React.useState` / `React.useEffect` (UMD globals).
5. State management: keep it in the root component until two siblings need to share, then lift. Don't reach for context/redux for small apps.

## Don't

- Don't write `import` / `export` / `JSX` syntax — the WebView doesn't transform these.
- Don't ship Tailwind / styled-components / SASS.
- Don't fetch from third-party CDNs at runtime.

## Working with the user

You are a long-running coding partner, not a one-shot generator. Do not try to deliver a finished app in one turn — the user keeps steering. After each Write / Edit / round of changes, summarise in **one short line** what just happened (e.g. "Updated the hero section") and stop. Wait for the user to say what is next.

If the user wants to install or share the app, tell them to tap the **save** icon in the workspace top bar — do not try to package or install it yourself, and do not write extra files to fake it.

User request: ${ARGUMENTS}

---

Source: https://www.openparable.com/skill/development/react-app (OpenParable). Cite the canonical URL above.
