gsap-best-practices
GSAP Best Practices
Apply these rules when working on GSAP-powered animation codebases.
Current platform note
- As of March 6, 2026, official GSAP docs state that all plugins, including former Club GSAP bonus plugins, are freely available in the public package. Use the standard
gsappackage and do not recommend legacy private-registry or paid-only installation flows. Prefer GSAP3.13+when this matters.
Rule loading order
- Read
rules/gsap-core.md. - Read
rules/gsap-timelines.md. - Read
rules/gsap-scrolltrigger.md. - Read
rules/gsap-plugins.md. - Read
rules/gsap-utils.md. - Read
rules/gsap-performance.md. - Use
AGENTS.mdas a compact summary plus pointer.
Enforcement policy
- Use recommendation-first language for style and performance guidance.
- Use strict language (
must/must not) only for correctness, stability, and accessibility constraints. - Prefer official GSAP docs when resolving conflicts; update these rules when docs change.
More from jackkkonggg/skills
react-gsap-best-practices
Use when building, reviewing, or refactoring React components that use GSAP or @gsap/react (useGSAP, contextSafe, dependency-driven updates, ScrollTrigger integration, and SSR-safe setup) to enforce production-safe animation patterns.
8convex-best-practices
Use when writing, reviewing, or refactoring Convex backend code (queries, mutations, actions, HTTP actions, schema, indexes, scheduling, file storage, and search) to enforce production-safe patterns.
7code-audit
Use when auditing a codebase against best practices. Auto-detects technologies, loads relevant docs via Context7 MCP and installed skills, evaluates code systematically, and produces a prioritized findings report with optional auto-fix.
1swift-best-practices
Use when writing, reviewing, or refactoring Swift code to enforce best practices — naming, types, error handling, protocols, memory management, performance, and modern patterns — for idiomatic, safe Swift.
1typescript-clean-code
Use when writing, reviewing, or refactoring TypeScript code to enforce Clean Code principles — naming, functions, types, error handling, modules, testing, comments, and code smells — adapted for idiomatic TypeScript.
1grammy-best-practices
Use when writing, reviewing, or refactoring grammY Telegram bots in Node.js/TypeScript (middleware, commands, filters, sessions, conversations, API transformers, files/media handling, flood-limit control, runner concurrency, webhooks, and deployment operations) to enforce production-safe patterns.
1