Steal this.
Make it yours.
One HTML file, one URL, one idea. Ship self-contained artifacts to any subdomain in seconds.
Ideas move faster than slide decks.
So we don't make slide decks.
Google Slides is a filing cabinet. Figma is a design tool. Notion is a wiki. None of them let you ship an artifact: a self-contained, linkable, brandable thing you throw on the internet in one click.
This template is the atomic unit. One HTML file, one URL, one idea. Generate it in seconds, replace it in seconds, forget about it forever.
Four rules.
-
◆
Single file, always
No bundler, no framework, no runtime dependencies beyond a CDN. If it breaks in five years, one file to fix.
-
◆
Content is the design
Type does most of the work. Terracotta accent. Rubik for structure, mono for detail. Nothing else.
-
◆
Scroll and snap
Feels like a deck on desktop with keyboard nav. Feels like a landing page on mobile. Same file, no branch.
-
◆
Deployable in one push
Drop into Cloudflare Pages. Wildcard routes
*.ogarocious.comto the right artifact.
The pipeline.
Slack to live URL in about sixty seconds. Four real steps, not four decorative cards.
/artifact
Slash command in Slack. Describe the piece in one sentence.
n8n calls Claude
Workflow feeds template plus brief to Claude. Filled HTML comes back.
git push
Commit to artifacts-hub. Cloudflare Pages picks it up.
Yemoja DMs URL
Live at slides.ogarocious.com/<slug>.
What Claude fills in.
The section shape:
<section id="slug" data-title="Nav label"> <h2>## big display headline</h2> <div>## body: prose, list, grid, code, quote</div> </section>
Nav rebuilds itself from data-title. Add or remove sections; JS untouched.
"The best interface is a URL you can send someone."
an artifact, probably
Steal these bits.
- →Wildcard subdomain plus Cloudflare Pages beats per-project deploys.
- →IntersectionObserver with
scroll-snapcovers most of the decky feel. - →One template, many artifacts. The template is the product.
- →Keyboard nav belongs on marketing pages, not just docs.
Take these two.
Copy both. Paste into Claude. Answer the questions it asks. Get your artifact back.
Interview me relentlessly about every aspect of this until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering. For each question, also solicit any pretext, subtext, or context I should surface; the reasons behind my answer often matter as much as the answer. When a question has discrete options, letter them alphabetically (A, B, C, ...). For each option, explain what it means and its trade-off. State which option you recommend and why. If a *fact* can be found by exploring the environment (filesystem, tools, etc.), look it up rather than asking me. The *decisions*, though, are mine; put each one to me and wait for my answer. Ask for permission before generating any solutions, artifacts, or code. Grilling produces shared understanding; solutions come only after I explicitly authorize them. Do not act on it until I confirm we have reached a shared understanding.
/plugin marketplace add ogarocious/grilling /plugin install grilling@grilling /reload-plugins
Fetch the template at https://raw.githubusercontent.com/ogarocious/artifacts-hub/main/template/template.html and fill every {{PLACEHOLDER}} slot based on what you learned from grilling. Output the completed HTML file. Save it as slides/<slug>/index.html in your fork of the artifacts-hub repo.
Take it.
Ship yours.
Ogarocious · Liberation Through Creation