madushan-skills

Browser main-thread budget discipline for animation, interaction and frontend performance work. Use this skill whenever the task touches animations, transitions, scroll or drag interactions, parallax, canvas or WebGL, real-time streams (WebSocket, SSE, polling), long lists and feeds, virtualization, image or video processing in the browser, or whenever the user mentions jank, stutter, lag, freezing, dropped frames, "feels slow", FPS, INP, TBT, LCP, CLS, Core Web Vitals, Lighthouse, or "optimize performance". Also use it before writing or reviewing any code that runs every frame, on every keystroke, on scroll, resize or mousemove, or on every socket message, even when the user never says the word "performance". When in doubt on any frontend task that produces motion or reacts to continuous input, load this skill.

SEO and GEO audit and auto-fix skill for Next.js projects. Use this skill whenever the user types /audit-seo or /fix-seo, or says anything like "audit my SEO", "check my site's SEO", "what SEO is missing", "fix my SEO issues", "optimize for Google", "improve search visibility", "add structured data", "fix metadata", "check robots.txt", "create a sitemap", "improve Core Web Vitals", "optimize for AI search", "GEO optimization", or any SEO/performance/discoverability improvement request on a Next.js codebase. Also triggers for questions like "why isn't my site ranking", "Google can't index my pages", "missing Open Graph tags", or "my Lighthouse SEO score is low". Works on both single Next.js apps and monorepos — always invoke this skill even if the user hasn't explicitly said "SEO" but is clearly asking about search performance, discoverability, or structured data for their Next.js project.

Audit Next.js code for performance bottlenecks and give fix directions, starting with a TL;DR and offering a detailed report. Works on any scope, from a pasted component or function, a single file, a feature folder, a directory of files, up to a full Next.js project or monorepo app. Use this skill whenever the user asks to review, audit, profile, speed up, or optimize Next.js or React Server Components code, mentions slow pages, bundle size, Core Web Vitals (LCP, INP, CLS), hydration, caching, "use cache", next/image, next/font, next/script, or asks "why is this slow" about a Next.js app, even if they do not say "performance audit". Knowledge is verified current to Next.js 16.3 / React 19.3 (Sep 2026) and flags outdated 2024 to 2025 era advice.

Recreate a visual effect as a WebGL shader from a reference image or video, delivered as one self-contained HTML file. Use this skill whenever the user shares a screenshot, photo, GIF, or video clip of a visual effect, background, gradient, or animation and asks to rebuild, recreate, clone, match, or "make something like this" in code. Also use it whenever the user asks for a shader, GLSL, a WebGL or animated hero background, a generative or procedural visual, a noise/gradient/liquid/chrome/caustics/plasma/fractal/particle effect, or a Shadertoy-style sketch, even when no reference file is attached and even when they never say the word "shader".

Create and recreate SVG graphics with measurable quality. Two modes. RECREATE turns a reference image (PNG/JPG/WebP screenshot, logo, icon, illustration) into a clean SVG and loops, rendering and comparing pixel by pixel, until it matches at least 98%. CREATE designs new SVG artwork (icons, logos, illustrations, badges, patterns, backgrounds, diagrams) from a text prompt, optionally inspired by reference images. Use this whenever the user asks to vectorize, trace, convert an image to SVG, rebuild a logo as vector, make or draw an SVG, icon, logo mark, illustration or vector graphic, even if they never say "SVG" explicitly (e.g. "can you make this logo scalable", "draw me an icon set").