# Module JS

> Module JS 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 plain JavaScript extension module for the WebToApp Module Market

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

## SKILL.md

# JS Extension Module

You produce a community module for the WebToApp Module Market. The runtime wraps your `main.js` in an IIFE before injection.

## Required files

```
module.json             ← manifest (id, name, version, runAt, urlMatches, permissions, configItems)
main.js                 ← code that runs inside the page
style.css               ← optional, auto-injected when hasCss=true in registry
```

## `module.json` schema (minimal)

```json
{
  "id": "kebab-globally-unique-id",
  "name": "Display Name",
  "description": "One paragraph",
  "icon": "auto_awesome",
  "category": "FUNCTION_ENHANCE",
  "tags": ["dark-mode", "reading"],
  "version": { "code": 1, "name": "1.0.0", "changelog": "Initial release" },
  "author": { "name": "<user>", "url": "https://github.com/<user>" },
  "runAt": "DOCUMENT_END",
  "urlMatches": [ { "pattern": "*", "isRegex": false, "exclude": false } ],
  "permissions": ["DOM_ACCESS", "CSS_INJECT"],
  "configItems": []
}
```

## `main.js` contract

- Wrapped in an IIFE — don't write `return` at top level.
- Globals available: `__MODULE_INFO__`, `__MODULE_CONFIG__`, `__MODULE_UI_CONFIG__`, `__MODULE_RUN_MODE__`, `__MODULE_PANEL_HTML__`, `getConfig(key, defaultValue)`.
- Errors are caught and logged with the module name as prefix.

## Panel UI (interactive modules)

If your module shows a panel UI when the user taps its FAB button:

1. **Define CSS** in `style.css` using `wta-` prefixed class names. Use `var(--wta-*)` CSS variables for colors (e.g. `var(--wta-on-surface, #1f2937)`) to support both light and dark themes.
2. **Set `panelHtml`** in `module.json` to a static HTML string with CSS classes and `data-wta-action` attributes. **No inline `style=""` attributes.**
3. **Register module actions** via `window.__wta_module_action_<name> = function(arg) { ... };` in `main.js`.
4. The runtime wires `data-wta-action="<name>"` clicks to your action functions automatically via event delegation.

### `module.json` additions for interactive modules

```json
{
  "panelHtml": "<div class=\"wta-mod-panel\"><button class=\"wta-mod-btn\" data-wta-action=\"doThing\">Do it</button></div>",
  "cssCode": ".wta-mod-panel { padding: 16px; } .wta-mod-btn { ... }"
}
```

### Don't

- Don't use inline `style="..."` in `panelHtml` — use CSS classes in `cssCode` instead.
- Don't use `onclick="..."` or other inline event handlers (CSP may block them). Use `data-wta-action` attributes.
- Don't use `onAction` unless your UI depends on runtime page analysis (e.g. detecting videos on the current page). For static UIs, `panelHtml` + `cssCode` is sufficient.

## Workflow

1. Pick a kebab-case `id` distinct from any existing module (use `Glob` to check).
2. Write `module.json` first with sane defaults.
3. Write `main.js` and keep it small — most modules are 30-150 lines.
4. Choose `urlMatches` carefully. `*` (= every URL) is invasive — use site-specific patterns when possible.
5. Declare only the permissions you actually use. Reviewers reject permission-bloat.
6. If the module ships CSS, add `style.css` AND set `hasCss: true` in the registry entry.

## Don't

- Don't fetch from third-party endpoints unconditionally.
- Don't read `document.cookie` or auth tokens unless declared in `permissions` and absolutely needed.
- Don't generate userscript headers (`==UserScript==`); for that, use `module-userscript` instead.
- Don't reference `chrome.*` APIs; for that, use `module-chrome-mv3`.

## Working with the user

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

If the user wants to install or share the module, tell them to tap the **save** icon in the workspace top bar — the host parses your `module.json` / `manifest.json` / `.user.js` and adds the result to the *Extension Modules* list. Do not try to install it yourself, and do not write extra files to fake it.

User request: ${ARGUMENTS}

---

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