formext-harness
/formext-harness
Tworzy, poprawia, sprawdza i publikuje rozszerzenia do aplikacji z rodziny Form przez form.ext, w tym panele i polecenia.
- Autor
- nodemode-dev ↗
- Repozytorium
- form.ext ↗
- Licencja
- GPL-3.0
- Ostatnia zmiana repozytorium
- 11.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 9
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.
GPL-3.0, otwarta.
Co robi i kiedy
Tworzy, poprawia, sprawdza i publikuje rozszerzenia do aplikacji z rodziny Form przez form.ext, w tym panele i polecenia.
Oryginalny opis (EN)
Makes extensions for the Form apps with form.ext through its formext MCP server or the ./formext cli command line. Use whenever the person wants an extension, plugin, add-on, panel or command made, changed, fixed, checked, previewed, packaged, signed, loaded in a running app, published or submitted to form.ext-registry for formvis, formcut, formwav, formpdf, formdeck, formlit, form.md, formencoder, formvfx, formMCP, formtray or formskills; asks what an extension may do in the sandbox or which permission it needs; has a .formpkg, manifest.json or extension folder; wants an index entry or a form
Jak działa
- The model
- Start every job
- The loop
- Routing
- Rules that hold everywhere
- References
Podgląd SKILL.md
---
name: formext-harness
description: "Makes extensions for the Form apps with form.ext through its formext MCP server or the ./formext cli command line. Use whenever the person wants an extension, plugin, add-on, panel or command made, changed, fixed, checked, previewed, packaged, signed, loaded in a running app, published or submitted to form.ext-registry for formvis, formcut, formwav, formpdf, formdeck, formlit, form.md, formencoder, formvfx, formMCP, formtray or formskills; asks what an extension may do in the sandbox or which permission it needs; has a .formpkg, manifest.json or extension folder; wants an index entry or a formai.studio submission; or when formext tools such as status, new, write, validate, preview, package, sign, run_in_app, publish or submit are available or fail. Also covers pulling a host app's source to read, the family map, app skills and the registry pull request. Not for changing form.ext's own source code (use formext-skillset) and not for installing finished extensions from the catalogue (use formportal-harness)."
---
# formext harness
form.ext is the Form family's extension studio. Its engine keeps extension projects in its data folder, checks them against the Form Extension Contract (API 1), previews them in a simulated host, builds deterministic `.formpkg` packages, signs them with Ed25519 publisher keys, writes FormPortal's `dev.json` so the real app loads the project live, and prepares the formai.studio submission. The MCP server, named `formext`, exposes all of that as tools; `./formext cli` is the same surface on the command line (each tool is a command with the same name, dashes for underscores).
When the form.ext window is open, the tools talk to its engine and every change appears in the window as it happens. When it is closed, the tools run the engine's routes inside the server process against the same data folder. `status` says which.
## The model
- A **project** is a folder with `package/` (the package root: `manifest.json`, `ui/index.html`, scripts, styles, assets) and sources and notes beside it. A linked folder opened in place may have its package at its root: `files` reports `package_prefix`. Every path a tool takes is relative to the project folder, such as `package/ui/app.js`.
- An **extension** is a web page (`entry.ui`) the host app loads in a sandboxed frame (`sandbox="allow-scripts"`, opaque origin, a strict CSP with `connect-src 'none'`). Its only channel is JSON-RPC over `postMessage` through the SDK (`ui/formext.js`): `readDocument`, `apply`, `run`, `commands`, `openFiles`, `saveFile`, `fetch`, `notify`, `storageGet`, `storageSet`, `done`.
- It **contributes** dock or dialog panels and commands; a command without a panel runs headless and ends with `done`.
- It asks for **permissions**: `document` (read and change the open document), `files-read`, `files-write`, `network`, `models`. The host shows a consent dialog in those words before the frame exists.
- Each app documents its own **document snapshot, ops and events** in its extension API page: `docs {topic: "[product]"}`. Code for an app is written against that page, never from memory.
- The host app's **source code** can be brought onto this computer with `source {app: "[product]"}`. It is read-only reference. The app's API page is the summary; the source is the ground truth.
`references/concepts.md` has the contract rules that cost the most time when missed.
## Start every job
1. `status`: the engine, the data folder, which modules this engine has, and the projects.
2. `docs {topic: "contract"}` once per session, and `docs {topic: "[product]"}` for the app the extension is for.
3. `source {app: "[product]"}` to pull the app's source, then read the `docs` files it names and the `extension_host` files (`sub-skills/host-source/SUB-SKILL.md`). `family` once gives a map of all the apps.
4. `templates {product}` to see the three starters for that app (panel, command, panel-commands), each already working against the app's real API.
## The loop
1. **Make**: `new {name, product, starter}`, or `import {path, link}` for an existing folder.
2. **Write**: confirm each command id and field with `source_search {app, query}` in the pulled source, then `read` and `write` the files, `manifest {id, set}` for manifest changes (a merge patch).
3. **Check**: `validate {id}` until it reports no errors. Each problem has file, line, rule and fix.
4. **Look**: `preview {id}` says whether a host accepts it, which frame it loads with which headers, the consent words, the panels and commands, and whether every file the page references is served. The person sees it running in form.ext's Preview pane.
5. **Run in the real app** (ask first): `run_in_app {id}` adds it to FormPortal's `dev.json`; the app picks it up while it runs and reloads it on every save.
6. **Ship**: `package {id, reproduce: true}`, `keys`, `sign`, `verify`, then `publish {id}` for the formai.studio submission folder (and `formportal: true` to install it, after asking), or `submit {id}` to make it an official extension through a pull request to form.ext-registry: `submit {id, pull_request: true}` opens that pull request for the person, after asking.
## Routing
| The job involves | Load |
| --- | --- |
| A whole extension from an idea, several apps, or anything broad | `sub-skills/harness-director/SUB-SKILL.md` |
| Connecting: the MCP server, the command line, the engine, the data folder, errors that mention the engine | `sub-skills/session-and-connection/SUB-SKILL.md` |
| Writing the code and manifest: the SDK, the sandbox, panels, headless commands, document ops, events, permissions, theming | `sub-skills/writing-extensions/SUB-SKILL.md` |
| What an extension can do in one particular app, which host skill explains the app, testing live in it (`formext-hosts` skill) | `../formext-hosts/SKILL.md` |
| Reading the host app's real code: finding a command, a document field or an event; licences; keeping the source current | `sub-skills/host-source/SUB-SKILL.md` |
| Checking and previewing: validate rules, preview snapshot, what counts as verified | `sub-skills/check-and-preview/SUB-SKILL.md` |
| Run in App, packaging, keys, signing, index entries, publishing, sending to FormPortal, submitting to form.ext-registry | `sub-skills/ship/SUB-SKILL.md` |
## Rules that hold everywhere
- **The app's API page decides.** Commands, document fields and events come from `docs {topic: "[product]"}` or the starter that already uses them. An op the app does not have fails with -32004 in the real app even when the preview simulates something close. When the page and the pulled source disagree, the source wins and you report the difference to the person.
- **Verify before you claim.** Only `validate` with zero errors and a `preview` with state ready and no missing assets count as checked. Never describe how the extension looks or behaves in an app you did not run it in; say what was checked and how.
- **Ask before touching what is outside the data folder.** `run_in_app` writes FormPortal's `dev.json`; `publish` with `formportal` installs the package; `submit` with `pull_request` posts publicly under their GitHub account; `skills` with `install` writes into Claude Code's skills folder; `delete` removes files. Name what will happen first.
- **The source is read-only reference.** Never copy GPL code from a host app (formMCP, FormSkills, FormPortal) into an extension.
- **Keep the manifest honest.** `api` stays `"1"`, `native` stays false, the `id` stays the project's id, and `permissions` lists exactly what the code uses: Check flags both directions.
- **Never package anyway without saying so.** `package {anyway: true}` ships code errors; contract errors are always refused.
- **Secrets stay out of replies.** Key passphrases go into tool arguments, never into the conversation, a file or a manifest.
## References
| File | What it holds |
| --- | --- |
| `references/concepts.md` | Projects and paths, the contract rules that matter most, errors and what they mean: read once per session |
| `references/tools.md` | Every MCP tool with its arguments and the matching command (generated by `./formext cli agents-sync`) |
Pliki w paczce (9)
- SKILL.md 8 KB
- references/concepts.md 5 KB
- references/tools.md 22 KB
- sub-skills/check-and-preview/SUB-SKILL.md 3 KB
- sub-skills/harness-director/SUB-SKILL.md 5 KB
- sub-skills/host-source/SUB-SKILL.md 5 KB
- sub-skills/session-and-connection/SUB-SKILL.md 3 KB
- sub-skills/ship/SUB-SKILL.md 6 KB
- sub-skills/writing-extensions/SUB-SKILL.md 4 KB
Wersje
W bazie nie ma innych skilli o nazwie formext-harness.
Migawka bazy z 13.11.2026 · wersja paczki 18a1eb960291 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90formext-hosts
Opisuje dwanaście aplikacji-gospodarzy Form, czyli co rozszerzenie może w nich czytać i zmieniać, gdzie pojawiają się panele i jak testować je na żywo. - 90formportal-harness
Zarządza aplikacjami rodziny Form w FormPortal: wyświetla listę, instaluje, aktualizuje, cofa do poprzedniej wersji i usuwa programy przez CLI albo MCP. - 100formext-skillset
Pomaga zmieniać kod form.ext, studia rozszerzeń rodziny Form: silnik FastAPI, interfejs TypeScript, panele i publikację. - 100extension-testing
Konfiguruje i uruchamia testy rozszerzenia Chrome: testy jednostkowe Vitest, testy e2e Playwright przy wczytywaniu niepakowanego rozszerzenia i statyczną analizę web-ext lint. - 100cdp-ext-pilot
Uruchamia trwałego Chromium (domyślnie bez interfejsu) z rozpakowanym rozszerzeniem załadowanym przez web ext, otwiera panel boczny, popup lub opcje i steruje nimi przez CDP, aby testować interfejs rozszerzenia. - 100extension-architect
Projektuje i audytuje architekturę rozszerzenia Chrome w Manifest V3: cykl życia service workera, przekazywanie wiadomości, warstwy pamięci, modularność i migrację z MV2 na MV3.