affaan-m/ecc

manim-video

Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/affaan-m/ecc --skill manim-video

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Manim Video

Use Manim for technical explainers where motion, structure, and clarity matter more than photorealism.

When to Activate

  • the user wants a technical explainer animation
  • the concept is a graph, workflow, architecture, metric progression, or system diagram
  • the user wants a short product or launch explainer for X or a landing page
  • the visual should feel precise instead of generically cinematic

Tool Requirements

  • manim CLI for scene rendering
  • ffmpeg for post-processing if needed
  • video-editing for final assembly or polish
  • remotion-video-creation when the final package needs composited UI, captions, or additional motion layers

Default Output

  • short 16:9 MP4
  • one thumbnail or poster frame
  • storyboard plus scene plan

Workflow

  1. Define the core visual thesis in one sentence.
  2. Break the concept into 3 to 6 scenes.
  3. Decide what each scene proves.
  4. Write the scene outline before writing Manim code.
  5. Render the smallest working version first.
  6. Tighten typography, spacing, color, and pacing after the render works.
  7. Hand off to the wider video stack only if it adds value.

Scene Planning Rules

  • each scene should prove one thing
  • avoid overstuffed diagrams
  • prefer progressive reveal over full-screen clutter
  • use motion to explain state change, not just to keep the screen busy
  • title cards should be short and loaded with meaning

Network Graph Default

For social-graph and network-optimization explainers:

  • show the current graph before showing the optimized graph
  • distinguish low-signal follow clutter from high-signal bridges
  • highlight warm-path nodes and target clusters
  • if useful, add a final scene showing the self-improvement lineage that informed the skill

Render Conventions

  • default to 16:9 landscape unless the user asks for vertical
  • start with a low-quality smoke test render
  • only push to higher quality after composition and timing are stable
  • export one clean thumbnail frame that reads at social size

Reusable Starter

Use assets/network_graph_scene.py as a starting point for network-graph explainers.

Example smoke test:

bash
manim -ql assets/network_graph_scene.py NetworkGraphExplainer

Output Format

Return:

  • core visual thesis
  • storyboard
  • scene outline
  • render plan
  • any follow-on polish recommendations

Related Skills

  • video-editing for final polish
  • remotion-video-creation for motion-heavy post-processing or compositing
  • content-engine when the animation is part of a broader launch

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
affaan-m
Communauté

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

Installations / 24h
489
GitHub Stars
308,2 k
Mis à jour
20 nov.
affaan-m
Communauté

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

Installations / 1h
5
GitHub Stars
308,2 k
Mis à jour
20 nov.
affaan-m
Communauté

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

Installations / 1h
2
GitHub Stars
307,9 k
Mis à jour
20 nov.
affaan-m
Communauté

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

Installations / 1h
2
GitHub Stars
307,9 k
Mis à jour
20 nov.