agentleFS
jqaisystemsjqaisystems/jqai-ai-skills/skills/demo-animation/SKILL.md

demo-animation

Skill3 starsChanged 6 months agoMITView on GitHub

Generate a simple desktop-oriented self-playing HTML product demo. Use for legacy demo walkthroughs with an intro screen, dashboard mockup, sidebar captions, timeline controls, cursor animation, highlights, piano music, and ending screen. Prefer demo-animation-v2 when the user needs mobile support, fullscreen controls, touch gestures, or the packaged template engine.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the project README, app entry points, and relevant UI files.

    line 16
  2. Very specific:

    If you need the original desktop architecture, read references/legacy-demo-engine.md.

    line 25
  3. Distinctive:

    Keep the generated UI realistic for the actual product.

    line 29
  4. Distinctive:

    Keep wait times reasonable: 800-1500ms for reading, 300-600ms for animations.

    line 30
  5. Distinctive:

    Do not add network dependencies beyond Google Fonts.

    line 31
  6. Very specific:

    Do not use this legacy skill when the user explicitly requests mobile-first, touch, fullscreen, or highly responsive behavior.

    line 32
  7. Very specific:

    Write to demo/index.html. Tell the user:

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Demo Animation

Generate a simple self-playing HTML product demo. Output: demo/index.html.

For most new demo requests, prefer demo-animation-v2. Use this skill when the user asks for the legacy desktop-oriented demo style or when a smaller, simpler demo is enough.

Workflow

  1. Read the project README, app entry points, and relevant UI files.
  2. Identify the product name, tagline, visual style, font stack, and 6-10 features to showcase.
  3. Draft a brief demo step list. If the project is unclear, ask one concise question; otherwise proceed.
  4. Generate a single self-contained demo/index.html file with no external dependencies except Google Fonts.
  5. Include intro, dashboard mockup, animated cursor/highlights, sidebar captions, timeline controls, optional piano music, ending screen, and replay.
  6. Validate that all referenced IDs exist, controls work, and the file opens directly in a browser.

Legacy Reference

If you need the original desktop architecture, read references/legacy-demo-engine.md. It contains the older detailed CSS, layout, animation, music, and quality checklist guidance.

Rules

  • Keep the generated UI realistic for the actual product.
  • Keep wait times reasonable: 800-1500ms for reading, 300-600ms for animations.
  • Do not add network dependencies beyond Google Fonts.
  • Do not use this legacy skill when the user explicitly requests mobile-first, touch, fullscreen, or highly responsive behavior; use demo-animation-v2 instead.

Output

Write to demo/index.html. Tell the user:

Demo created at `demo/index.html`. Open it in a browser to preview. Click "Watch Demo" to start the animation.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.