css-formatting

Standardize CSS formatting and linting with Prettier and stylelint across frontend codebases.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/caraya/agent-skills --skill css-formatting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: css-formatting
Source: https://github.com/caraya/agent-skills/tree/main/skills/css-formatting
Command: npx skills add https://github.com/caraya/agent-skills --skill css-formatting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how CSS is organized, named, and linted to reduce stylistic drift and improve maintainability across projects.

Core Features & Use Cases

  • Guidelines for file structure, naming conventions, and token usage to enforce consistency.
  • Stylelint-based linting rules to enforce property order, vendor prefixes, and allowed patterns.
  • Prettier integration for deterministic formatting across the codebase.

Quick Start

Enable Prettier with the CSS plugin and stylelint in CI to automatically format and lint styles.

Frequently Asked Questions about css-formatting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize CSS formatting to prevent style drift across a team?

Standardize CSS formatting by enforcing file structure and naming conventions through Prettier and stylelint. This prevents style drift and ensures consistent styling across frontend codebases by applying deterministic formatting and linting rules in CI.

What is the best way to enforce CSS property order and naming conventions in a frontend project?

Enforce CSS property order and naming conventions using stylelint rules integrated into your CI pipeline. This approach automatically checks vendor prefixes, allowed patterns, and property ordering to maintain codebase consistency.

Does Prettier work with stylelint for CSS linting and formatting?

Prettier works alongside stylelint to handle CSS formatting and linting. Prettier manages deterministic code formatting while stylelint enforces specific style rules like property order and naming conventions, together preventing stylistic drift.

Can I adapt CSS linting rules to fit project-specific design tokens and naming schemes?

You can adapt CSS linting rules to fit project-specific design tokens and naming schemes. The formatting approach remains flexible enough to accommodate custom tokens while enforcing concrete baseline requirements via editor configurations.

Why does my CSS styling become inconsistent across different team members' editors?

CSS styling becomes inconsistent without shared editor configurations and automated formatting. Implementing Prettier with a CSS plugin and stylelint standardizes formatting deterministically, overriding individual editor settings to maintain a unified codebase style.