← ClaudeAtlas

epic-pagelisted

The one HTML frame both EPIC pages render into — the design page /fleet-epic-plan hosts before the operator confirms a batch, and the batch report /fleet-epic-report hosts after it ends — so the operator reads the pair as one document. Use when either command builds its page: copy template.html, keep the <style> and the section ids, fill the ⟨slots⟩, share via doc-preview.
verkyyi/claude-fleet · ★ 2 · Web & Frontend · score 68
Install: claude install-skill verkyyi/claude-fleet
# epic-page — the shared frame for the EPIC trio's pages <!-- fleet skill --> Two of the three EPIC commands render a page for the operator: `/fleet-epic-plan` puts a **design page** in front of them before anything is filed (issue #809), and `/fleet-epic-report` renders the **batch report** after the run ends. Both are model-authored HTML, and without a shared source they came out looking like two different products — the first two reports on this machine did. This skill is the shared source: one `template.html`, one `<style>`, one set of section ids. ## Use ```sh cat ~/.claude/skills/epic-page/template.html # read the frame, then write your page ~/.claude/skills/doc-preview/share.sh <page.html> # host it; relay the READY URL ~/.claude/skills/doc-preview/share.sh --refresh # after editing the SAME file — URL unchanged ``` - **Keep** the `<style>` block verbatim and every `id=` on `<section>` / member cards. The ids are the contract the commands (and their selftest) refer to; the style is what makes the two pages one document. - **Fill** every `⟨slot⟩`. Labels inside the slots follow the theme's language (the fixed Chinese labels are this fleet's default — translate them if the theme is in another language; keep the ids). - **Drop** the sections the other page owns — each is marked PLAN ONLY / REPORT ONLY / BOTH in the file. Never add UX chrome — doc-preview's viewer is reading/print-first by design. - **Re-render, don't re-share.** `share.sh <file>` AP