Total 50,277 skills, Frontend Development has 4850 skills
Showing 12 of 4850 skills
Debug Svelte application issues systematically. This skill helps diagnose and resolve Svelte-specific problems including reactivity failures, runes issues ($state, $derived, $effect), store subscription memory leaks, SSR hydration mismatches, and compiler warnings. Covers both Svelte 4 legacy patterns and Svelte 5 runes-based reactivity. Provides debugging tools like $inspect(), {@debug} tags, and svelte-check CLI usage.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Suite of tools for creating elaborate, multi-component interactive HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Capture a rendered local web page or app screen into the clipboard for pasting into Figma using the official html-to-design capture.js flow. Use when the user invokes /figma-capture, asks to copy the current browser page to Figma, asks for a dev-only Figma capture button, or asks whether figma_key/captureId is needed for Figma HTML capture.
Store speed audit — lazy loading, image compression, app bloat removal, theme code optimization
Frontend Code Commit Assistant, triggered in frontend projects with src directory structure. Summarize modified files under the src directory, generate standardized commit messages, and automatically execute add and commit operations. Supports features such as forbidden directory filtering, intelligent file selection, conflict detection, and multi-change separation. Note: Push operations are prohibited.
Run comprehensive accessibility audit (WCAG 2.1) on Webflow pages - checks buttons, forms, links, focus states, headings, keyboard navigation, and generates detailed reports with fixes. Requires Webflow Designer connection. Excludes image alt text (covered by asset-audit skill).
Apply when building VTEX IO apps that must work correctly in multi-binding stores where bindings use path prefixes (e.g. store.com/us/, store.com/br/). Covers rootPath extraction from x-vtex-root-path header, useRuntime().rootPath in React, URL construction in backends, link generation, asset paths, and API route considerations. Use when the app breaks or produces wrong URLs in cross-border or multi-binding setups.
Authoritative guide for implementing stunning, accessible, performant UI. Synthesizes design engineering philosophy, accessibility standards, animation principles, spatial design, typography, color systems, and component craft into a single actionable reference. Complements the design-system skill (which covers DESIGN.md spec writing) by covering the HOW of implementation. Trigger phrases: "build UI", "create component", "landing page", "make it look good", "frontend", "design", "polish UI", "implement design", "make it beautiful", "UI implementation", "component styling", "animation", "accessibility"
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
Edit and design the materials provided by users (webpage URLs / PDFs / DOCX files / Markdown / plain text / screenshots / pasted content) into a beautiful, offline-accessible and shareable **single-file HTML web article**. Based on the reacticle component protocol: instead of writing raw HTML/CSS manually, use semantic components + theme-constrained Raw free layers; follow the small harness workflow of source → planning → double confirmation → generation → final review → repair, and produce long articles with 100% information retention by default. Trigger scenarios: convert URLs/PDFs/DOCX files/articles into web articles / long-form articles / briefings / explanatory articles / visual articles / tutorials / review and retrospectives / program analyses, with triggers like 'render this as a beautiful web article / turn this into a web article / generate a shareable HTML long-form article / reacticle article'. Only generate articles, not backends, forms, dashboards, product prototypes or general web apps.