Build one dependency-free HTML page + one plain-markdown agent.md, publish both to the SAME here.now site. The page serves three readers in priority order:
agent.md.Editorial voice: active, direct, zero hedging above the appendix. Roughly 9th-grade speaking level. Every claim you'd hedge belongs in the appendix, not the flow.
h1, one-line deck.section.tldr) — exactly:pre[data-copy="prompt"] containing a complete prompt the reader pastes into their own agent, e.g.
Fetch https://<slug>.here.now/agent.md and follow it to set this up in my current project. Run the success check at the end and show me the result.section.quick-start) — ONE copy-run block (pre[data-copy="commands"]), ≤ 8 lines, portable paths, runnable as-is.section.prompts) — 2–6 article.prompt-cards. Each card: a meta row (which agent · from what cwd · what you should see) + the verbatim, complete prompt in pre[data-copy="prompt"]. Never paraphrase or abridge a prompt.section.agent-guide) — numbered steps with COMPLETE inline file contents (pre[data-copy="file"] with a data-filename), portable paths, then a Success check: exact command(s) + expected observable result. This section's content must match agent.md (the page renders it; agent.md is the canonical machine copy).section.story) — the narrative/argument, condensed to ≤ 50% of the source folio's essay. Keep the strongest evidence and real anecdotes; cut repeated rhetorical moves. Plain h2/h3 titles that say what the section covers ("The two files that rewire every command"), not rhetorical verbs.section.appendix) — two <details> blocks: Limits & caveats (all hedges migrate here) and Provenance (the source ledger). Closed by default.agent.md.pre[data-copy="prompt"|"commands"|"file"] — liftable. app.js wraps every block in a header bar (filename or kind label + line count) with a labeled copy button ("Copy prompt" / "Copy commands" / "Copy file"). data-copy="file" blocks must also carry data-filename="path".--collapse-after lines (6 by default) collapse behind a "Show all N lines" button. This is by design — long file contents must not dominate the page; never inline a long file without letting it collapse.pre[data-output] — captured output/transcripts. Header reads "output — not runnable", NO copy button, never collapsed.pre[data-example] — illustrative only. Header reads "example — don't paste", NO copy button, never collapsed.pre MUST carry exactly one of these three attributes. A bare pre is a defect.data-example.Plain markdown, published at the site root alongside index.html. Structure:
$HOME, <project-root> placeholders only where unavoidable, declared up top).No HTML, no styling, no scholarly apparatus. An agent must be able to execute it top-to-bottom cold.
templates/index.html, templates/styles.css, templates/app.js from this skill as the starting point; fill the slots. Keep app.js byte-identical to the template. templates/agent.md is the agent.md skeleton.pre[data-output].icn.prefers-color-scheme, with <html data-mode="light|dark"> as a manual override hook. The two dark blocks in styles.css (media query + data-mode) must stay byte-identical. Typography uses variable system fonts only (system-ui / ui-serif / ui-monospace with weight axes + font-optical-sizing) — never add webfonts. Verify pages in BOTH modes.max-width: 100%.When a project already has .herenow/state.json, publish as an UPDATE to that site so the slug/URL is preserved. Add agent.md to the same publish. Never create a second site for the same topic. Keep the site display name unchanged.
pre carries exactly one of data-copy / data-output / data-example (grep count check).data-copy="file" blocks all have data-filename.<details> open/close; copy buttons appear only on liftable blocks and copy exact text.index.html AND agent.md both return HTTP 200 at the same slug; local and live bytes match; zero cross-origin requests.Published URL, agent.md URL, the named money artifact, what was cut from the story (roughly), and the verification results.
---
name: here-now-workshop-page
description: >-
Build and publish a workshop-grade, action-first web page (plus a
machine-readable agent.md companion) from an existing Scholarly Folio,
project demo, notes, or topic brief. Use when the audience is workshop
attendees and their AI agents: people who skim on a phone, copy/paste
prompts and commands, and hand the URL to their own agent to replicate the
setup. Supersedes the here-now-scholarly-folio presentation for hands-on
material; keeps the folio's honesty (caveats, provenance) but moves it into
a collapsed appendix. Publishes with the existing here-now skill.
---
# here-now Workshop Page
Build one dependency-free HTML page + one plain-markdown `agent.md`, publish both to the SAME here.now site. The page serves three readers in priority order:
1. **Attendee during the talk** (phone, 30 seconds) → TL;DR card.
2. **Developer afterward** (desk, tonight) → Quick start + Prompt library.
3. **Their AI agent** (fetches a URL) → Agent setup guide + `agent.md`.
Editorial voice: active, direct, zero hedging above the appendix. Roughly 9th-grade speaking level. Every claim you'd hedge belongs in the appendix, not the flow.
## Required page anatomy (in this order)
1. **Header** — kicker (workshop name · date), `h1`, one-line deck.
2. **TL;DR card** (`section.tldr`) — exactly:
- 3 bullets max: what this is / what you walk away with / the one move.
- The **agent bootstrap chip**: a `pre[data-copy="prompt"]` containing a complete prompt the reader pastes into their own agent, e.g.
`Fetch https://<slug>.here.now/agent.md and follow it to set this up in my current project. Run the success check at the end and show me the result.`
- No hedging. No caveats. Limits live in the appendix.
3. **Quick start** (`section.quick-start`) — ONE copy-run block (`pre[data-copy="commands"]`), ≤ 8 lines, portable paths, runnable as-is.
4. **Prompt library** (`section.prompts`) — 2–6 `article.prompt-card`s. Each card: a meta row (which agent · from what cwd · what you should see) + the **verbatim, complete** prompt in `pre[data-copy="prompt"]`. Never paraphrase or abridge a prompt.
5. **Agent setup guide** (`section.agent-guide`) — numbered steps with COMPLETE inline file contents (`pre[data-copy="file"]` with a `data-filename`), portable paths, then a **Success check**: exact command(s) + expected observable result. This section's content must match `agent.md` (the page renders it; agent.md is the canonical machine copy).
6. **The story** (`section.story`) — the narrative/argument, condensed to ≤ 50% of the source folio's essay. Keep the strongest evidence and real anecdotes; cut repeated rhetorical moves. Plain `h2`/`h3` titles that say what the section covers ("The two files that rewire every command"), not rhetorical verbs.
7. **Appendix** (`section.appendix`) — two `<details>` blocks: **Limits & caveats** (all hedges migrate here) and **Provenance** (the source ledger). Closed by default.
8. **Footer** — link back to the workshop hub (if one exists) and to `agent.md`.
## Code-block semantics (strict)
- `pre[data-copy="prompt"|"commands"|"file"]` — liftable. app.js wraps every block in a header bar (filename or kind label + line count) with a labeled copy button ("Copy prompt" / "Copy commands" / "Copy file"). `data-copy="file"` blocks must also carry `data-filename="path"`.
- Liftable blocks longer than `--collapse-after` lines (6 by default) collapse behind a "Show all N lines" button. This is by design — long file contents must not dominate the page; never inline a long file without letting it collapse.
- `pre[data-output]` — captured output/transcripts. Header reads "output — not runnable", NO copy button, never collapsed.
- `pre[data-example]` — illustrative only. Header reads "example — don't paste", NO copy button, never collapsed.
- Every `pre` MUST carry exactly one of these three attributes. A bare `pre` is a defect.
- **The money-artifact rule:** the single most valuable artifact of the topic (the actual prompt, the actual config file, the actual script) must appear verbatim and complete in a liftable block. "Abridged", "condensed", and "constructed illustration" are banned for liftable blocks; if an illustration is genuinely needed, mark it `data-example`.
## agent.md contract
Plain markdown, published at the site root alongside `index.html`. Structure:
1. Title + one line: what following this file sets up.
2. **Prerequisites** — tools/versions, checked with commands.
3. **Steps** — numbered; every file created is given in full in a fenced block with its exact path; every command is exact and portable (`$HOME`, `<project-root>` placeholders only where unavoidable, declared up top).
4. **Success check** — command(s) the agent must run plus the expected observable output, and an instruction to report the result to its user.
5. **Notes for agents** — known failure modes and how to recover (from the project's real experience).
No HTML, no styling, no scholarly apparatus. An agent must be able to execute it top-to-bottom cold.
## Building
- Copy `templates/index.html`, `templates/styles.css`, `templates/app.js` from this skill as the starting point; fill the slots. Keep `app.js` byte-identical to the template. `templates/agent.md` is the agent.md skeleton.
- No external requests of any kind (fonts, scripts, images from other hosts). Inline or local-file everything. Mermaid/ASCII diagrams as `pre[data-output]`.
- Icons: app.js injects inline Lucide SVGs (section headings by section class, code-block kind icons, copy/expand glyphs, success-check). Never add icon fonts or CDN icon scripts; to use an icon in page content, inline the Lucide SVG markup directly with class `icn`.
- The canonical theme ("Instrument Panel", chosen by head-to-head voting in both modes) is theme-aware: colors are an oklch token system (hue/chroma tokens; dark mode only flips the lightness ramp) driven by `prefers-color-scheme`, with `<html data-mode="light|dark">` as a manual override hook. The two dark blocks in styles.css (media query + data-mode) must stay byte-identical. Typography uses variable system fonts only (system-ui / ui-serif / ui-monospace with weight axes + `font-optical-sizing`) — never add webfonts. Verify pages in BOTH modes.
- Images: only local files shipped with the site; `max-width: 100%`.
## Updating an existing site (keep the URL)
When a project already has `.herenow/state.json`, publish as an UPDATE to that site so the slug/URL is preserved. Add `agent.md` to the same publish. Never create a second site for the same topic. Keep the site display name unchanged.
## Verification (all required before publishing; repeat the live checks after)
1. Every `pre` carries exactly one of `data-copy` / `data-output` / `data-example` (grep count check).
2. `data-copy="file"` blocks all have `data-filename`.
3. The money artifact is present, complete, and liftable (human judgment — name it in your report).
4. Quick start block runs (or dry-runs) from a clean shell.
5. agent.md steps reference no files that aren't fully printed inside it.
6. Browser check at ~1440px and 320px: no horizontal page scroll; code blocks scroll internally; long liftable blocks are collapsed with a working "Show all N lines" toggle; `<details>` open/close; copy buttons appear only on liftable blocks and copy exact text.
7. After publish: `index.html` AND `agent.md` both return HTTP 200 at the same slug; local and live bytes match; zero cross-origin requests.
## Report format
Published URL, agent.md URL, the named money artifact, what was cut from the story (roughly), and the verification results.