Css Formatting
Formatting and style guidance for CSS/stylesheet code: organization, naming, and linting.
Install
$ agentstack add skill-caraya-agent-skills-css-formatting ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-caraya-agent-skills-css-formatting) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
stylelintandprettier --checksteps to CI to fail on style violations.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: caraya
- Source: caraya/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.