Family

Claude skills for web development

13 skills in the bank are filed under Web. They are grouped here because they compete for the same jobs - which is the reason an agent reaching for one of them sometimes gets another.

• Design Taste FrontendleonxlnxBuilds the persuasion surface of a website - a launch page, a personal or studio portfolio, a visual overhaul of a site that already exists - and ships the working page, steered hard away from the templated look a model reaches for by default: a stated aesthetic read of the brief, a committed type and colour language, and motion that has to justify itself. Its scope stops at surfaces meant to be scrolled and read; dashboards, data grids, and multi-step wizards are handed off to a product-UI system rather than restyled.
• Design Taste Frontend V1leonxlnxThe superseded edition of the same frontend skill, kept installable so a project tuned against its exact rules does not shift underneath when the current one changes them. Nothing about its subject differs. Only its vintage does.
• Frontend Designanthropics/skillsDeciding how a UI should look and feel before you build it: typography, colour, hierarchy, and escaping the default templated appearance.
• GPT TasteleonxlnxThe same push away from templated pages, aimed at Codex and GPT because they drift differently: it forces a fresh pick of hero shape, type stack and scroll choreography each build instead of reaching for last time's, and leans hard on scroll-driven motion. What separates it from the general version is the model it corrects, not the work it covers.
• High End Visual DesignleonxlnxSpends its rules on the feel of expensive: how far a card lifts, how light falls across it, how long an easing runs, how much room a section is given. It varies the composition every time by design, and the things it bans are the ones that read as cheap, like blunt shadows and motion that snaps.
• Image to CodeleonxlnxDraws the page as artwork first, one legible frame per band of the page, studies what it drew, then writes the frontend to match. The picture is a step in the middle rather than the deliverable, which is what separates it from the image-only skills next to it.
• Industrial Brutalist UIleonxlnxCommits a build to one hard-edged look: exposed structure, sizes that jump from tiny to enormous, colour used only to warn, and print or CRT artefacts faked in software. Pick it when the interface should read as machinery rather than a product, and when packing the screen is the point.
• Minimalist UIleonxlnxStrips an interface back to type, rules and air: warm greys, shadow almost absent, tiles laid flat, one muted tint where something has to stand out. The result reads as a document more than an app, and gradients and pill-shaped containers are refused outright.
• Redesign Existing ProjectsleonxlnxReads the code already there and names what is weak in it, then lifts type, rhythm, colour and the states nobody built, on whatever styling the project happens to use. The binding constraint is that it improves in place rather than replacing, so structure and behaviour survive the pass.
• Responsive DesignwshobsonMake one layout work across screen sizes - fluid grids, breakpoints, and sensible touch targets - so a page reads well on phone, tablet, and desktop without a separate mobile site.
• Theme Factoryanthropics/skillsPut a consistent look on something already built: pick or generate a colour-and-font theme and apply it across slides, docs, or a page.
• Web Artifacts Builderanthropics/skillsAmbitious claude.ai artifacts with many moving parts: React, Tailwind, component libraries, real state and routing rather than a single static page.
• Webapp Testinganthropics/skillsDrive a running web app with a real browser to check it works: click through a flow, grab a screenshot, read the console when it breaks.