coding-styleguide-html-css

A set of HTML and CSS coding rules with a focus on accessibility. HTML structures web pages, while CSS controls their visual presentation.

In plain words
What is it for?
Writing and reviewing semantic HTML, accessible forms, buttons, links, image alt text, CSS selectors, and related web styles.
Why use it?
It helps prevent common web interface problems such as unlabeled form fields, incorrect link or button usage, and missing image descriptions.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/peerigon/configs/coding-styleguide-html-css
Clone the repo
git clone --depth 1 https://github.com/peerigon/configs
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 803 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00803
Opus 5 $0.00000 $0.00402
Sonnet 5 $0.00000 $0.00161
Haiku 4.5 $0.00000 $0.00080

Measured yesterday against content hash b1406e2de481, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

coding-styleguide-html-css scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ai/coding-styleguide-html-css.mdc · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

HTML & CSS

HTML

Semantic Elements

Use semantic elements like header, nav, main, article, section, aside, footer, figure, time when content has inherent meaning:

<article>
  <h1>Breaking News</h1>
  <time datetime="2025-01-15">January 15, 2025</time>
</article>

Form Labels

Every input requires an associated label. Prefer wrapping the input with label. Otherwise use for/id (when using React, call useId()):

<!-- Good -->
<label for="user-email">Email Address</label>
<input type="email" id="user-email" name="email" />

<!-- Better -->
<label>
  Email Address:
  <input type="email" name="email" />
</label>

Buttons vs. Links

Use buttons for actions, links for navigation:

<button type="button" onclick="saveData()">Save</button>
<a href="/next">Next</a>

Image Alt Text

Provide descriptive alt text for content images, empty alt for decorative images:

<img src="chart.png" alt="Sales increased 23% in Q4 2024" />
<img src="decoration.png" alt="" />

CSS

Selectors and naming

Use purpose-based named classes for styling with a maximum of 3 levels specificity.

.site-header {
}
.card {
}
.error-message {
}
.feature-highlight {
}

Check what styling solution (CSS Modules, BEM, Tailwind, ...) is used in the project and follow its conventions.

Units

Use typography units like rem, ch, ... for typography-related spacing:

font-size: 1.125rem;

Use px for everything else:

border: 1px solid #ccc;

Accessibility

Focus Indicators

Provide visible focus for all interactive elements:

button:focus {
  outline: 2px solid #007bff;
  outline-offset: 2px;
}

Color Information

Never use color alone to convey information. Use text labels or patterns to supplement color.

Motion Preferences

Respect reduced motion preferences:

@media (prefers-reduced-motion: reduce) {
  * {
    animation-duration: 0.01ms !important;
    transition-duration: 0.01ms !important;
  }
}

Read the full file on GitHub · 160 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 160 lines · 803 tokens per session scan A b1406e2de481

Subscribe to this mod's changes

coding-styleguide-html-css is a cursor rule published in the GitHub repository peerigon/configs (4 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 803 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.