example-svelte
Skill130 starsChanged 38 days agoApache-2.0View on GitHub
Patterns for using Helios with Svelte. Use when building compositions in a Svelte environment, utilizing Svelte stores for reactive frame updates.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- skill-creatorSkill
- helios-coreSkill
- animated-video-philosophySkill
- cinematic-product-promo-planSkill
- motion-stylesSkill
- example-canvasSkill
- example-chartjsSkill
- example-d3-animationSkill
- example-framer-motionSkill
- example-gsapSkill
- example-lottieSkill
- example-p5-animationSkill
- example-pixiSkill
- example-podcast-visualizerSkill
- example-reactSkill
- example-signals-animationSkill
- example-solidSkill
- example-tailwind-animationSkill
- example-threejsSkill
- example-vanillaSkill
- example-vueSkill
- helios-getting-startedSkill
- guided-brand-videoSkill
- guided-cartoon-shortSkill
- motion-design-rulesSkill
- guided-music-videoSkill
- guided-video-recipesSkill
- helios-playerSkill
- helios-rendererSkill
- helios-skillsSkill
- helios-studioSkill
- archive-brollSkill
- create-compositionSkill
- render-videoSkill
- workflow-visualize-dataSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 149
Reactive Statements (
$:): Use reactive statements to trigger redraws whenever $heliosStore updates.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Svelte Composition Patterns
Integrate Helios into Svelte components using Svelte Stores to manage frame state reactivity efficiently.
Quick Start
1. Create Helios Store
Wrap the Helios instance in a readable store to make state reactive.
// lib/store.js
import { readable } from 'svelte/store';
export const createHeliosStore = (helios) => {
return readable(helios.getState(), (set) => {
// Set initial value
set(helios.getState());
// Subscribe to updates
const unsubscribe = helios.subscribe((state) => {
set(state);
});
return unsubscribe;
});
};2. Create Composition Component
<!-- App.svelte -->
<script>
import { onMount, onDestroy } from 'svelte';
import { Helios } from '@helios-project/core';
import { createHeliosStore } from './lib/store';
let canvas;
let ctx;
const duration = 5;
const fps = 30;
// Initialize Singleton
const helios = new Helios({ duration, fps });
helios.bindToDocumentTimeline();
// Expose to window
if (typeof window !== 'undefined') window.helios = helios;
// Create Store
const heliosStore = createHeliosStore(helios);
// Reactive Drawing Statement
$: if (ctx && $heliosStore) {
draw($heliosStore.currentFrame);
}
function draw(frame) {
const width = canvas.width;
const height = canvas.height;
// Clear
ctx.clearRect(0, 0, width, height);
// Draw
const progress = frame / (duration * fps);
ctx.fillStyle = '#ff3e00';
ctx.fillRect(progress * width, height / 2 - 50, 100, 100);
}
onMount(() => {
ctx = canvas.getContext('2d');
canvas.width = 1920;
canvas.height = 1080;
// Initial draw
draw(helios.currentFrame.peek());
});
</script>
<canvas bind:this={canvas}></canvas>
<style>
canvas {
display: block;
width: 100%;
height: 100%;
}
</style>Svelte 5 (Runes)
For Svelte 5, use the $state rune to create a reactive state class.
1. Create Helios State Class
// lib/helios.svelte.ts
import { Helios } from '@helios-project/core';
export class HeliosState {
currentFrame = $state(0);
fps = $state(0);
duration = $state(0);
isPlaying = $state(false);
constructor(helios) {
this.fps = helios.fps;
this.duration = helios.duration;
this.isPlaying = helios.isPlaying;
helios.subscribe((state) => {
this.currentFrame = state.currentFrame;
this.isPlaying = state.isPlaying;
});
}
}2. Use in Component
<!-- App.svelte -->
<script>
import { Helios } from '@helios-project/core';
import { HeliosState } from './lib/helios.svelte.js';
const helios = new Helios({ duration: 10, fps: 30 });
const state = new HeliosState(helios);
// Reactivity works automatically with state properties
$effect(() => {
console.log(`Current Frame: ${state.currentFrame}`);
});
</script>
<div>Frame: {state.currentFrame}</div>Key Concepts
- Store Pattern: Svelte's
readablestore is the perfect primitive for wrapping thehelios.subscribecallback. - Reactive Statements (
$:): Use reactive statements to trigger redraws whenever$heliosStoreupdates. - Singleton Helios: Initialize
Heliosoutside the component script or in a separate module to ensure it persists if the component remounts (though for a root App component, inside<script>is fine).
Audio Visualization Pattern
For audio visualization, use a derived store to compute analysis data (RMS, Waveform) reactively based on the current frame.
1. Create Audio Store
// lib/audio.js
import { derived } from 'svelte/store';
export function createAudioStore(bufferStore, heliosStore) {
return derived(
[bufferStore, heliosStore],
([$buffer, $heliosState]) => {
if (!$buffer || !$heliosState) return { rms: 0, waveform: [] };
const data = $buffer.getChannelData(0);
const sampleRate = $buffer.sampleRate;
const time = $heliosState.currentFrame / $heliosState.fps;
// Analyze window around current time
const center = Math.floor(time * sampleRate);
const windowSize = 1024;
// ... (FFT logic or simple time-domain analysis) ...
return { rms: 0.5, waveform: [] }; // Mock result
}
);
}2. Use in Component
<script>
import { createAudioStore } from './lib/audio';
// ... setup heliosStore and bufferStore ...
const audioStore = createAudioStore(bufferStore, heliosStore);
$: if (ctx && $audioStore) {
const { rms, waveform } = $audioStore;
// Draw using rms/waveform
}
</script>Source Files
- Example:
examples/svelte-canvas-animation/ - Example:
examples/svelte-runes-animation/ - Example:
examples/svelte-audio-visualization/
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.

