Frontend Guidelines (Bendc)
Foundational HTML, CSS, and JS best-practices repo by Benjamin De Cock (
bendc), described simply as "Some HTML, CSS and JS best practices." Created Feb 2015; 9,096 stars as of 2026-07-01. Emil Kowalski called it "the OG frontend skill file." Source: GitHub bendc/frontend-guidelines, https://github.com/bendc/frontend-guidelines, 2026-07-01
What It Is
A single-document style guide covering semantic HTML, accessibility defaults, CSS specificity discipline, layout flow, and JS brevity. Written as bad/good pairs — the same pedagogical pattern modern agent SKILL.md files use. Source: GitHub bendc/frontend-guidelines README, https://github.com/bendc/frontend-guidelines, 2026-06-13
Topics include: semantic elements over div soup, proper alt text, UTF-8 charset, deferring non-critical scripts, box-sizing consistency, avoiding unnecessary position: absolute, selector brevity, and inheritance over duplication. Language-agnostic vanilla HTML/CSS/JS — no framework, no build step. Source: GitHub bendc/frontend-guidelines README, 2026-06-01
Why It Matters
Created in 2015, it predates the agent-skills explosion by ~10 years yet encodes the same contract: opinionated defaults you load once and enforce. design-engineering-polish explicitly positions it as a predecessor to modern design-engineering skill files. Source: compiled from design-engineering-polish.md
Stack fit (Kevin)
- Lineage ancestor of Kevin's own frontend enforcement: CSS UI Enforcement (Tailwind +
cn(), globals-only raw CSS), Frontend and Design Skills (Vercel Interface Guidelines), and design-engineering-polish all extend this same bad/good-pairs discipline. Good primary source to mine when tightening those rules. - Reference prose, not a drop-in
SKILL.md— cite or wrap specific sections when authoring frontend agent rules rather than installing blindly. The semantic-HTML / a11y / specificity defaults are durable even where 2015-era specifics are dated. Source: User convention, 2026-06-01 - License caveat: the repo carries no license (all-rights-reserved by default), so adapt/quote rather than wholesale-copy into Kevin's committed rules. Source: GitHub bendc/frontend-guidelines, 2026-06-13
- Pairs with Frontend and Design Skills for the "distinctive output" half of the same problem — guidelines set the floor, art-direction skills raise the ceiling.
Source snapshot
Current check on 2026-07-01: bendc/frontend-guidelines has 9,096 stars, 679 forks, no declared license, no public tags, and master HEAD a6e4857b728b27889a24b916c069b35e76bfa3e6. The repo has not been pushed since 2023-12-30, which reinforces its role as a stable reference document rather than an active package dependency. Source: GitHub API and git ls-remote, 2026-07-01
Timeline
- 2026-06-01 | Enriched absorption: @emilkowalski bookmark resolved to full README (9,065 stars). Dedicated tool page created (previously timeline-only in design-engineering-polish). Source: enrichment pipeline, 2026-06-01
- 2026-05-15 | @emilkowalski: "The OG frontend skill file"; 2,018 likes, 2,876 bookmarks. Source: X/@emilkowalski, 2026-05-15
- 2026-06-13 | Quality remediation: verified repo facts (bendc / Benjamin De Cock, created 2015-02-21, 9,080★, no license), added explicit Kevin stack-fit and the license caveat. Source: https://github.com/bendc/frontend-guidelines
- 2026-07-01 | Deep-reviewed the resolved GitHub source for the artifact-audit row and refreshed source state to 9,096 stars, 679 forks, no license, no tags, and HEAD
a6e4857. Local decision unchanged: reference/adapt the patterns, do not copy wholesale. Source: GitHub API and X/@emilkowalski, 2026-07-01