paololupo/gaanim-dev

Implement complete Gaanim features across the owning Rust crate, gaanim_api, PyO3 bindings, Python stubs and exports, Typst API docs, examples, and tests. Use when adding or extending public Rust or Python behavior, animation primitives, scene methods, drawables, layouts, rendering features, or fluent API methods in the Gaanim repository.

Diagnose and fix Gaanim defects with a reproducible case, root-cause analysis, focused regression coverage, and change-aware verification. Use for crashes, incorrect animation or rendering, timeline seek errors, layout or transform bugs, PyO3/Python API failures, documentation examples that do not run, visual regressions, or failing Gaanim tests and CI checks.

Audit and maintain the Gaanim repository's workspace, just commands, CI alignment, agent guidance, Python API contract, Typst documentation structure, generated artifacts, and dirty-worktree safety. Use for repository health checks, AGENTS.md or README maintenance, command drift, crate/workspace changes, CI workflow updates, cleanup planning, or preparing the repo for collaborative agent work.

Measure, compare, and evolve Gaanim runtime performance budgets for reload, exact seek, headless preview, and export. Use when profiling latency or memory, investigating a performance regression, calibrating p50/p95 budgets, changing the benchmark harness, or reviewing scheduled performance evidence in the Gaanim repository.

Synchronize Gaanim public Rust and Python APIs with the correct Typst documentation page, signatures, examples, and navigation. Use when API methods, constructors, arguments, defaults, return types, errors, compatibility aliases, examples, or docs/content/**/*.typ files change, or when auditing documentation drift after a feature change.

Select and run change-aware Gaanim verification profiles for Rust crates, the PyO3/Python API contract, Typst docs, examples, visual regression, and performance smoke. Use when testing a change, validating a fix or feature, checking CI parity, comparing snapshots, inspecting reports, or explicitly approving visual baselines.

Persist, list, inspect, and resume Gaanim bug reports through GitHub Issues. Use when the user asks to note, save, or report a Gaanim bug; list pending bugs; inspect a saved bug or issue number; or start fixing a bug that was previously recorded.