A Datastar Go web frontend framework
This repository also configures its own agents. See what datapages tells them →
Skill Claude CodeCodex
Write Datapages action handlers (GET, POST, PUT, PATCH, DELETE, QUERY): file responses, parameters, return values, Datastar signals, SSE patching, HTTP error status codes and the RecoverError hook.
Skill Claude CodeCodex
Datapages real-time events: event types and subjects, dispatchers, On handlers, per-user and signal-bound subject fields, and the StreamOpen and StreamClose hooks. Activate when adding events, subscriptions or stream hooks to a Datapages app.
Skill Claude CodeCodex
Add or change a Datapages page: route doc comments, GET return values, path and query parameters, custom error pages, the global head and sharing handlers across pages by embedding.
Skill Claude CodeCodex
Configure the Datapages server entry point: NewServer type arguments, the message broker, server options, static assets, TLS and Prometheus metrics.
Skill Claude CodeCodex
Add Datapages authentication: define and read the Session type, open and close sessions, configure CSRF protection and choose a session manager. Use when adding sign-in, sign-out or authenticated handlers to a Datapages app.
Skill Claude CodeCodex
Add per-tab Datapages State[T], initialize and use it in handlers, dispatch state-scoped events, and configure the live instance limit. Activate when a Datapages page needs server-side values that belong to 1 browser tab.
Skill Claude CodeCodex
Write Templ templates for a Datapages app: the generated href and action helpers, their options, attribute syntax, Web Components and Templ pitfalls. Read with the datastar skill.
Skill Claude CodeCodex
Plan a Datapages app or feature: choose where to store values, how to update the browser, where to define handlers, how to scope event subjects and how many server processes to run. Use before other Datapages skills when these choices are not set.
Skill Claude CodeCodex
The Datapages service worker: offline page snapshots and cached shims written by handlers through the pageCache parameter, the offline module and its Config, and the PageOffline fallback.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: