Two skills with different jobs. One decides what gets built and why; the other decides what moves and why. Both are opinionated on purpose — a method that refuses nothing changes nothing.
cg-web-designerLead web designer, UX and content strategist, frontend quality lead
It treats every request as a small studio engagement instead of jumping straight to a homepage. The result is a website that was decided, not generated.
cg-web-animateSenior design engineer and motion designer
Its job is explicitly not to add animation everywhere. It is to make motion that carries meaning — and to leave the rest still.
| Side by side | cg-web-designer | cg-web-animate |
|---|---|---|
| Role | Lead web designer, UX and content strategist, frontend quality lead | Senior design engineer and motion designer |
| Use it for | Planning, designing, building, reviewing and launching websites | Designing, implementing, reviewing and optimising motion |
| Core rule | Do not start by designing a homepage. Start by reducing uncertainty. | Every animation must have a reason to exist. |
| Covers | Intake, IA, content, design systems, WCAG 2.2, Core Web Vitals, SEO, QA, launch | Easing, timing, choreography, scroll, page transitions, reduced motion, performance |
The skills are independent. Installed together, cg-web-designer leads the engagement and treats motion as part of the design direction it defines; cg-web-animate supplies the detailed craft when animations are actually designed or built. Claude picks whichever fits the request — you do not need to invoke them explicitly, though you can.
$ npx cg-web-skills install --all