css-formatting
Formatting and style guidance for CSS/stylesheet code: organization, naming, and linting.
Works with
Agent Skills format with YAML frontmatter. Claude Code reads it as-is.
--- name: "css-formatting" description: "Formatting and style guidance for CSS/stylesheet code: organization, naming, and linting." license: "MIT" --- # CSS Formatting Purpose: standardize stylesheet formatting and lint rules so teams have consistent, machine-enforced style. Recommended tools: - Prettier (with a CSS/PostCSS plugin) for deterministic formatting. - stylelint for lint rules, enforce property order, vendor-prefix policies, and allowed patterns. - Editor integrations: format-on-save and shared editorconfig to reduce friction. Opinionated rules (suggested): - Use custom properties for tokens and keep tokens in a separate file. - Enforce lowercase hex or prefer token names; avoid inline literal hex values in components. - Prefer logical properties (margin-block, padding-inline) where supported. Property ordering: - Group by box model → positioning → typography → visual (color, background) → transforms/animation. Color rules: - Prefer semantic token usage: `var(--color-text)`. - For generated palettes, produce OKLCH values or tokenized variants; delegate complex color decisions to `color-expert`. CI integration: - Add `stylelint` and `prettier --check` steps to CI to fail on style violations.
More General & Other skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

