Frontend Agent Skill

Visual design taste for web UI, distilled from a stronger model's aesthetic - invoke when about to BUILD or STYLE any web page, component, artifact, or UI; picking a visual direction; writing CSS; reviewing how a design looks; or when a design works but feels generic or boring. Named style directions with exact tokens, concrete craft numbers, and a catalog of garbage design to refuse.

8k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

238

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/telagod/code-abyss --skill frontend

The instruction itself

4 sections, as written by the author

Frontend — taste, styles, craft, and what to refuse

Rule content lives in the five files below; this SKILL.md only routes (duplicating rule

text here is drift — doctrine/04-maintenance.md governs edits to this bundle too).

Route by moment

| You are about to… | Read (in this folder) |

|---|---|

| Start any page/component/artifact — brief to shipped | process.md first; it routes onward |

| Pick a visual direction, or choose between styles | styles.md |

| Understand what makes a design striking vs mediocre; make a boring design memorable | taste.md |

| Write actual CSS values — type, space, color, depth, motion, dark mode | craft.md |

| Judge a design (yours or anyone's); name precisely why something feels cheap | garbage.md |

Start with the ONE file that matches and follow its cross-references — they are required

inputs, not optional reading. Starting from scratch usually means process.md + the two

files it points you to.

Scope and neighbors

This bundle is the visual/aesthetic layer only. Server-side design (stack, APIs,

data) → the backend bundle; whether to delegate → doctrine; how to think → methods. If the environment provides an artifact-design skill

(harness-side), it calibrates how much to invest per request; THIS bundle governs

direction and craft once you're building.

The stance

Left unguided, every model produces the same page (garbage.md §A names it precisely).

What taste means here — and why a clean-but-forgettable page counts as a failure — is

taste.md's opening; read it before judging any design.

Other skills for the same job

different authors, same section of the catalogue

Theme Factory

by anthropics

vendor ×16

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

Suite of tools for creating elaborate, multi-component claude.ai 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.

11k tokens scripts

Web Artifacts Builder

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.

3k tokens

How to use it

Copy the folder

Take telagod/frontend from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.