worktable-create-or-manage-interactive-html
/worktable-create-or-manage-interactive-html
Tworzy i ulepsza interaktywne dokumenty HTML w Worktable, takie jak panele, trackery, kalkulatory i prezentacje.
- Autor
- worktable ↗
- Repozytorium
- worktable-plugin ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 07.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Tworzy i ulepsza interaktywne dokumenty HTML w Worktable, takie jak panele, trackery, kalkulatory i prezentacje.
Oryginalny opis (EN)
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
Jak działa
- Choose the composition
- Build the artifact
- Verify the result
Podgląd SKILL.md
--- name: worktable-create-or-manage-interactive-html description: Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc. --- # Build HTML Use an HTML doc for an interactive tool, visual explanation, or custom view. Keep it understandable when opened outside the current conversation. Use the Worktable tools the connection lists. On a Worktable that lists the earlier grouped tools, such as `worktable_discover`, use the listed tool with the matching `request.action` instead. ## Choose the composition - **Presentation or visual brief:** keep the complete high-level experience in one HTML Doc. Link a narrative Doc when deeper reasoning or source notes matter independently. - **Board, tracker, planner, directory, or dashboard:** keep independently changing entities in Records; make the HTML Doc a focused view that subscribes to and updates those Records. - **Calculator or mini tool:** keep deterministic logic in the HTML. Use `worktable.state` only for interface-local drafts, filters, selections, or preferences. Create Records only when outputs need durable identity or reuse. - **Live external data:** request network access only when the user actually needs it. Prefer Worktable runtime APIs for Worktable data. ## Build the artifact 1. Discover the workspace and related artifacts. Update the existing HTML Doc when it already owns the job. A new HTML Doc needs a `lifetime`: `durable` for interfaces people will return to, `temporary` for a one-off view that only supports current work. Check a document's lifetime with `worktable_files_read`; change it later with `worktable_files_update` and `lifetime`. 2. Before updating an existing HTML Doc, read its source with `worktable_html_read`. List open annotations with `worktable_annotations_read` filtered by its `htmlId`, inspect the context of relevant instructions, and preserve user-owned content that the request does not replace. 3. Make the purpose and primary action clear. Use the content and task to choose the layout. 4. Read `worktable_guidance` with `topic: "html"` and the `runtime` profile for the authoritative sandbox, bridge, permission, and data contract. Do not treat visual workflow guidance as a server security boundary. 5. Model and seed canonical Records first when the interface depends on them. Then write the HTML Doc with the narrowest permissions that cover its actual calls; a new one is one complete self-contained HTML document. Change an existing HTML Doc with `edits` copied exactly from your read, passing its revision as `expectedRevision`, and replace the whole page only when most of it changes. 6. Validate Mermaid sources with `worktable_mermaid` when embedding a diagram or returned SVG. Repair actionable Worktable validation warnings. 7. Inspect desktop/mobile and light/dark screenshots with `worktable_files_render` (or request a `preview` when you write the HTML). Read the image and diagnostics, then correct the source. Previews disable persistent writes and external network; `partial` identifies incomplete or blocked content. If a saved write's preview fails, retry `worktable_files_render`, not the write. Separately exercise important controls in the real interface and verify that intended Record mutations survive rereading the collection. Exercise controls that change or delete Records only on Records you created for this work, meaning `worktable_records_create` returned `created: true` (`created: false` means the ID already belonged to a Record). For the user's existing Records, ask before changing a value and restore it afterwards, and never test a delete on them, because deleted Records cannot be recovered. ## Verify the result - **Comprehension:** use descriptive headings and a clear next action. Remove controls, metrics, and decoration that do not help the task. - **Visual craft:** follow "Make the page easy to take in" in the HTML guide: lead with the point, show rather than tell, say each fact once, and cut what a reader would skip. Use Worktable's theme variables, and render the page to look at it before you hand off. - **Interaction:** give every control a purpose and legible loading, saving, success, empty, and failure states where relevant. Record-backed actions must update canonical Records, not only local HTML. - **Accessibility:** use semantic headings and native controls, visible focus, keyboard operation, comfortable targets, reduced-motion support, and a non-drag path for drag-and-drop workflows. - **Continuity:** explain the artifact without relying on the transcript, link supporting durable work, preserve user-owned content, and make the next update straightforward. Return `urlToSendInChat` as the entry point and briefly name the durable sources behind the interface. The artifact is complete when its purpose is clear, its important path works with the intended data, and the user can return through one stable link. If you could not exercise a control or render a view, say which, rather than reporting it as verified.
Pliki w paczce (3)
- LICENSE 1 KB
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
Wersje
W bazie nie ma innych skilli o nazwie worktable-create-or-manage-interactive-html.
Migawka bazy z 13.11.2026 · wersja paczki f94a19229971 (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
- 90worktable-create-or-manage-records
Porządkuje powtarzalne dane w rekordach Worktable: inwentarze, katalogi, lejki i trackery z polami, filtrami i walidacją. - 90worktable-create-or-update-docs
Tworzy i bezpiecznie aktualizuje dokumenty tekstowe w Worktable, takie jak plany, decyzje, briefy i notatki badawcze. - 100composition
Tworzy dopracowane kompozycje HTML narzędziem create_composition Jazz: wykresy, panele, interaktywne objaśnienia, kalkulatory, formularze, diagramy, planery, małe gry i prezentacje. - 90Presentations
Tworzy interaktywne prezentacje HTML w Reveal.js, na przykład pitch decki i pokazy slajdów, do otwierania w przeglądarce. - 90baoyu-design
Tworzy dopracowane artefakty HTML: makiety UI, prototypy, landing pages, dashboardy, prezentacje, animacje i raporty badawcze. - 100static-web-artifacts-builder
Buduje samodzielne statyczne strony HTML do otwarcia w przeglądarce: interaktywne diagramy, dashboardy i infografiki.