landing-page
Skill32 starsChanged 8 days agoMITView on GitHub
Maintain the aidemo marketing/landing page (docs/index.html, served by GitHub Pages at https://tandryukha.github.io/aidemo/) and its indexing plumbing (llms.txt, robots.txt, sitemap.xml). Use when the user says "update the landing page", "add a section to the site", "change the hero", "update positioning", "fix the site", or asks to reflect a new feature/integration on the page. Do NOT use for: the GitHub README (separate, hand-curated), the docs/internal/ planning docs, or recording demo videos (that's record-demo).
49 other projects use a version of this.
Adopted by
Most recently taken up by
- leejianrong/claude-skillstheir own version, first seen Nov 16, 2026
- yotamwiesel/claude-skillstheir own version, first seen Nov 16, 2026
- vaferkhanom/Website-skillstheir own version, first seen Nov 16, 2026
- teodstr/garagetheir own version, first seen Nov 15, 2026
- igoroliveirg/claude-copytheir own version, first seen Nov 15, 2026
- ImBIOS/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use product-proof-saas, framed-grid-layout and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
boraoztuncSkillproduct-proof-saas
Create or redesign SaaS and AI product landing pages where a real workflow, interface, or deterministic demo is the central proof. Use for pale atmospheric shells, product UI in the hero, prompt-to-output stories, audience tabs, compact feature modules, honest pricing comparisons, and FAQ handoffs.
Also in 4 projects that use this
boraoztuncSkillframed-grid-layout
Create minimal framed grid layouts with thin visible boundary lines, L-shaped corner brackets, subtle diagonal line texture, and strict section alignment. Use when asked for clean, neutral, precise, structured, editorial, technical, or guide-border web layouts.
Also in 3 projects that use this
shawnpangSkillmvp-scoping
When the user needs to decide what to build, cut, and defer for a first release or minimum viable version of a product or feature.
Also in 3 projects that use this
Dragoon0xSkillonboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
Also in 3 projects that use this
shawnpangSkilllead-scoring
When a founder needs to qualify inbound leads, define their ICP, build a lead scoring model, set MQL criteria, or route prospects through pipeline stages. Activate when the user mentions lead scoring, ICP, MQL, SQL, lead qualification, inbound leads, or pipeline design.
Also in 3 projects that use this
AnthropicSkillpitch-deck
Populates investment banking pitch deck templates with data from source files. Use when: user provides a PowerPoint template to fill in, user has source data (Excel/CSV) to populate into slides, user mentions populating or filling a pitch deck template, or user needs to transfer data into existing slide layouts. Not for creating presentations from scratch.
Also in 5 projects that use this
- +5 more from boraoztunc
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- emotixco/claude-skills-founder★ 796same name
- boraoztunc/skills★ 473same name
- shawnpang/startup-founder-skills★ 331same name
- whawkinsiv/solo-founder-skills★ 260same name
- whawkinsiv/claude-code-skills★ 258same name
- realjaymes/marketingagentskills★ 68same name
- duncan-buildroom/freeskills★ 65same name
- KeWang0622/agent-zero-to-hero★ 55same name
- ariaxhan/kernel-claude★ 15same name
- calven-ai/marketing-as-code★ 10same name
39 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- aidemo-blogSkill
- blog-waveSkill
- record-demoSkill
- releaseSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Commit straight to main and push (no PRs in this repo).
- Very specific: line 50
Run that check with Bash run_in_background: true, never a bare foreground sleep.
- Distinctive: line 54
Only claim what ships: No named future integrations or roadmap promises on the page.
- Very specific: line 68
When showing an assistant/integration, show the actual command a developer would type (if a genuinely unshipped integration ever needs …
- Very specific: line 78
Self-contained page: No CDN scripts, external fonts, or third-party requests.
- Very specific: line 81
FAQ and JSON-LD move together: Every visible FAQ <details> has a matching entry in the FAQPage JSON-LD block, same wording.
- Very specific: line 144
Update the aspect-ratio / width/height attrs if dimensions changed.
- Distinctive: line 145
Keep the "watch the narrated version" link pointing at the release asset URL (the page's video is muted).
- Very specific: line 150
Follow the swap checklist in docs/internal/INDEXING_PLAN.md §4: Pages custom-domain setting, find-replace the tandryukha.github.io/aidemo …
“Common” is measured: kept by at least 6 in 10 of the 44 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
landing-page
You maintain aidemo's public landing page. It is the project's pitch to humans AND its primary machine-readable source for LLM search (GEO). Every edit must serve both audiences.
Where things live
docs/index.html— the entire site: one self-contained file (inline CSS/JS).docs/llms.txt— curated map for LLM crawlers; MUST stay in sync with any positioning/feature claims changed on the page.docs/robots.txt— AI-crawler allowlist.docs/sitemap.xml— single URL.docs/hero-demo.mp4(1280×800 h264, copy of the release asset) +docs/hero-poster.jpg(poster frame, also the og:image).docs/icons/*.webp— card icons (176px, shown at 44px) + real customer logo marks;docs/favicon.png(64px, from the clapper icon). See "Icon system" below before adding one.docs/.nojekyll— keep; Pages servesdocs/verbatim frommain.docs/internal/is gitignored and private — never link to it from the page, and readdocs/internal/INDEXING_PLAN.mdfor strategy/decisions (domain-swap checklist lives there).
Deploy = push to main
Commit straight to main and push (no PRs in this repo). GitHub Pages
rebuilds in ~30–60 s. Always verify after pushing:
until curl -sL https://aidemo.top/ | grep -q "<distinctive new string>"; do sleep 6; done(-L matters: tandryukha.github.io/aidemo now 301s to aidemo.top, so a bare
curl -s there greps a redirect stub and never matches.)
Run that check with Bash run_in_background: true, never a bare foreground sleep.
Hard rules (learned, do not relearn)
- Only claim what ships. No named future integrations or roadmap promises
on the page. (History: ElevenLabs was removed while planned, then claimed
once it shipped; the old "Codex/Gemini planned" exception is obsolete —
since v0.6.0 they work today via the built-in MCP server, as do the
ElevenLabs provider and the in-process local voice, and the page claims all
of them as shipped.) Describe extensibility via what's true in code
("swappable
VoiceProviderinterface"). - Positioning (approved): built for coding agents to autonomously record
product demos — landing-page hero videos, GitHub README walkthroughs,
what-shipped videos for customer release notes. Open-source alternative to
Screen Studio / Clueso / Demosmith. Keep this framing consistent across
hero sub, meta description, og:description, JSON-LD, and llms.txt.
Audience = developers (owner directive): write dev-to-dev — terminal-first
examples with real, runnable commands and real paths, no marketing fluff.
When showing an assistant/integration, show the actual command a developer
would type (if a genuinely unshipped integration ever needs showing, a
muted
# plannedcomment is the approved mechanism — currently none are). - Video, never GIF, for the hero. GIFs are 256-color mush (the old
560×350 GIF looked terrible upscaled). Use
<video autoplay muted loop playsinline preload="metadata" poster=...>with a same-origin MP4. Setwidth/heightattrs to the file's REAL dimensions (check withffprobe -v error -select_streams v:0 -show_entries stream=width,height -of csv=p=0 <file>) and keep CSSwidth:100%; height:auto; aspect-ratio: W / H— a mismatched height attribute stretches the frame. - Self-contained page. No CDN scripts, external fonts, or third-party
requests. Inline everything. Both color schemes must work
(
prefers-color-scheme+ the CSS variables at the top of the file). - FAQ and JSON-LD move together. Every visible FAQ
<details>has a matching entry in theFAQPageJSON-LD block, same wording. Question-shaped headings ("Can Claude Code record a demo video?") — LLM search lifts them verbatim. New claims also go intollms.txt. - Respect the motion system. Load stagger =
fade+d1..d5classes; scroll fade-in/out =revealclass picked up by the IntersectionObserver at the bottom of the file; everything is disabled underprefers-reduced-motion. New sections:class="reveal"on theh2and on each card/step/details. Don't add per-elementtransition-delaythat would lag hover states (.reveal.inresets it to 0s for this reason).
Design system (match, don't reinvent)
- CSS variables in
:root(+ light-mode override block):--bg, --panel, --border, --text, --muted, --accent(#d97757 coral),--accent-2(#b07aff violet),--shadow. - Building blocks already styled:
.term(terminal window w/ traffic-light bar),.cards/.card(grid + hover lift),.steps/.step(numbered gradient chips),.faq details,.pill,.btn primary|ghost,.halo(blurred accent glow behind the hero video). - Max content width 920px (
.wrap); wide content scrolls in its own container, the body never scrolls horizontally. - Section order: hero → How it works → Why it's built this way →
Made with aidemo (#examples) → Integrations → Quickstart → FAQ → footer.
New sections get a nav link (
hide-smclass hides it on mobile).
Icon system (no emojis)
Card icons, the nav brand mark, and the favicon are locally generated matte-clay badge tiles (own dark backdrop → theme-proof), NOT emojis and NOT transparent cutouts. Rendered with the dropshipping-irondust SDXL backend:
HF_HUB_DOWNLOAD_TIMEOUT=20 ~/.venvs/sdxl/bin/python \
~/dropshipping-irondust/scripts/blog/sdxl_backend.py --fast --jobs jobs.jsonl- Job =
{"prompt", "negative", "out", "seed", "width":1024, "height":1024}; prompt is used verbatim. Locked style prompt: "3D icon of {subject}, minimalist matte clay style, soft rounded shapes, smooth studio product render, centered, floating on a plain dark charcoal background, coral orange and violet purple rim lighting, gentle top light, soft shadow, high detail, square composition" — matches--accent/--accent-2. Keep it for new icons or the set stops matching. Note:--fastruns guidance 1.0, so the negative prompt has little effect and CLIP truncates at 77 tokens — the positive prompt must carry the style. - Generate 2–3 seeds per subject, pick at ACTUAL size (44px and 24px composited
on
#161a20AND white) before shipping — subjects that come out crumbly or abstract get re-rolled, not shipped. Object subjects work; abstract marks don't. - Post-process: crop ~6% margins → 176×176 webp q85 (44px @4x) →
docs/icons/{name}.webp; wire as<img class="ic" ... width="44" height="44">above the cardh3(alt="" aria-hidden). Customer logo marks useclass="ic brand"(transparent, no tile). Favicon = 64px PNG of the clapper icon. - Raw seeds/jobs live in the session scratchpad only; committed output is the small webps. One GPU job at a time (Metal contention).
When swapping the hero video
gh release download <tag> --repo tandryukha/aidemo -p '<asset>.mp4' -O docs/hero-demo.mp4- Regenerate the poster:
ffmpeg -y -v error -ss <good-second> -i docs/hero-demo.mp4 -frames:v 1 -q:v 3 docs/hero-poster.jpg - Update the
aspect-ratio/width/heightattrs if dimensions changed. - Keep the "watch the narrated version" link pointing at the release asset URL (the page's video is muted).
When the custom domain lands
Follow the swap checklist in docs/internal/INDEXING_PLAN.md §4: Pages
custom-domain setting, find-replace the tandryukha.github.io/aidemo URLs in
index.html (canonical, og:url, og:image), robots.txt (Sitemap line),
sitemap.xml, package.json homepage, repo website field; then Search
Console + Bing Webmaster Tools verification and sitemap submission.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

