animaxxing-skills
Copilot instructions22 starsChanged 50 days agoMITView on GitHub
This repository publishes Agent Skills in three families: framework skills for routing and rendering environments, motion skills for reusable GSAP effects, and style skills for visual design and motion art direction. Before changing a skill, read AGENTS.md and the target skill's SKILL.md.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,343 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/llms.txtllms.txt
- animaxxingSkill
- animaxxing-webglSkill
- gsap-astroSkill
- gsap-nextjsSkill
- gsap-nuxtSkill
- gsap-react-routerSkill
- gsap-sveltekitSkill
- gsap-tanstack-routerSkill
- gsap-vanillaSkill
- style-animaxxingSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 11
Keep names, descriptions, the README skills tables, and skills/llms.txt synchronized.
- Distinctive: line 12
Run the validation workflow before committing.
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
Animaxxing — Repository-wide instructions for GitHub Copilot
This repository publishes Agent Skills in three families: framework skills for routing and rendering environments, motion skills for reusable GSAP effects, and style skills for visual design and motion art direction. Before changing a skill, read AGENTS.md and the target skill's SKILL.md.
- Framework skills own routing, rendering, animation timing, interruption, and cleanup. Leave the GSAP API itself to the official GSAP skills.
- Motion skills own reusable recipes and technical requirements, preserving the app's fonts, colors, and layout. Use vanilla TypeScript and GSAP without framework constructs.
- Style skills own tokens, typography, layout, and effect selection/configuration. Keep implementations in motion skills; a static restyle must not require animation.
- Neither motion nor style skills own lifecycle. Use the shared wording exactly: mount → initial state → intro → settled → outro → end state → unmount.
- Gate framework advice on installed versions and bundled source or types rather than memory.
- Preserve progressive disclosure: essential routing stays in
SKILL.md; substantial details belong in focusedreferences/files linked from it. Cross-skill references use installed skill names rather than assuming sibling directories. - Keep names, descriptions, the README skills tables, and
skills/llms.txtsynchronized. - Run the validation workflow before committing.
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.