# HTML App

> HTML 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 single-page HTML/CSS/JS app for an Android WebView

- Skill name: `html-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/html-app/SKILL.md
- Repository: shiaho777/web-to-app (4,879 GitHub stars when collected)

## SKILL.md

# HTML App

You're building a single-file HTML page that ships inside an Android WebView. The user runs the result on a phone, so the page must work well at narrow widths (320–428 px), respect tap targets, and survive on slow 4G.

## Constraints

- Entry file is always `index.html`.
- Include the viewport meta on every page: `<meta name="viewport" content="width=device-width, initial-scale=1.0">`.
- Use relative units (`vw`, `vh`, `%`, `rem`, `clamp()`); minimum 44×44 px tap targets.
- Default to a single file: CSS in `<style>`, JS in `<script>`. Split into `style.css` / `app.js` only when the file passes ~400 lines.
- No build step. No npm install. The user runs the file as-is.
- Inline images are fine; for richer art, call `GenerateImage` and reference `assets/<filename>` in `<img>`.

## Workflow

1. If the project is empty, draft a brief plan: what sections, what palette, what interactions. For anything beyond a few sections, call `EnterPlanMode` first.
2. `Write index.html` with the full page. Don't fragment work across multiple write calls if a single write is small enough to be readable.
3. When the user wants illustrations or icons, call `GenerateImage` — you'll see the result in the next turn and can iterate.
4. If the user has previous code in the project, `Read` it before editing. `Edit` for surgical changes; `Write` only for full rewrites.
5. After each iteration, summarise in one short line what changed and stop. Don't paste the HTML back at them — they can see it in the preview.

## Review heuristics before finishing

- Are tap targets ≥ 44 px?
- Does the page render without a network connection? (No external CDNs unless the user explicitly asked.)
- Are images alt-tagged?
- Are colour contrasts AA-compliant for body text?

## 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/html-app (OpenParable). Cite the canonical URL above.
