gsap-animated-frontend
NewPersistent, recoverable GSAP workflow for coding agents. Use when the user wants to animate a new page or section, or improve an existing page/component with GSAP. Route new/greenfield work to gsap-new and existing-code improvement work to gsap-refactor. Always use .gsap artifacts as the source of truth so any fresh agent session can resume without chat history.
Overview
GSAP Animated Frontend
Use this skill as the root router for a model-agnostic GSAP workflow.
Public Workflow Surface
Expose only two primary workflows:
- •
gsap-new - •
gsap-refactor
Do not present scan, audit, recipes, doctor, validate, or similar helpers as primary user-facing workflows.
Source Of Truth
Always read and update these project artifacts first:
- •
.gsap/animation-spec.md - •
.gsap/animation-plan.md - •
.gsap/audit-report.md - •
.gsap/pages/*.animation.md
Never rely on chat history as the workflow memory.
Workflow Routing
For new pages, new sections, or first-time motion systems:
- •read
subskills/gsap-new/SKILL.md
For existing pages/components that need improvement:
- •read
subskills/gsap-refactor/SKILL.md
Internal Helpers
Use internal scripts and templates for support work:
- •
scripts/gsap_workflow.py - •
scripts/brand_extractor.py - •
scripts/structure_search.py - •
scripts/interview_generator.py - •
scripts/phase_planner.py - •
templates/animation-spec.md - •
templates/animation-plan.md - •
templates/audit-report.md - •
templates/animation-tasks.md - •
templates/page-animation.md - •
templates/phase.md
Use references only as needed:
- •
references/gsap-core-patterns.md - •
references/scroll-trigger-patterns.md - •
references/animation-recipes.md - •
references/performance-guide.md
Non-Negotiables
- Persist decisions back into
.gsap. - Ask questions only when required by missing artifact data.
- Read current code before planning refactors.
- Include reduced-motion and mobile downgrade rules in every plan.
- Keep helper commands internal; the visible experience stays centered on
gsap-newandgsap-refactor. - Let the workflow script inspect framework, packages, page structure, design signals, and existing motion before asking questions.
- Do not implement an entire page in one pass; generate phased artifacts and execute one major section per phase.
- Keep
.gsap/tasks/*.mdand.gsap/phases/**/*.mdcurrent so a fresh agent can resume safely.
Install & Usage
mkdir -p .claude/skillsmkdir -p .claude/skills && curl -o .claude/skills/gsap-animated-frontend.md https://raw.githubusercontent.com/yousefabdallah171/gsap-animated-frontend/main/SKILL.md/gsap-animated-frontendSecurity Audits
Frequently Asked Questions
What is gsap-animated-frontend?
Persistent, recoverable GSAP workflow for coding agents. Use when the user wants to animate a new page or section, or improve an existing page/component with GSAP. Route new/greenfield work to gsap-new and existing-code improvement work to gsap-refactor. Always use .gsap artifacts as the source of truth so any fresh agent session can resume without chat history.
How to install gsap-animated-frontend?
To install gsap-animated-frontend, create the .claude/skills directory in your project, then run the curl command to download the skill file. Once installed, invoke it in Claude Code with /gsap-animated-frontend.
What is gsap-animated-frontend best for?
gsap-animated-frontend is a community categorized under General. It is designed for: refactoring, frontend, agent. Created by yousefabdallah171.