Frontend css

Skill bg-szy/TOP-SKILLS/skills/marketplace/frontend-css

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill frontend-css

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write consistent, maintainable CSS following the project's methodology (Tailwind utility classes) while minimizing custom CSS and adhering to design system tokens. Use this skill when writing or editing CSS files, Tailwind classes in React components (.tsx, .jsx files), when implementing design system colors/spacing/typography, when using Tailwind utility classes, when deciding between framework utilities vs. custom CSS, when optimizing CSS for production with tree-shaking, when configuring Tailwind theme extensions, or when maintaining design consistency across the application.

SKILL.md

1.7 KB, as published. Nobody here has run it

Frontend CSS

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle frontend CSS.

When to use this skill

When writing or editing CSS files in the project
When applying Tailwind CSS utility classes in React components (.tsx, .jsx files)
When implementing design system tokens (colors, spacing, typography)
When configuring Tailwind theme extensions using the @theme directive
When deciding between using framework utilities vs. writing custom CSS
When maintaining consistent styling patterns across components
When optimizing CSS for production with purging/tree-shaking
When avoiding unnecessary framework style overrides
When working with the project's CSS methodology (Tailwind, BEM, utility-first, etc.)
When implementing responsive styles using Tailwind breakpoints
When ensuring CSS performance and bundle size optimization

Instructions