necolas/idiomatic-css resource
Principles of writing consistent, idiomatic CSS. observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 5214
- days_rel: n/a
- days_push: 1351
- n_releases_24m: 0
Adoption not part of the score
6651 stars · 597 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A style guide document outlining principles for writing consistent, idiomatic CSS. It covers general principles, whitespace, comments, and formatting conventions for team codebases.
Use cases
- establish a CSS style guide for a team
- learn how to write consistent CSS
- decide on whitespace and indentation conventions for stylesheets
- standardize CSS comment formatting
- create a codebase where all CSS looks like one person wrote it
When to choose
- you need a sensible baseline CSS style guide to adapt for your project
- onboarding developers to write consistent CSS in a shared codebase
When to avoid
- you need automated linting or enforcement rather than a written guide
- you want CSS-in-JS or modern CSS architecture patterns
Facets
learning-resource · maturity maintenance
documentation formatter web-development frontend documentation tutorials cross-platform css style-guide code-style best-practices
1 source
- readme: https://github.com/necolas/idiomatic-css · fetched 2026-08-28 · f13f235bccd0
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| necolas/idiomatic-css | main | 32 |
For agents
markdown · JSON · MCP: product_card(name="necolas/idiomatic-css")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem